Still down. Managing apps really shouldn’t be dependent on the app store being online. As it stands now, one cannot even enable/disable currently installed apps without occ access.
1 Like
Still down for me,stuck with a brand new installation trying to configure the apps. Wondering looking at this post if I should consider something else… Scracthing my head for a day, until I saw the logs and forums. I thought no way, online access blocks me at looking at local apps? but then this… please help with new installation. This is a complete blocker for installation, I can confirm
{"reqId":"0WvW0b8qqaZo8U2s5njd","level":2,"time":"2020-10-11T07:38:51+00:00","remoteAddr":"172.19.0.3","user":"admin","app":"appstoreFetcher","method":"GET","url":"/settings/apps/list","message":"Could not connect to appstore: cURL error 7: Failed to connect to apps.nextcloud.com port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36","version":"20.0.0.9"}I have the exact same problem, just installed nextcloud on my VPS, and I can’t really do anything with it because appstore is down
I am amazed at the way nextcloud communicates.
There is none!
No reference to github, twitter or facebook that there are massive problems with this.
I haven’t been able to install any apps for days… okay, I can tolerate that.
But leave users and admins in the dark?
Dozens of messages on github and help.nextcloud about aborted updates that get stuck in maintenance mode.
Not even the php installer works without setting the php timelimit to at least 1 hour high.
Get a CDN or a decent solution that scales.
Folks… this is how you break opensource.
1 Like
A little tooo pathetic, I think we have a small issue this weekend, for a small amount of early adopters. Every productive serveradmin should wait until 20.1 as in the past with all major release.
Just my five cents 
I agree, that a sticky or announcement would have been appropriate, though.
1 Like
This is not overdone!
Did you read the many issues and help entries in Github and here?
It concerns also admins like me.
And I should only update to 19.04.
After my update aborted, I restored my previously created snapshot.
I can handle that.
But i see that a lot other people cant.
1 Like
Same here. I even cannot use the “Apps” menu entry. It’s just running the circle infinitely without any message or information. A timeout doesn’t occur either.
1 Like
Same here 
Hi all, i’m newbie here, does anyone know, when apps.nextcloud.com will work? I’ve just installed nextcloud server, but i cannot install apps, because i have gateway timeout error. In journal it is: Could not connect to appstore: cURL error 28: Connection timed out after 60001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
It’s 22:53
I see that it is working now
1 Like
Not really … Seems to be a continuous On and Off 
2 Likes
I think the developers are aware of the situation now and they are working on it. Give them some time to bring up the server, perhaps with more hardware resources and/or a mirror. They probably think about some fall-back solutions since this is a very bad experience for everybody installing or updating Nextcloud.
3 Likes
It works for me
I am sorry Guys, but it is still an imposition. And yes, it is not up to me. I start the download from a server at Hetzner, where your download servers are located.
$ wget https://download.nextcloud.com/server/releases/nextcloud-19.0.3.zip
--2020-10-14 09:51:16-- https://download.nextcloud.com/server/releases/nextcloud-19.0.3.zip
Resolving download.nextcloud.com (download.nextcloud.com)... 2a01:4f9:2a:3119::181, 95.217.64.181
Connecting to download.nextcloud.com (download.nextcloud.com)|2a01:4f9:2a:3119::181|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 121315571 (116M) [application/zip]
Saving to: ‘nextcloud-19.0.3.zip.2’
nextcloud-19.0.3.zip.2 0%[ ] 360.00K 61.8KB/s eta 30m 15s
And yes, I know that you are already working on a CDN. But the problem is still there from the user’s point of view, no matter if you are working on it or not. And that for a very long time.
Is there really no short-term solution? Varnish Cache or Scale Horizontally (put more server in the dns) or use a temporary cdn or so on… I mean, come on. You really have HugoOps 
from me, but since it takes so long I can’t take it seriously. The problem does not exist since a few days, the problem exists since months.