-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Home WiFi issue #865
Comments
Most likely your problem is with your router at home. Either way you should be able to clear your DNS cache on your router or remove the DNS entry for mydomain.tld and all should work :) |
You're absolutely right, the problem comes from the router behaving in a weird way. |
owncloud/core#13039 What should be done:
|
Thanks, I Didnt notice this one. |
Check if you can enable Hairpinning in your router. This solves most problem. The feature often also goes by the name Hairpin NAT or Loopback NAT. |
It looks like it can't :( |
OOPS, ERRATUM! "On the android device, mydomain.tld resolves in 192.16.1.1 which is my box's IP instead of 192.168.1.46 which is the IP of my server." |
Some routers can't access their own public IP, a friend of mine has one of those and it's a pain but nothing you can do besides getting a proper router and complaining to your ISP that that router is broken by design. |
Hi, I have the same issue here. I can connect to my ownCloud with android only if mobile-networking is enabled (I then had to confirm the self-signed certificate of my web-hoster), but not through my wifi. But I can connect with the desktop-client and with iOS-client (mobile and wifi). 26.06.2015 08:46:01DNSv6-Fehler: Der angegebene Domainname kann nicht von 2003:180:2:9000:0:1:0:53 aufgelöst werden. Fehler: Non Existent Domain (P008) 26.06.2015 08:38:58DHCP ist aktiv: 26.06.2015 08:38:58 WLAN android-8be89d5d51f70a2e 84:00:D2:B4:7F:FA 192.168.2.100 255.255.255.0 192.168.2.1; 192.168.2.1 86400 (H001) I think, the error appeared after I updated to the latest android-client. |
I have the same problem. And I do not think that it a problem of the router because other apps like foldersync work perfectly with webdav. When looking into logcat I found this line XXXXX.dyndns.org/2a02:8109:8000:58:1df3:5109:e419:bcc7 (port 443) after 5000ms: isConnected failed: ECONNREFUSED (Connection refused) The ipv6-adress is from my router, but why it is used? Other apps do not do this... I cannot disable IPv6 in my router (rented FritzBox). Using owncloud client with openvpn-connection from inside to outside and then inside works :-( |
So this seems to be an IPv6 problem. Please track here: #616 Thanks! |
Hi, I encounter a bug... which I think indeed comes from my Internet box ! So this is not a bug report for OC.
However, other users seem to encounter this issue (see http://forum.owncloud.org/viewtopic.php?f=24&t=25185&p=78127#p78127). Thus it could make sense bringing support for this particular situation.
So here is the problem:
I can perfectly sync my android device with my home OC server through friends WiFi and mobile data network.
BUT, it doesnt work with my WiFi at home.
It seems my Internet box doesnt let my android device access https://mydomain.tld/owncloud from the WiFi. On the android device, mydomain.tld resolves in 192.16.1.1 which is my box's IP instead of 192.168.1.46 which is the IP of my server.
Here is a workaround I found to enable using the OC app on your local WiFi: add an account to the OC app specifying the adress on my LAN: https://192.168.1.46/owncloud
It is clearly not a very convenient solution, but at least, it seems to work !
May be OC could have an option like an alternative address. Or just enable the user to specify multiple adresses separated by comas so the GUI does not get messy for basic usage.
PS: I'm using OC Android client 1.6.2 from f-droid and OC 7.0.0 server.
The text was updated successfully, but these errors were encountered: