Nextcloud version (eg, 29.0.5): 29.0.8
Operating system and version (eg, Ubuntu 24.04): Ubuntu 22.04
Apache or nginx version (eg, Apache 2.4.25): Apache 2.4.55
PHP version (eg, 8.3): 8.2.24
Problem first encountered after update to 29.0.7.
Hi everyone,
you see me completely confused. Maybe you can help me get back on track…
What’s not working:
I am unable to reach my Nextcloud instance over WIFI, using local IP (i.e. entering something like https://192.168.x.x:443 or similar on several smartphones’ different browsers just gives me a time out).
(Using external IP or name it doesn’t work either, but well, there’s a crappy router without NAT-loopback, so that’s to expect.)
What is working:
I can reach the Nextcloud instance with external IP or name over the mobile connection.
I can reach the Nextcloud instance over the LAN from the desktops.
I can ping the host over WIFI.
I can reach other services on the host over WIFI.
I can even reach a non-Nextcloud-port of the same Apache installation over WIFI.
Most probably I’m just plain stupid (or tired), but thinking this through for days and reading dozens of posts here and elsewhere I don’t have the slightest clue where to look for the solution.
Nothing special done for the LAN connection. Two (automatic) routes, default and 192.168.0.0 on a desktop.
Wifi is on the same network, and the host is reachable from the phone - just not ports 80 and 443.
I just installed a port scanner on the phone. Ports 80 and 443 are missing, besides that it’s the same ports as from the desktop. That probably rules out nextcloud as the culprit, but I still don’t have a clue where to search next. It’s not firewall on the server, not firewall on the router, …
Is this a router where you have full access and you can run tcpdump or similar? This way you can check if the packets arrive at the router, if they are forwarded to the server, … this way you can see at which point they are filtered.
Do you have other mobile devices on the wifi behaving the same way?
No, it’s an ISP router (Vodafone Station CGA6444VF 19.3B80-3.5.12), I only have a web interface with limited options.
I tested with three mobile devices, three different android-flavours, four different browsers, none of them gets a connection to 192.168.x.x:80 or :443.
Just put up a test web server on my desktop. Works fine…
Okay, I think I “solved” it.
When I turn on port forwarding in the router, mobile devices cannot connect to these ports locally. LAN devices can.
When I turn off port forwarding in the router, mobile devices can connect to the server over wifi using local ip. Of course then they can’t connect from anywhere else, but well, you can’t have everything, I guess.
I’m sorry to have wasted your time. It’s just a damn bug in the router (and I don’t think anybody’s gonna convince me that this might not be a bug…)
@cgdi
The error is that you are trying to access via local IP address at all. This is completely unnecessary. It also means that you have different URLs on different devices or channels.
Normally, access via the global name should be possible both externally and internally. Possibly look for Hairpinning and NAT traversal.
@devnull Of course it started out with the domain name not working. But after some hours of “it’s always dns” I noticed local IP didn’t work either, which is a much more fundamental problem obviously.
The router isn’t capable of NAT-loopback, so I make use of local DNS and stuff, but that’s not the thing I wanted to discuss here (as it is working fine, usually).
Thanks, problem (more or less) solved.