wwe
May 30, 2021, 7:55pm
2
My experience is the same, it looks Android prefers IPv6 (and Win10 as well from ~2020)
In your Fritzbox you can configure port sharing for IPv4 and IPv6 separately. maybe you just didn’t share your NC system for IPv6?
It’s crucial - for IPv6 you can’t share specific IP address… So far I understand you can only tie the share to specific MAC address (directly connected to Fritzbox) by choosing the system from a drop-down menu. I’m using docker so maybe this limitation doesn’t apply to your system.
some references:
Hallo, ich habe seit Jahren daheim eine Nextcloud laufen. Das technische Szenario sieht so aus:
Ich habe eine eigene Domain. Der myfritz-DNS-Eintrag meiner Fritzbox wird über einen CNAMe Eintrag an meiner Domain als intranet.meinedomain.com zur Verfügung gestellt. An der Fritzbox ist eine Portweitleitung für 443 an den Server zuhause eingerichtet. Anschluss ist ein Magenta VDSL100 Anschluss bei der Telekom.
Das klappt alles einwandfrei.
Sobald ich nun an der Fritzbox IPv6 aktiviere, kann ich …
I followed the guide here HowTo: Ubuntu + Docker + Nextcloud + Talk + Collabora by @KarlF12 . It’s working but since I am using a DDNS I can only access Nextcloud from my cellphone data connection. How do I configure it from here to get it to work on my local network as well? I have tried adding the server’s local IP address using OCC to trusted_domains and also localhost, and still I cannot access Nextcloud from the server itself.
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: …
hi @ncwarrior
in my case the problem is related to the myfritz service. Most guides are using some public dyndns providers. The difference is most likely that public dyndns providers don’t resolve ipv6 (AAAA) DNS records. In my situation I have to use AVM service as in Switzerland even residential DSL lines get semi-static IP (in opposite to Germany the provider is no obliged to assign new IP every 24h) - which violates DynDNS requirements.
From my experience there was no problem for Desktop F…
1 Like