[Solved] Nextcloud AIO inside container - domain verification fails
from someacnt@sh.itjust.works to selfhosted@lemmy.world on 20 Mar 14:03
https://sh.itjust.works/post/34758068

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…

#selfhosted

threaded - newest

RagingHungryPanda@lemm.ee on 20 Mar 14:13 next collapse

Can you share some screenshots? It sounds like you’re not even reaching the service.

CrackedLinuxISO@lemmy.dbzer0.com on 20 Mar 17:29 collapse

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

someacnt@sh.itjust.works on 21 Mar 12:41 collapse

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.