-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Failed to connect to www.nextcloud.com #9932
Comments
That's not how it works. We use www.nextcloud.com only for general connectivity check. apps.nextcloud.com is another machine that serves the app store and the updates of those apps. updates.nextcloud.com is yet another machine that informs your Nextcloud about updates of the server. Seeing your first description it looks like there is a slight setup issue somewhere. As we can't reproduce the issue I would think it is outside the scope of the PHP code base. Thus I would ask you to reach out with your setup related question to the forums: https://help.nextcloud.com and check if other people also run into this. |
Thanks for your fast comment! |
GitMate.io thinks possibly related issues are #9509 (Can't connect Nextcloud to MariaDB with SSL), #6410 (Nextcloud 11 - Upgrade to 12 failed - ), #3735 (Recommend doing a external Security Scan over "scan.nextcloud.com"), #5882 (Swift as external storage fails in Nextcloud 12), and #9728 (Migrate from GitHub to git.nextcloud.com). |
I feel bad to post that it was related to my firewall settings. I only had some filters on the incoming network traffic and did not expect to have any problems with "outgoing" connections. However, the firewall somehow interferred with some targets which prevented my server to download git-repositories in many cases as well as connections to nextcloud.com (both often but not always). |
I am having trouble to connect to nextcloud.com from my server. When searching for this issue, I often find solutions where the server is not connected to the internet. Therefore I did some ping-tests:
So, what I know is that there is a very messy connection between my server and nextcloud.com while the overall internet connection of my server (dedicated server machine with gigabit-connection to the internet) seems to be very stable. Using my nextcloud over the internet works fine. Might it be that due to some misconfiguration, my server "spams" nextcloud.com and becomes therefore blacklisted for some time? The log entries do not seem to be too frequent unless I try to open the app store or try to look for updates.
Steps to reproduce
or: Try to open the app store in my nextcloud installation
Expected behaviour
nextcloud.com should return the current version which allows my installation to check if it's up-to-date
The app store should show up and show me the available apps
Actual behaviour
The requests often time out with the note:
The App store needs at least 10 seconds to show up and than just shows my installed apps and some app bundles (in german "App Pakete"). Clicking on the app bundles-button takes even longer. Finally, it shows three bundles which are all composed of already installed packages. The log is being flooded with the following log entries:
I am sure that it has already been working but I am not absolutely sure if it was with my current 13.0.1 or an earlier version.
Server configuration
Operating system:
Arch Linux
Web server:
Apache
Database:
MariaDB
PHP version:
7.2
Nextcloud version: (see Nextcloud admin page)
13.0.1 / stable branch
Updated from an older Nextcloud/ownCloud or fresh install:
Clean install of Nextcloud 13 (testing-branch) and one update to the officially stable 13.0.1 as soon as it became publicly available (update via pacman/Arch repositories)
Where did you install Nextcloud from:
Arch repositories
I installed the apps through the webinterface of nextcloud
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: No
Are you using encryption: No
Are you using an external user-backend, if yes which one: LDAP
LDAP configuration (delete this part if not used)
I think, this is not interesting. But when needed, I can add it later.
The text was updated successfully, but these errors were encountered: