500 error after 7.5.2. update

[WiseMetalhead]

After updating to version 7.5.2, I am getting 500 error when trying to enter the App Store. Also, my Cloudron.io account information is not displayed.

Sep 04 15:42:00box:apphealthmonitor app health: 8 running / 0 stopped / 0 unresponsive
[ServiceUnavailableError]: Response timeout
at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8)
at IncomingMessage.emit (node:events:513:28)
at IncomingMessage.emit (node:domain:489:12)
at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) {
code: 'ETIMEDOUT',
timeout: 20000
GET /api/v1/appstore/subscription 500 Internal Server Error Response timeout 20001.240 ms - 72

[nebulon]

Can you just double check via SSH from the server, if the appstore is reachable in the first place? curl -v https://api.cloudron.io/api/v1/apps

[girish]

@WiseMetalhead said in 500 error after 7.5.2. update:

Also, my Cloudron.io account information is not displayed.

This usually happens when unbound is down. See https://docs.cloudron.io/troubleshooting/#unbound

[WiseMetalhead]

@nebulon said in 500 error after 7.5.2. update:

Can you just double check via SSH from the server, if the appstore is reachable in the first place?

I get the following response. Is this how it's supposed to be?

*   Trying 165.227.67.76:443...
* Connected to api.cloudron.io (165.227.67.76) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):

@girish said in 500 error after 7.5.2. update:

This usually happens when unbound is down

The service itself is active, but I see repeated output in the logs.

● unbound.service - Unbound DNS Resolver
     Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor prese>
     Active: active (running) since Mon 2023-09-04 12:24:26 UTC; 42min ago
   Main PID: 940 (unbound)
      Tasks: 1 (limit: 9388)
     Memory: 11.1M
        CPU: 574ms
     CGroup: /system.slice/unbound.service
             └─940 /usr/sbin/unbound -d

Sep 04 12:24:26 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: start of service (unbound 1.13.1).
Sep 04 12:24:26 vlishchenkolp.fvds.ru systemd[1]: Started Unbound DNS Resolver.
Sep 04 12:24:26 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 12:30:09 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 12:36:16 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 12:41:48 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 12:47:27 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 12:54:35 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 13:02:30 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN
Sep 04 13:10:02 vlishchenkolp.fvds.ru unbound[940]: [940:0] info: generate keytag query _ta-4f66. NULL IN

[girish]

@WiseMetalhead said in 500 error after 7.5.2. update:

I get the following response. Is this how it's supposed to be?

you are supposed to get some json output. If you visit https://api.cloudron.io/api/v1/apps on the browser, you will see what the output is supposed to look ilke. Do you see that when do curl ?

[WiseMetalhead]

@girish said in 500 error after 7.5.2. update:

Do you see that when do curl

There is no output after the line TLSv1.3 (OUT), TLS handshake, Client hello (1):.

[girish]

@WiseMetalhead it's not able to connect to api.cloudron.io for some reason. Is there some firewall ? Otherwise, can you write to support@cloudron.io and we can investigate.

[WiseMetalhead]

Suddenly, after 1-2 hours, everything started working by itself. My hosting provider confirmed that there is no IP blocking on their end. I'll email you if the problem occurs again.