Power Outage now Nextcloud does not work - using docker/portainer/nginx

Nextcloud version (eg, 29.0.5): 29.0.0-ls321 Build-date:- 2024-05-21T11:52:31+00:00
Operating system and version (eg, Ubuntu 29.04): Raspian - Bullseye
Apache or nginx version (eg, Apache 2.4.25): NGINX 2.11.2 / 1.21.4.3 PHP version _(eg, 8.3)_: 8.3.8

The issue you are facing:

Internal Server Error

The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.

Is this the first time you’ve seen this error? (Y/N):
Y

Steps to replicate it:

  1. No Clue how or why

The output of your Nextcloud log in Admin > Logging:

can't get into the nextcloud to pull it

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

Can not figure out how to get it in here

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

❯ Configuring npm user ...
useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
❯ Dynamic resolvers ...
❯ IPv6 ...
Enabling IPV6 in hosts in: /etc/nginx/conf.d
- /etc/nginx/conf.d/include/block-exploits.conf
- /etc/nginx/conf.d/include/assets.conf
- /etc/nginx/conf.d/include/ip_ranges.conf
- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- /etc/nginx/conf.d/include/force-ssl.conf
- /etc/nginx/conf.d/include/proxy.conf
- /etc/nginx/conf.d/include/ssl-ciphers.conf
- /etc/nginx/conf.d/include/resolvers.conf
- /etc/nginx/conf.d/production.conf
- /etc/nginx/conf.d/default.conf
Enabling IPV6 in hosts in: /data/nginx
- /data/nginx/proxy_host/1.conf
❯ Docker secrets ...
-------------------------------------
 _   _ ____  __  __
| \ | |  _ \|  \/  |
|  \| | |_) | |\/| |
| |\  |  __/| |  | |
|_| \_|_|   |_|  |_|
-------------------------------------
User:  npm PUID:0 ID:0 GROUP:0
Group: npm PGID:0 ID:0
-------------------------------------
❯ Starting nginx ...
❯ Starting backend ...
[6/23/2024] [10:25:40 PM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
[6/23/2024] [10:25:41 PM] [Migrate  ] › ℹ  info      Current database version: none
[6/23/2024] [10:25:41 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[6/23/2024] [10:25:41 PM] [Global   ] › ⬤  debug     CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
[6/23/2024] [10:25:41 PM] [Setup    ] › ℹ  info      Logrotate completed.
[6/23/2024] [10:25:41 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[6/23/2024] [10:25:41 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[6/23/2024] [10:25:42 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[6/23/2024] [10:25:42 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[6/23/2024] [10:25:42 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[6/23/2024] [10:25:42 PM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
[6/23/2024] [10:25:42 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[6/23/2024] [10:25:42 PM] [Global   ] › ℹ  info      Backend PID 163 listening on port 3000 ...
[6/23/2024] [10:25:42 PM] [SSL      ] › ℹ  info      Completed SSL cert renew process

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.

can not get it

For internal server errors, it’s the best to check the webserver’s logfiles. Can be a lot of things, e.g. if your data is on an external disk and is not mounted properly, the database not running, … and without that information there are too many options.

I moved into the applicance section, so some people with more knowledge of these docker ecosystems can give you more details straight away.

This should give a hint to the logfile of a nginx proxy, so if you can check this logfile already, that could be helpful (if the proxy generates the error, or the webserver within the docker container).

Thank you.

Please excuse the brevity. Sent from my mobile device.