https://httpd.apache.org/docs/2.4/en/bind.html
In which file must i do the entry
"Listen [2001:db8::a00:20ff:fea7:ccea]:80" an in my case âListen [2001:db8::a00:20ff:fea7:ccea]:443â . In ports.conf or in my host or in apache.conf or in all?
No it does not correspondent.
The ipv6 address, which is resolved by your hostname *.dynv6.net, is ipv6 from the router (fritzbox).
The addresses in the output of ifconfig ist the ipv6 from the server.
And the server is behind the router.
Ok, i make an dynv6.net an A and AAAA entry with my ipv6 adress from nextcloud server
these are the entries, the other two are the entries from dyn-dynamic service.
Not sure what you are doing. 5405:: is no valid ip address, no idea where it is coming from. You should add the ip address you can see via ifconfig. You can try from an external host, if you can ping this ipv6.
Itâs also a bit strange that you have two different ipv6 addresses (of two different networks). Does your ISP provide ipv6 and you set up a tunnel on top?
I had the same problem. Everything working fine using 3G but not over wifi. Not a specific one, just using wifi in general made the client impossible to communicate. Didnât find any hint to the problem. No matter whether Iâm accessing via IPv6 or not. In fact the webservers log do not even show any attempt to access the site at all after connection has been tested. The phone does not try to connect and then states it took too long. I donât remember it happening before I changed my password but could be the case that the app did not work for a while using wifi.
However, I can use the Android-cilent over Wifi again after I activated 2-factor-authentification and generated an app-passwort for the Android-client. I think this is even better than storing the same password everywhere.
Thanks for the solution with the App-Pin
It also works with normal user authentication, I just created the App-Pin under the user settings.
I had the issues on iPhone and Android Apps and just changing from the normal user password to the App-Pin madi it working on WiFi. Still very strange that it works fine with the user password via mobile network
After a few days it now stopped working even with the App-Key
No idea whatâs wrong hereâŠ
The connection test in the app always works fine, but as soon as I try to connect I get an error that the server took too long to respond.
I have the same issues. Nextcloud is on home web server ubuntu 18.04. I can access my nextcloud from lan on any computer. Andriod app canât access over wlan but can access over mobile network.
I think this issue has nothing to do with Nextcloud app as I also canât access my web site using wlan from Android.
Note: My Android device has an ipv4 address on lan.
Possible that apache seeâs mobile devices as insecure?
Hi @Kenneth_Sartre
I had the exact same problems as you and solved it in this topic (linked at bottom)
I will just blindly assume that you use Cloudflare as well - try to disable the cloudflare Proxy and set the domain to DNS only. This way you can check if cloudlfare is causing the issue.
If this is not the case, are you using any other form for reverse proxy?
Please continue the thread here (as this is an old topic):
I do not use cloudflare. I have found that my issue has nothing to do with Nextcloud as my domain is not accessible from lan or wlan. Solely DNS issue.
Iâve got the same issue and i think i have the explanation but not the solution.
First, i will explain my case witch is, i think, the same as you.
My server is in my local network and is in demilitarized zone. So, for IPv4 connections, it is acceded by my public IPv4 address for outside the LAN and by itâs local IPv4 address from LAN.
Bur for IPv6 connections, itâs public address works no matter where you connect from.
Iâve got two DNS entry for it:
an AAAA record with the public IPv6 address of the server a
an A record for the public IPv4 address.
So my server can be acceded both by IPv4 and IPv6 from inside and from outside the LAN.
Now, let see what happens in the two cases you mentioned:
When my phone uses 4G for internet connection (IPv4 only due to my provider):
Both the android apps and Firefox uses IPv4 and the DNS gives the external address ; Every thing is working well in this scenarii ;
When my phone is connected by wifi on my LAN (IPv4 and IPv6 connections):
The android apps still use IPv4 and the DNS gives the external address witch is not reachable from the LAN ;
Firefox also use IPv4 and get stuck (shame on them to prefer A records on AAA ones) ;
Edge chromium uses IPv6 and work well.
My trick for PCâs is to use an hosts file under windows and linux to resolve local names and my server global name with IPv6 global address only.
For Android, there is no solution until the Nextcloud app will prefer use IPv6âŠ
Thank you this worked both for chromebook and my phone.
just needed to download via git and make install and make sure the etc/hosts files was up to date