Curl didn't produce a 200 status, is appstore reachable?

ℹ️ Support
, , ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Nextcloud Hub 9 (30.0.6)
  • Operating system and version (e.g., Ubuntu 24.04):
    • `Linux 5.15.167.4-microsoft-standard-WSL2 x86_64
  • Web server and version (e.g, Apache 2.4.25):
    • Latest aio release
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Latest aio release
  • PHP version (e.g, 8.3):
    • Latest aio release
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • Three days ago
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

Updated Docker Desktop to 4.39.0 (184744)
Shortly after received a message that there was a new release of AIO - 10… something
I stopped all containers via the AIO interface and applied the master and container updates.
After nothing came up… it is stuck trying to start Nextcloud container, Redis and DB are the only ones that come up.
Log for Nextcloud has this in it:

Curl didn’t produce a 200 status, is appstore reachable?

Over and over into infinity…all I can to is force a stop to the containers and if I try again, same issue.

I can go back to a backup from three days ago and it seems OK, but then at some point NC goes down for the same reason.

This instance is very stable and has been up for two years, I have been keeping up with all the updates.

I am aware of this: Aio-nextcloud fails to connect to appstore, but it seems this is from a while ago and I have rebuilt from mastercontainer pull in the last year…

Steps to replicate it (hint: details matter!):

  1. See above

Log entries

Curl didn’t produce a 200 status, is appstore reachable?

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.
2

Is there a firewall infront of your instance, blocking access ?
can you please post the full/raw log entry ?

3

Hi, thanks for the quick response.
I did not realize that restoring the backup would wipe the Nextcloud log (makes sense it would). All I have is the final recursive error message. " [Curl didn’t produce a 200 status, is appstore reachable?"

I find it very odd that failing to access the appstore is a single point of failure to start the entire instance…

I will have to wait until this starts again, or if I am asked to upgrade, as was the case when this started…

Yes, there is a Ubiquity UDM firewall in front of the instance, nothing has changed with the appliance or its config in months… what has changed in the latest AIO release to cause this?

Thanks.

4

I think I located the issue…

Is the App Store on a server in Finland?

If so, I had region blocked the country - call me paranoid, as I was getting a lot of unwanted traffic from there… Seems I am able to get to the app store pretty well now.

1 Like
5

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.