NextCloud client unable to connect to server

[XtremXpert]

Hi, I did try to replace my owncloud by the sexiest nextcloud. I did it pretty easy on all my computer, except on my 2 macs. I got informed that it is not a valid url but and can not reach the status.php in https. Work fine with the web interface (status.php) on that computer, so...

The linux client is working fine and I dont have ant windows to check

Thank for help and considering fixing it

[marians]

I seem to have the same problem.

I can reach the status URL https://wolke.netzbegruenung.de/status.php just fine.

We are using SAML auth, if that is of any importance.

Edit: Also worth noting might be that the host is reachable both on IPv4 and IPv6, but the nextcloud service (AFAIK) is only listening on IPv4.

[marians]

FYI: I have no trouble using the ownclowd client on the same Mac with the same (nextcloud) server.

[XtremXpert]

Confirming marians, onwncloud client with nextcloud server fix it

[wiserweb]

Confirming that this issue affects OSX machines as of client release 2.3.2

FYI: Issue has also been reported on nextcloud.com forums here

[mgiammarco]

Please try to add end slash ("/") to your urls

[marians]

It doesn't work with a slash either.

[gerbsen]

(Disclaimer: I'm working with the same backend as @marians)

I've tried with the new version and now I get at least to the user credential stage. But this fails for my normal user password and for the app password with the error down below. We have SAML enabled. The current version of ownCloud can login, but does not save the session :(

[gerbsen]

Is there anything we can provide (debug messages) to fix this?

[raidenn]

Same problem here using MacOS and Version 2.3.3 (build 84)

[camilasan]

Are you still having this problem?

[marians]

Just checked with the current version 2.3.3.84.

I now see a different error:

Edit: which is the same problem @gerbsen reported in #4 (comment)

[peterleerental]

I have the same problem with NextCloud 13 server and Ubuntu 18.04 snap NextCloud client (version 2.3.3.). Can't get past initial screen where it says it can't connect to status.php on server.
SOLVED: The AppImage for Linux from NextCloud (2.3.3) works fine, but I don't like the temporary nature of AppImages so I looked around again and found that the PPA works as well: ppa:nextcloud-devs/client. Just go to https://launchpad.net/~nextcloud-devs/+archive/ubuntu/client. I suppose it must be a later version (it's 2.3.3-20180415.190957) than available from the Ubuntu 18.04 Software Centre.

[jamlazevedo]

I Have the same problem in my ubuntu 18.04 NextCloud client 2.3.3. and NextCloud 13

[Eeemil]

I have the same problem (can't even get to the credentials screen) in Ubuntu 16.04, NextCloud client 2.3.3 and NextCloud Server 13.0.2

[ComputerCarl]

I can connect on neither a Windows 7Pro x64 nor Windows 10Home computer using Nextcloud-2.3.3.1-setup.exe install.
I can connect using ownCloud-2.4.1.9270-setup.exe.

On both computers, I get the error;
Timeout while trying to connect to Nextcloud at https://computercarl.com/cloud/status.php
(it would also be super-nifty to be able to select the error text)

[jeremiah-s-putnam]

Same problem. Only does it on local network. Works fine from external. NAT problems?

Mobile apps work when on mobile data but do not work when on local LAN WiFi.

[ComputerCarl]

@jeremiah-s-putnam it doesn't seem like the same issue.
You could probably diagnose by pinging your Nextcloud address from inside and outside the network.
Is your cloud hosted inside your LAN?

[jeremiah-s-putnam]

Well, that's wired. This reply went to the wrong post. I don't know what happened.

Ping is fine. The cloud is hosted on a local machine on my LAN. Seems like a redirect problem or something like that.

[arthurvanzyl]

has anyone managed to get this resolved? I have the Same issue on my mac

[ciil]

@arthurvanzyl We've had this issue as well just now. The current nightly-build seems to work, though: https://download.nextcloud.com/desktop/daily/Mac/Installer/Nextcloud-qt5.9.2-2.5.0.20180710daily.pkg

[arthurvanzyl]

thanks @ciil

[arthurvanzyl]

running - version 2.5.0daily (build 20180710)

ok seem sbetter but now I am getting:

The server was unable to complete your request.
If this happens again, please send the technical details below to the server administrator.
More details can be found in the server log.
Technical details

Remote Address: 192.168.254.6
Request ID: IqfivBrqLEFfHbY0ZvHP

[scurrvy2020]

my problem was due to bruteforce protection. To fix it I had to remove the items from the oc_bruteforce_attempts table. You can find more here: https://help.nextcloud.com/t/solved-bruteforce-detection-blocking-my-ip-but-theres-no-oc-bruteforce-attempts-database/7652/2

[toweih]

Had the same problem. Root-Cause was IPv4/IPv6 hassle.
Try to put the IPv4-address into /etc/hosts as a quickfix.

[marians]

I don't see the problem any more in the latest Nextcloud client for Mac.

[frauhottelmann]

Had the same problem. Ping your server and see which IP it tries to reach. On my machine it tried to reach the IPv6 which was broken. I fixed my connection issues and voila it works from Linux in my local network.

[flukejones]

If your Nextcloud instance is behind a proxy you may need to set some config options. I required this in my config.php as I was using a reverse proxy to enforce https:

'overwriteprotocol' => 'https',

you may also need:

'htaccess.RewriteBase' => '/',

docs

[kbalicki]

I had similar issue today, the problem was DNS v6.

[stale]

This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[camilasan]

The release candidate for 2.6 has a new login flow: https://download.nextcloud.com/desktop/prereleases/Windows/nextcloud-2.6.0.5818-rc1-20190907.exe

Could you try it?

[trobotham]

same exact issue with the latest client for macos, I have completely disabled ipv6, it loads fine in browser but throws the error in the client.

Edit:

Found the issue, for me it was mod_headers, I had to add the following:

SetEnvIfNoCase ^Authorization$ "(.+)" XAUTHORIZATION=$1 RequestHeader set XAuthorization %{XAUTHORIZATION}e env=XAUTHORIZATION

[ghost]

Not sure what is going on, but I recently tried owncloud server again and the owncloud client and I'm not having this issue. So switching back to owncloud for now.

[misch7]

Have you tried the latest 2.6.0 release, best with NC server 16 or up?

The new Login Flow v2 works from NC 16 on and completely leaves the SAML authorization up to your NC server and standard browser.

Linux:
https://download.nextcloud.com/desktop/releases/Linux/Nextcloud-2.6.0-x86_64.AppImage

Mac:
https://download.nextcloud.com/desktop/releases/Mac/Installer/Nextcloud-2.6.0.20190927.pkg

Windows:
https://download.nextcloud.com/desktop/releases/Windows/Nextcloud-2.6.0-setup.exe

[ghost]

@misch7 Yes, I was on both the latest client and server.

[remixoff]

I have same issue. It's definitely not an error in server config: I tried to short look on demo server: all similar.
IPv6 not used.

[camilasan]

Hi, Could you try to run the most recent desktop client and server to check if you still have this issue? The latest version can be seen by checking https://nextcloud.com/install/#install-clients and https://nextcloud.com/install/#instructions-server respectively.

And then if you still have this problem, could you please share the desktop client logs?

• Since 3.1: Under the "General" settings, you can click on "Create Debug Archive ..." to pick the location of where the desktop client will export the logs and the database to a zip file.
• On previous releases: Via the command line: nextcloud --logdebug --logwindow or nextcloud --logdebug --logfile log.txt (See also https://docs.nextcloud.com/desktop/3.1/troubleshooting.html#log-files)

Thanks!

[bdcarr]

Hey, I'm on Windows client 3.1.2 and having the same issue, see screenshot.

I'm also using 3.1.2 on MacOS and getting the same error. Logs included for the windows version. Note I tried specifying a proxy server before changing it back to No Proxy, so there are logs there for that attempt.

The oc_bruteforce_attempts db table is empty. My nextcloud instance is behind the nginx reverse proxy provided by a linuxserver/swag docker container; I tailed all the nginx/fail2ban logs while trying to log in and there was nothing logged.

I can access the server with the Android app, and through the browser on the same devices as the desktop client. I can load /status.php through the browser too.

Also maybe of note, my internal DNS server is a pihole which has a dns entry mapping the duckdns domain to my local nextcloud host. I just now, while writing this comment, discovered that if I connect my desktop to a mobile hotspot I can log in with the desktop client. Not sure what that means.

[camilasan]

What is the server version?

I just now, while writing this comment, discovered that if I connect my desktop to a mobile hotspot I can log in with the desktop client. Not sure what that means.

Could you share the logs too?

[bdcarr]

Here's the debug archive after attempting login via hotspot: nc_via_hotspot.zip. It might be a bit noisy because I still have my account logged in to the client, so as soon as I connected to the hotspot it tried to reconnect to the nextcloud server with that account. At the same time I went to 'Add Account' and entered the server URL, which timed out (I assume because it was busy reconnecting). Once it had reconnected, I paused sync for the existing login and attempted adding another account again. It successfully reached the server and opened the browser login page, at which point I dumped the log.

Server version is 20.0.7.1 according to my status.php

btw, I'm getting the same issue on the linux client (whatever the version on the fedora repository is at the moment, 3.1.1 I think?). I just tried going through the Add Account workflow on my Android client (v3.15.0, installed via play store), connected to the same LAN as the devices that are having this problem with the desktop client, and it worked.

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[github-actions]

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!