this post was submitted on 20 Mar 2025
10 points (100.0% liked)

Selfhosted

44837 readers
1306 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
10
[Solved] Nextcloud AIO inside container - domain verification fails (sh.itjust.works)
submitted 3 days ago* (last edited 2 days ago) by [email protected] to c/[email protected]
3 comments fedilink hide all child comments
 

I am setting up nextcloud AIO in a podman container on my VPS. After some struggle, I got to the installation page, but domain checking is simply not working out.

After looking up, I decided to check the port from host machine. Strangely, curl localhost:11000 hangs indefinitely. nextcloud-aio-domaincheck container is running, and it mapped port as 0.0.0.0:11000->11000/tcp. The domaincheck server should be reachable, and I don't think firewall would be preventing localhost access.. The single line log from domaincheck container is:

2025-03-20 13:47:43: (../src/server.c.1939) server started (lighttpd/1.4.76)

I am utterly lost here. Does anyone know what would be possible reasons, and how to troubleshoot the issue? Any pointers would be greatly appreciated. Thank you in advance!

EDIT: Just ran sudo podman exec nextcloud-aio-mastercontainer curl nextcloud-aio-domaincheck:11000, it seems to work in the internal network. At a loss how this does not get exposedd to the host..

EDIT2: Solved it, podman is misbehaving when the port is set to 0.0.0.0. Darn it, podman is such a pain..

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 3 days ago (1 children)

Are you able to independently confirm that the domaincheck container is listening to the right port? Eg netstat -tunlp on the host

[–] [email protected] 1 points 2 days ago

I got

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
...
tcp       51      0 0.0.0.0:11000           0.0.0.0:*               LISTEN      155359/conmon

It is listening at the right port. But Recv-Q is nonzero, which seems quite strange.