Skip to content
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

Client on Ubuntu: timeout while trying to connect to Nextcloud at status.php #12

Closed
mathiasconradt opened this issue Oct 12, 2017 · 5 comments

Comments

@mathiasconradt
Copy link

mathiasconradt commented Oct 12, 2017

This issue was also noticed by other users in the help forum at https://help.nextcloud.com/t/timeout-while-trying-to-connect-to-nextcloud/7429/5

I run Nextcloud 12 on a raspberry pi in my wifi network, and I can access it via browser just fine. But the desktop client fails on Ubuntu 17.04 Gnome with the timeout message seen in the screenshot below.
The client is netxtcloudclient version 2.2.4.5 from Snapcraft

The Nextcloud client on my Mac OS X on the other hand works fine with the same Nextcloud instance, can connect there without problems, and via the same host name (raspberrypi2).

screenshot from 2017-10-12 21-27-08

As you can see from the screenshot, the mentioned URL opens just fine in the web browser.

Related, but not exactly identical: #4

@mathiasconradt
Copy link
Author

mathiasconradt commented Oct 12, 2017

Update from my side: I just found that while entering the hostname, in my case “raspberrypi2”, does not work, as shown in my comment above, the IP address (IPv4) instead (in my case 192.168.178.39) works just fine.

When I do a “ping raspberrypi2” from my machine, I get this:

PING raspberrypi2(2003:c1:13cb:4c00:e41d:2f49:2c72:e8a8 (2003:c1:13cb:4c00:e41d:2f49:2c72:e8a8)) 56 data bytes

Maybe it’s a problem with the IPv6 and that it’s resolved like that.

@camilasan
Copy link
Member

Do you still have this problem @mathiasconradt ?

@rullzer
Copy link
Member

rullzer commented Jul 2, 2018

@mathiasconradt as far as I remember you used the appimage right?
There was an http2 and ipv6 issue on the old qt version there.

Should be fixed now.
If not please reopen.

@NightMachinery
Copy link

NightMachinery commented Dec 30, 2018

@rullzer I have this exact problem, too, even with explicit ip. (Things work fine in a browser but the client timeouts. The client is connected with no problems to my other nextcloud on another box. Both nextclouds are installed via snaps.)
I use the latest macOS client:

Version 2.5.0daily (build 20181112). For more information please visit nextcloud.com.
This release was supplied by Nextcloud GmbH
Built from Git revision 371001 on Nov 12 2018, 01:03:46 using Qt 5.9.2, OpenSSL 1.0.2m 2 Nov 2017

Here is the last lines of my nextcloud.log:

{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:01:21+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::step: Repair step: Install new core bundle components","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:01:21+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::step: Repair step: Repair invalid paths in file cache","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:01:21+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::step: Repair step: Rename folder with user specific keys","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:01:21+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::step: Repair step: Add log rotate job","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:01:21+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::step: Repair step: Clear frontend caches","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:01:21+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::info: Repair info: Image cache cleared","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:02:57+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::info: Repair info: SCSS cache cleared","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:03:31+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Repair::info: Repair info: JS cache cleared","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:03:31+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Updater::startCheckCodeIntegrity: Starting code integrity check...","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:03:57+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Updater::finishedCheckCodeIntegrity: Finished code integrity check","userAgent":"--","version":"13.0.7.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:03:57+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Updater::updateEnd: Update successful","userAgent":"--","version":"13.0.8.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:03:57+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Updater::maintenanceDisabled: Turned off maintenance mode","userAgent":"--","version":"13.0.8.2"}
{"reqId":"vrj41PJIx4n5msPi7uXq","level":1,"time":"2018-12-18T20:03:57+00:00","remoteAddr":"","user":"--","app":"updater","method":"--","url":"--","message":"\\OC\\Updater::resetLogLevel: Reset log level to Warning(2)","userAgent":"--","version":"13.0.8.2"}

As you see, the logs are for 12-18, while I tested the client today.
Update: I just tested with the latest daily release. Same result.

@Gsam333
Copy link

Gsam333 commented Nov 20, 2023

The timeout issue in connecting to Nextcloud on Mac is caused by the network connection configuration, which is set to "Specify proxy manually." To resolve this problem, you simply need to go to the "Proxy Settings" in the "Network" section of the settings and change it to "No Proxy." This will fix the issue and allow you to connect to Nextcloud without any timeout errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants