Uploaded 200 images - 503 Service Unavailable

[tomasenskede]

Why are my nextcloud so instable…

[jtr]

You failed to fill out the support template so we have zero information about your environment or installation.

Check:

• Your web server (and fpm if applicable) error logs
• Your Nextcloud log

[bb77]

503 means that the server is unable to process the request, usually because the server is overloaded, which can happen for a variety of reasons.

Since you offer absolutely no information in your post, I can only add a few very general tips:

1. Run htop on the server and see which processes are using the most CPU when uploading images.

2. Take a look at the Server tuning guide and see if you can optimize your setup.

If that doesn’t help, fill out the support template, as @jtr already suggested, and provide as much information as possible, otherwise no one will be able to help you.

[tomasenskede]

I found something strang…

From pfsense/HAPROXY-firwall:

• curl -vI https://192.168.1.30

• connect to 192.168.1.30 port 443 from 192.168.1.1 port 14453 failed: Connection refused

• Failed to connect to 192.168.1.30 port 443 after 0 ms: Couldn’t connect to server

  0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0

• Closing connection
  curl: (7) Failed to connect to 192.168.1.30 port 443 after 0 ms: Couldn’t connect to server

but from another computer in LAN i get connected… so why isnt connections from my firewall accepted by the nextcloud server… the two other nextcloud servers accept connections from the firewall.

root@storage ~# curl -vI https://192.168.1.30

• Trying 192.168.1.30:443…
• Connected to 192.168.1.30 (192.168.1.30) port 443 (#0)
• ALPN: offers h2,http/1.1
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• CAfile: /etc/ssl/certs/ca-certificates.crt
• CApath: /etc/ssl/certs
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
• ALPN: server accepted http/1.1
• Server certificate:
• subject: CN=storage
• start date: Aug 5 12:43:46 2024 GMT
• expire date: Aug 5 12:43:46 2025 GMT
• subjectAltName does not match 192.168.1.30
• SSL: no alternative certificate subject name matches target host name ‘192.168.1.30’
• Closing connection 0
• TLSv1.3 (OUT), TLS alert, close notify (256):
  curl: (60) SSL: no alternative certificate subject name matches target host name ‘192.168.1.30’
  More details here: curl - SSL CA Certificates

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.