As a general advice, this is a bit risky because it only applies for one specific situation in a specific environment (hoster, local network) and can break your ipv6 connectivity (or enable ipv6 with a broken connection).
What is strange that it works on the mobile webbrowser. Not sure if the android client supports ipv6 or not??
I take by the fact you say you are trying to access Nextcloud via your WLAN that you are running your Nextcloud server at home? That being the case unless your router supports NAT Loopback your attempt to connect to NC will be getting directed to your primary router and hence will not work.
If my assumptions are correct you’ll need to set up an internal dns server to route internal requests to your domain to an internal ip address; for that I’d recommend dnsmasq as it’s relatively simple to set up.
Yes my nextcloud server running at home.
And with my wlan home i cannot connect to my server [quote=“dcrdev, post:7, topic:2626”]
hat being the case unless your router supports NAT Loopback your attempt to connect to NC will be getting directed to your primary router and hence will not work
Well I imagine the reason it’s not working via the app and connecting to the ip address is that the certificate is not issued to your ip, but your domain instead.
It’s good that you can reach your server via the ip though, it suggests the issue with the domain is dns related. It’s very difficult to say what the problem is without seeing your web server configuration, ssl configuration and how you’ve got dns set up.
a) I’m not sure overwrite.cli.url is what you think it is.
b) Why are you try to access the root domain in the above screenshot? You’re serving nextcloud from subdomain.domain.net/nextcloud.
c) I’m assuming you forgot to remove your domain from the above config - needless to say I have tried accessing that address and I can access it.
If your dns entry also resolves an ipv6 address, you should tell your server to answer ipv6 requests as well. On your home network, you have dual stack meaning that ipv6 is preferred. On the mobile network you only have ipv4. 2 possible solutions:
tell your server to handle ipv6: check with netstat -tlpuen if apache already listens to ipv6 (https://httpd.apache.org/docs/2.4/en/bind.html) and the address from the ssllabs-test really is the ipv6-address of your server (see ifconfig).
only use a dns name that resolves ipv4 only (you need to use a dynamic dns provider, such as no-ip.com (there are others as well)).