Arch Linux

herrzinter

Member

Registered: 2019-12-15

Posts: 24

[SOLVED] nextcloud-client does not connect to server during setup

I try to setup the latest version of the nextcloud-client on my gnome3 desktop. If I put in the address (https) of my nextcloud server, the client reports a timeout for https://<address>/status.php despite this address being accessible from my browser. Setups of the nextcloud clients on android and windows work fine. I also tried the owncloud-client, but it has the same problem. I also looked at the debug log of the nextcloud log, but it didn't say anything more.

Any ideas, what the problem could be, or how I could investigate further? Could it be, that access of this address is somehow restricted for the desktop application, but now for my browser?

Last edited by herrzinter (2019-12-19 23:39:54)

qinohe

Member

From: Netherlands

Registered: 2012-06-20

Posts: 1,556

Re: [SOLVED] nextcloud-client does not connect to server during setup

Welcome to Arch, are you using your self-signed certificates, did you add the cert. to the system?
Is there a firewall on your server or any local firewall, did you add the clients address?
Are you adding the 'status.php' part to your server address? You shouldn't!

Not much more that can be wrong, client '2.6.1git' has no problems here...

herrzinter

Member

Registered: 2019-12-15

Posts: 24

Re: [SOLVED] nextcloud-client does not connect to server during setup

Thanks for your help qinohe! It turned out, that the nextcloud server I use does not allow ipv6 and for some reason the nextcloud client uses ipv6 by default, seemingly in contrast to other programs like eg. firefox. Disabling ipv6 system-wide solved the problem. In order to do that, I had to disable ipv6 for my wifi in the network manager AND follow the steps for the second method (ie. not the kernel method) in https://wiki.archlinux.org/index.php/IPv6#Disable_IPv6 .

qinohe

Member

From: Netherlands

Registered: 2012-06-20

Posts: 1,556

Re: [SOLVED] nextcloud-client does not connect to server during setup

Yes, that can also be a problem if you don't set your server to use ipv6 and create an entry for your VirtualHost with the ipv6 address.
I'm using the same method you do though.
Please mark your tread solved by editing your first post, thanks.