Hi all!
I’ve had Nextcloud installed on Docker and it has been working for a while until now.
I had to change my server from wifi to Ethernet and gave it a new static IP. I also uninstalled docker and reinstalled it so I’d be starting fresh.
I have Nextcloud working and when I go to localhost:8070, Nextcloud works properly. When I use another device connected to the same network by wifi, it doesn’t work.
I made sure the config.php file has the server’s static IP address listed in the trusted domains category.
This used to work before but now after hours of troubleshooting, I’m all out of ideas and frustrated 😩 Any help is appreciated.
EDIT: My wife to stroll by and casually was all “did you check Windows Firewall?” and lo and behold, Windows Firewall chose today to block private connections on Docker Desktop backend -_-
Once I enabled it everything worked perfectly. Leaving this up here in case someone else stumbles upon this exact issue.
What is the error you get when you try to connect from another device? If not a webserver error, then maybe a firewall issue. Docker might do weird things to your firewall rules when you first install
I’ve had Docker running a Nextcloud container successfully without issues twice before but you were exactly right.
Docker for some reason unchecked “private connections” in firewall settings. Re-checking it fixed everything and my sanity is back.
I stopped using docker because of this terrible behaviour…
How can anyone design a container that silently rewrites the firewall rules on the host??? Makes no sense
Podman manages to work without doing this
Ya checking windows firewall was the very last thing I had on my bingo list. It just didn’t logically make sense to me that it would work two other times without issue but the third time, my firewall settings quietly change 😆
I’ll look into podman and see if I’m smart enough to use it properly.
Some wireless access points / routers restrict access to Lan devices by default. You should be able to change this.
It’s also possible you have your wireless access point set up incorrectly if it isn’t your main router. Is your wifi devices on a different subnet? Is the WAP running a dhcp server? Did you plug your Lan cable into the wan port on it instead of one of switching ports?
If you can ping the server from a wifi device then it’s a server configuration issue. Is your NC instance binding to local host or the static ip? 0.0.0.0 would work too.
Tbh, to troubleshoot this rather elaborate problem (many things changed) we need more info. Besides, there is a NC community on lemmy and a NC community I think on help.nexctloud.com which should have pretty easy answers. I‘ve been asking questions there a lot and they’re experts.
Oh good advice! I’ll subscribe to the Nextcloud community. Didn’t cross my mind that it would exist haha.
Always happy to help!
Can you reach the server’s IP in general from other PCs in your network? Or is the issue restricted to the nextcloud service?
Ya, other services that I was running on that machine were accessible by IP address by other devices on the network, it was just Nextcloud giving me grief. Turns out the firewall decided docker was no longer friends. Everything is working great now :)
Stupid question, but you’re entering the servers_ipaddress:8070
When trying to access from a computer other than the server, Correct?
Ya I was trying to access http://192.168.2.x.
I had been troubleshooting for hours only for my wife to stroll by and be all “did you check Windows Firewall?” and lo and behold, Windows Firewall chose today to block private connections on Docker Desktop backend -_-
Once I enabled it everything worked perfectly. Leaving this up here in case someone else stumbles upon this exact issue.
I would check your router’s device table. See if you can find your nextcloud instance. It shouldn’t have a different IP given what you’ve done, but it still sometimes happens. Checking the router first will cut down your troubleshooting time.
Have a look into the logs of nc and see if it complains about a trusted proxy or similar. The ip range within a container network often changes between resstarts and that was a problem for me with my reverse proxy setup.
