Hi there !
I’m facing a problem with external access to nextcloud :
I have a domain name on no-ip (because my router has a dynamic ip). First I could acces only with my phone and 4G. I’ve partially solved this problem with dnsmasq and adding domain name in /etc/hosts so now I can access from my computer (wifi and ethernet) but still can’t access with my phone on wifi. It seems that it’s because my router can’t deal with nat loopback. Is there any workaround to this annoying problem ?
Thanks for your help
um… I’d say… there shouldn’t be any problem accessing your server via a no-ip.domain. There’s thousands of users doing that on a regular basis.
so it must be your serversetup and thus I’m afraid we’d need more infos about your setup…
wwe
February 18, 2022, 10:00pm
3
please use search the problem has been discussed often
I am running a nextcloud 18.0.11 on an own server behind a fritzbox. Since the last client of the android nextcloud app all users suffer a connection issue, when the phone is logged into a WIFI-network. The connection issue seems not to be there, when accessing from mobile network or even VPN to the university network. There is no connection attempt appearing in the nextcloud log, the app shows the message “Server nicht verfügbar”, when being opened while connected to a WIFI.
Setup Information: …
I am new to NextCloud server and I must say the documentation is much better than owncloud and many other open-sources projects. That said, after I successfully installed Nextcloud 20.0.5 on my local machine running Ubuntu 20.04 LTS everything seems to be working flawlessly, then I went to connect my Android mobile phone… only to discover that the server can’t be found on the LAN.
No sweat… I went back to https://docs.nextcloud.com/ , expecting to find some official documentation explaining ho…
Hi together,
About a year ago we have noticed, that our nextcloud cannot be accessed any more by the adroid client, when the smartphone was using a few specific, mostly small privat WIFI networks. A long error search brought us to the point, that this may be caused by the app trying to access via ipv6, but the host not responding on that channel. We are running the nextcloud using the DNS service inherent to our router (myfritz domain), so it is accessible from the web on some weird port (6971)…