While I’m having connection with web interface and with android clients from the older smartphone, I have problems with configuring a new android smartphone.
I try to connect to the server, it says that the connection will be tested and then a error message “es ist ein unbekannter Fehler aufgetreten” (unknown error) comes.
I tried deleting bruteforce table with no success.
nextcloud server is 12.0.4
android client is 2.0.0
Could it be a problem with the selfsigned certificate?
Hi,
I have a similar problem.
I can login to my nextcloud with a browser on my phone, but the android app fails to login. (continues to attempt)
My next cloud server is: 12.0.4
Android phone OnePlus X with android 6.0.1
A ordinary windows PC login works very fine (browser and app)
I wanted to test if some other apps could connect to my server, I had the app oCloud.de installed at my phone and a short test gave me access to my nextcloud server. I then tested if the nextcloud could get access. Yes it can.
After a reboot of my phone is the nextcloud app still connected to the server.
Yes, it’s probably not related but the only real error visible on the server. Self-signed could perhaps be a problem. Are certificates from letsencrypt no option?
Can you connect to a demo server?
On rooted phones, you can check the logs, not sure if there are more ways for non-rooted phones:
I have tested your demo server nextcloud12. Here the mobilephone connects correctly. After testing the connection the client requests access to some functions on the phone and after granting them it connects.
On my server I can only see the testing of the connection, which aborts with “unknown error”.
I never had problems before with my nextcloud in the past when connecting. It runs over a year now. This new android phone is the first with troubles.
I had setup the server with open ssl and had never problems. I do not want to change my running system. There must be a reason why the new android device does not connect.
Spin up another vanilla NC server on your network with exactly the same setup, then see if that works.
If not, swap out the self signed cert for a proper one and test again. That’s as simple a test as you can do really without continuing to collect logs and waiting for the error to show up properly.
I don’t see nextcloud app logs (from the phone app) listed with your logs above, but @tflidd is particularly right in that you can get device logs too, but you don’t need to be rooted.
Using ADB with “allow debugging” enabled on the device may capture the error in more detail, but it takes a bit to set it up.