Totally just remembered an old Android device that I havenât used in a while. Fired it up, installed the NextCloud client from F-Droid and I canât even connect to my server. On the âconnectâ screen when I put in my server I get the error âUnknown error occurred!â.
Going to try the beta client on this device real quickâŠ
For some odd reason, the majority of my Linux clients kept ticking away like nothing was wrong. My calendar applications were all syncing, my contacts to Thunderbird all worked, everything I tested seemed to work. Until I started poking at my Android device.
When both of those failed, I started thinking âWhat other devices do I have immediate access to that I can test?â I remembered a laptop shoved into the corner of the office that has an /old/ owncloud client. I fired it up not really expecting much. To my surprise it was complaining about permissions on the server. Huh.
chown apache:apache -R nextcloud/
TADA! Everything connects and works!
I feel so silly on one hand, but on the other I am kinda surprised nothing else mentioned that. Had I gotten that error on Android or any of the other clients, that would have been a 2 minute fix instead of a couple of hours poking around AndroidâŠ
Anyway. Solved now.
Thanks everyone for the awesome work done on NextCloud. Loving it!
Iâve got the same problem on my Nextcloud 10RC (hosted on a shared host on OVH).
Android Client is not working. I get an unknown error when the client check the URL. I canât see any message into log (even in debug).
All was working before the upgrade with Owncloud 9.1.0.15
I checked chown, all seems to be correctâŠ
What I donât understand is that
Windows Owncloud client is working (only sometimes a small error when validating URL which I need to do twice).
Web Interface is working
but
Android client is not working
Web interface on my android is working but I cannot downloid
Webdav doesnât seems to work (tested inside keepass2android)
I would just check all the permissions again on the nextcloud folder. Things like making sure all files are owned by the right user and that the config directory is writable by the user and stuff like that. If they are all correct, then I am not sure as the permissions were what bit me. However, I do completely understand your pain as I found it frustrating to get any type of error worth while out of Android.
I just run a chmod on all files and folder to be sure. No change.
All my files are owned by the same user/group. I canât change this since I am on a shared host and have only access to FTP to upload my files.
I donât have too much things on this server, I will try to start from scratch instead of upgrading from Owncloud.
But I still donât understand why all is working from a PC (web and client, didnât test webdav) and nothing is working from my mobile (web, client and webdav)⊠What is the difference between the two access mode!
I did some traces on my Android phone. I have seen only one difference. From apps that arenât working, there are no cookie in the request :
The cookie is set in this first request
When it is working there is a cookie.
Total commander is working because it does a first request without a cookie where he gets a 503 error and the cookie. It then does a new request with the cookie and all is working.
Just to say that I have the same behaviour with the Android client installed via Play Store.
Login step fails at url check with âunknown errorâ (not so helpfulâŠ).
Nextcloud 10.0.0, ovh shared hosting (might be related?).
Not really sure where to go from there, but available for testing!
Regards
@Fried can you give the beta version of the Android client a try and after the âunknown errorâ message post the log from the Android client (can be found in the settings screen)?
@TobiasKaminsky yes I can access the server from the webbrower on my phone. Desktop sync (with owncloud client 2.2.2) works well too.
@Andy Installed beta from F-Droid store, same issue. Sorry, but where can I get the logs? I canât see any settings screen, Iâm stuck at the login page.
@Fried would you post the servers URL, or DM it to me and @tobiasKaminsky so we can experience the issue & see if we can debug it? If the erros already accours at the server check we donât need any credentials etc. just the url.