Android: Server took to long to respond on IPv6

i can confirm this problem. the only solution i found is to turn off ipv6 in your network to avoid this, but for me this is a very very sad solution, especially if you cant turn off ipv6 in your AP (as mine)

I can confirm too. Using the v.1.41 app or the 20170209 beta version on Android 7 wields the same error. I have no problem whatsoever on networks with on IPv4.

This is pretty serious since IPv6 is the future and will be enable more and more, especially in business environments.

I can fix this by executing the following on my server which hosts the nextcloud:

ip -6 addr add <IPv6 address>/64 dev eth0
ip -6 route add default via fe80::1 dev eth0

this sets the correct ipv6 settings for my server. But it seems to be strange. Dhcps which offers only ipv4 are working fine..

Original request already has the main requirement: support ip6 since the app only supports v4 at the moment.

why is ipv6 not possible at the android app? Because ios app work fine on ipv6 wifi

The http library we are using does not support ipv6 :/

time to change the library or make this point clear to everyone.

I had the same issue with v.1.41. The issue was that the AAAA type (IP6 type record) was not configured with my DNS. Once I added the AAAA DNS record the app works great even via IP6. Before like many others I only had the regular A record setup for a regular ip and not not the AAAA IP6 record. This may help those that are having issues via their own domain name. Your IP6 address should be available via, the ifconfig command on the linux box you are running.

@parmdhoot That implies you have an IPv6 enabled server. Sadly, it's not yet the case for us at the moment and only IPv4 is available.

The app should not fail on networks with both IPv6 & IPv4 enabled if your server only has IPv4.

Is there a tracking issue for full IPv6 support? This is really a pain.

At the moment there is none, we look into the latest library release (https://github.com/nextcloud/android-library/issues/48) which may or may not be technically integrateable. If not we might have to write or own webdav client implementation (which would be a real effort to be taken...).

I hope everyone can get this resolved. Some clients are still having issues when they are on a IPv6 network.

i confirm this is failing for me in a mixed IPv4+IPv6 network when trying to connect to an IPv4-only server. this is really strange, and it is the only app behaving like this that i know of.

is there a workaround are using to deal with this?

i tried to disable IPv6 on the wlan interface (using those instructions, ie. echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6) but that had no effect.

i would urge people here to prioritize this task, as it makes the app completely unusable for users with an IPv6 upstream even if they are not using it. IPv6 adoption is growing really fast, reaching 85% with large providers like Verizon Wireless. 20% of the USA is now running IPv6, according to Akamai, and the numbers are similar in Europe.

Even extending connection timeout for 30 seconds more would be sufficient IMHO

@ser We extended the upload on latest (tomorrow build) dev version, so could you give it a try?

No response within the last month, therefore closing.
Please feel free to reopen with additional infos, if the problem still exists.

I was not able to reproduce the problem recently - it might be because it's gone or my network connection has improved. In summary: everything works now as desired.

Still it is broken for me.
If the folders are there in the App due to sync via mobile data conncetion, I cannot see the content from my home network. And if I click on the menu item "update" the mobile App takes ages.

And for mobile devices where I want to create a new link it sais after typing the URL that some error occured (very specific :D)

@twinkybot it is working on mobile data without problems, but on local/wifi connection not?

@tobiasKaminsky Yes correct. On mobile data without any issue. Outside of home via WIFI no problem. Home WIFI does not work.

I thought I got it goin on my cell phnoe for a while even on home network. But then I tried on my tablet with the newest Beta App from F-Store after installing Lineage OS, it failed to connect to the given URL.

Same here. I a was up to let deactivate IPv6 in my router but this isn't feasible either because my carrier Vodafone is provisioning my Box using TR069 and doesn't support ipv4only any longer. For me it works on mobile data but does not work on local wifi

Confirmed. Establishing a connection works just fine if I disable WiFi on my new phone and use mobile data instead. It does not work otherwise.

With NGINX and the config containing
listen [::]:443 ssl http2;
It works now.
But what I have noticed that TLSv1 has to be enabled?!? Which is sad. I'd rather only have TLSv1.2.

This is extremely annoying. My server has IPv6 and my domain has an IPv6 record, but my phone does not have an IPv6 connection, so I was not able to add my Nextcloud server.

If you can't easily fix this, please add a warning for IPv6 domains. This must be extremely frustrating for non tech savvy users.

As a workaround, I ended up creating an IPv4-only domain (think 4.nextcloud.example.com) and adding that domain to config/config.php on the server.

@AndyScherzinger some times ago you had a look if / how we can replace our http library. What was the outcome of this?

Can anyone post working NGINX settings?

I already use
`listen [::]:443 ssl http2;

I can upload/download via wifi in the Browser but not in the app. It seems to be an app issue and not an android issue.

Hope this will be fixed soon, as IPv6 problems are not new and should finally be fixed.
`

I do not have access right now but I will provide it next week. Hopefully :) Remind me plz if I forgot.

@powerriegel

So first the conf
nginx-nextcloud.conf.txt
second the ssl.conf
ssl.conf.txt

Hope this helps.
Please do not forget to replace and

@tobiasKaminsky he didn't get much done there, I'm afraid, the issue is stuck since March 2017. Yeah, I'm a vodafone user without IPV4 too, so I joined the club here 🥇

@jospoortvliet I fixed the IPv6 issue last week, so wait for RC1 ;)

But this is a shhhhhh :D

i am in that club as well AND i could bet there a myriads of people out there that have the same problem and don't even know its root cause

@twinkybot Thanks, I already used that config.
@mario Which RC1 version will contain the fix? Is the app being fixed or the server-side or both?

Android 3.0 RC1/RC2 should work

On Fri, 26 Jan 2018 at 08:48, Cornelius notifications@github.com wrote:

@twinkybot https://github.com/twinkybot Thanks, I already used that
config.
@mario https://github.com/mario Which RC1 version will contain the fix?
Is the app being fixed or the server-side or both?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/112#issuecomment-360707775,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAWsi0GbfrqI_ZNxeX_SZ3lpMFjclPdks5tOYNTgaJpZM4JIHvA
.

@powerriegel you can get it via google play store and register as beta user:
https://play.google.com/apps/testing/com.nextcloud.client

Fix works! NC Server 11.0.6 (production) on Debian Stretch, current Beta of the Android App. Took a photo at home (Wifi connected). Photo was immediately uploaded. Thumbs up!

👍 Thanks @powerriegel .