-
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
The server took too long to respond #516
Comments
How long is the server taking to respond? How much time goes since you click the 'connect' button til the error message appears? |
Server response is fine since i can use it with other accounts. |
Are you using nginx in your server? Likewise, could you share with us some logs from your server in the moment you try to log in? Thanks. EDIT: Still failing with version 1.5.7, I guess, |
Hi, sorry for late reply. Log from the reverse proxy: 111.147.129.214 - user1 [13/Jun/2014:23:34:43 +0200] "HEAD /remote.php/webdav/ HTTP/1.1" 200 0 "-" "Android-ownCloud" "-" web server: |
Hi, |
Hi, @fossxplorer . Sorry for replying so late. You can be sure, we really appreciate your assistance :) Could you check your nginx configuration? We are having some other problems with this lately. Please, check both the section about Nginx at http://doc.owncloud.org/server/6.0/admin_manual/installation/installation_source.html , and this comment : owncloud/core#9319 (comment) |
@fossxplorer Is it working for you now? |
i've just set up ownCloud 8.0 (using the package from the opensuse.org repo) on Apache 2.2 / Debian Wheezy(+updates) x86_64, and am facing a similar issue with the Android client. i can access my ownCloud instance via HTTPS in my phone's Web browser using mobile data, but the Android client says "The server took too long to respond", regardless of whether i specify the URL in the form "[fqdn]" or "[fqdn]/owncloud". |
Okay, i found the cause of the problem: i hadn't modifed the ownCloud |
@flexibeast great, good to hear. |
I have the issue lately with my owncloud installation. This suddenly started happening when I was in the configuration process. I personally suspect it had something to do with me playing around with server side encryption (which encrypts the entire storage by default, not by setting as advertised). I'm running on Apache with a self-signed certificate, whenever I point the Android app to my installation instance, it hangs around 10 seconds before coming up with the aforementioned error message. On my server I get the following messages: The result of calling status.php on my laptop is: The {fqdn} was already added to config.php so that shouldn't matter. The error message already appears without entering a user name. At first I thought there was an issue with the self-signed certificate, but I've imported it into my phone with CAdroid and there's a successfull 200 message on status.php so that shouldn't matter. I hope I find a chance soon to do some wiresharking on this with an intermediate computer. |
@tkteun maybe you can create a new server instance with a clean and simple installation to exclude encryption as a source for this problem? |
After updating to the latest version of owncloud and reinstalling the mobile client on Android I'm also getting this issue, how can I debug this?
|
I just installed ownCloud Server version 8.0.2 for the first time and although it responds well to web access, the Android mobile app constantly gives me this error. I do have the fqdn correctly added to the trusted domains in config.php, so that's not the cause of the problem in my case. I installed with all default options. I'm using postgres as the database. |
My phone was installed with all kind of factory bloatware, I haven't experienced this problem since I've installed Cyanogenmod 12. Similar errors in the use of DAV/CAdroid have disappeared. I think something was interfering with (homemade) SSL / certificates in the factory (hardened) firmware, but I'm unable to reproduce since I've reinstalled my phone. |
@peteruithoven , @GenomeAnalysts , what are your device models and Android versions? @tkteun , what is your device model? What Android version did it have before your changed to Cyanogenmod? |
I have a Samsung Galaxy S4 Mini (GT-I9195) which was supplied through Vodafone in The Netherlands. I guess it was running 4.4.4 or similar. This meant in my case that the phone had Samsung and Vodafone applications pre-installed and the regular rooting tools weren't functioning. I've experienced a lot of problems updating my bootloader using heimdall and finally got it to work with updated versions of both clockworkmod and heimdall. Now I'm running Cyanogenmod 12.1 on Android 5.1.1. |
My Galaxy S3 can only add a new server & account when WiFi is connected. Otherwise I get the "The server took too long to respond" message. |
+1 to this bug The client isn't even talking to the server: I get absolutely nothing in the remote server logs. Just how long is the remote timeout currently set to? Since mobile networks tend to have higher latency, wouldn't it make more sense to bump this value up? Setup is as follows: I can provide my server configs on request if you feel that it will help isolate the issue, but I feel like this problem lies in the app's intolerance for higher latency networks. Can also get my Android catlog if that could help isolate things, but I saw nothing of troubleshooting-worthy value in there when I was trying to solve this on my own. |
Actually realized my APN was on dual stack still, and the WiFi AP I tried before worked today, so I think this is possibly related to #616. Switching my APN to IPv4 only allowed the app to work as expected (might be a viable workaround for some people if their carrier supports it). Most cell carriers operate on IPv6 with tunneled v4 or have dual stack, so I wouldn't be surprised if something is choking up when operating with v6. Oddly enough I have no issues with v6/dual stack on my home WiFi, but this might be a good place to start looking for the cause of this issue. |
Hey guys, today I had the same issue after changing my passwords for both admin and user accounts. I've reenabled my account in desktop, then in my phone, and then tried to do that on MiPad, but received this error. I've found a solution. |
I have same problem except it only works when I connect my android to a VPN. |
In version 2.9, the ownCloud Android app switched to a new networking library. I'd assume this issue is gone. In case this happens again, please open a new issue. (too many things changed) |
After entering username/password i get 'the server took too long to respond'.
Although i'm able to use the same account with the sync client on Windows and Linux. Using another account just works fine.
Any idea what causes this?
Using the latest Android app 1.5.5
EDIT: tried on 3 different Android devices running 4.4.x
@davivel
The text was updated successfully, but these errors were encountered: