NextCloud - Internal Server Error

Ok, let's start from the beginning:

Post here inside a code box, the YML you used on the stack (hide sensible data).

Then, provide some more info about what guide did you follow;

On what hardware/software are you launching Nextcloud

Anything that can help us to help you

You can trust that none of us have crystal balls that see your setup.

Also FYI, I had some issues with the DB when I first installed Nextcloud because I was using special characters in the password, for eg ($%!%?=)

Only fixed it by using alphanumerical password only, for eg (Th15i54Pa55W0rD)

And, yeah, starting from scratch will save a lot of time.

Hello Everybody,

I still have the same problem, sometimes when i reboot the server, i have this error while retstart the docker service.

Now nextcloud doesn't work at all...

Zitat von Okipa

Hello Everybody,

I still have the same problem, sometimes when i reboot the server, i have this error while retstart the docker service.

Now nextcloud doesn't work at all...

This type of posts, doesn't help in any way to give any assistance.

Either explain, in detail, what is happening or, at least post some outputs of logs or some screenshots of what's going on.

Please guide me how to add an external drive on nextcloud !

Thank you very much alone !

Zitat von Soma

This type of posts, doesn't help in any way to give any assistance.

Either explain, in detail, what is happening or, at least post some outputs of logs or some screenshots of what's going on.

Sure you're right !

So i Have that error

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.

Where I can find log details?

I have a file inside nextcloud app data wich have .log extensions, but I can't open it or there is nothing inside.

Thanks

Zitat von Okipa

Where I can find log details?

Run and post inside a codebox

 docker logs -f nextcloud 

To quit, press Ctrl+c

I Have this when connected to ssh on the server

root@homeserver:~#  docker logs -f nextcloud 
Error: No such container: nextcloud

And when I try to launch a console to portainer :

root@8c9c5995dbc9:/#  docker logs -f nextcloud
bash: docker: command not found
root@8c9c5995dbc9:/#

Zitat von Okipa

I Have this when connected to ssh on the server

docker ps -a

Logs are too long, please find attached

Zitat von Okipa

Logs are too long, please find attached

8c9c5995dbc9        ownyourbits/nextcloudpi-x86    "/run-parts.sh 192.1…"   3 years ago         Up 6 hours                    0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:4443->4443/tcp                                                                                                                     nextcloudpi

You're running nextcloudpi that isn't, in any place of the forum, a supported guide.
You should be asking for help in their forum/github.

I can't help you, sorry.

Many Thanks for your support, I will try this way

Hello to everyone.

I tried for several days to solve the same problem of the thread ("Internal server error"), without success, so I'm here to ask for help.

This string appers only when try to connect to the subfolder in the URL: https://mysubdomain.domain.url/nextcloud.

I followed this guide: [How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose.

I modified some entries, because in the first time I received errors from Certbot (main domain cannot receive others certificates...). Then these errors was solved. This is now my .yml file:

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Rome #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-uuid-81c06d5b-9da1-431b-8031-4bb369fa03d9/Docker/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-uuid-81c06d5b-9da1-431b-8031-4bb369fa03d9/Docker/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
    ports: # uncomment this and the next line if you want to bypass the proxy
      - 450:443
    restart: unless-stopped
  mariadb:
    image: ghcr.io/linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=[omissis]
      - TZ=Europe/Rome
    volumes:
      - /srv/dev-disk-by-uuid-81c06d5b-9da1-431b-8031-4bb369fa03d9/Docker/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped
  swag:
    image: linuxserver/swag         #swag is the replacement for letsencrypt (see link below)
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1001 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Rome
      - URL=strangled.net #insert your domain name - yourdomain.url
      - ONLY_SUBDOMAINS=true
      - SUBDOMAINS=[omissis],
      - VALIDATION=http
      - EMAIL=[omissis] # define email; required to renew certificate
    volumes:
      - /srv/dev-disk-by-uuid-81c06d5b-9da1-431b-8031-4bb369fa03d9/Docker/appdata/swag:/config  #/srv/dev-disk-by-label-disk1 needs to be adjusted
    ports:
      - 444:443
      - 81:80
    restart: unless-stopped

Then, followed some tips of this thread ( Soma), I changed the password of database in the docker-compose.yml file, and create a new one without special characters.

To give more additional information,

docker ps -a

give this:

CONTAINER ID   IMAGE                           COMMAND   CREATED          STATUS             PORTS
                                                NAMES
9b22ebaeb447   ghcr.io/linuxserver/nextcloud   "/init"   18 minutes ago   Up 18 minutes      80/tcp, 0.0.0.0:450->443/tcp, :::450->443/tcp                              nextcloud
42a4e02f82c6   ghcr.io/linuxserver/mariadb     "/init"   18 minutes ago   Up 18 minutes      3306/tcp
                                                nextclouddb
366bf685142b   linuxserver/swag                "/init"   2 hours ago      Up About an hour   0.0.0.0:81->80/tcp, :::81->80/tcp, 0.0.0.0:444->443/tcp, :::444->443/tcp   swag

Now, if I try

docker logs -f nextcloud

I have this:

PHP Fatal error:  Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /config/www/nextcloud/cron.php:192
Stack trace:
#0 {main}
  thrown in /config/www/nextcloud/cron.php on line 192
PHP Fatal error:  Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /config/www/nextcloud/cron.php:192
Stack trace:
#0 {main}
  thrown in /config/www/nextcloud/cron.php on line 192

I don't understand the problem: "$server must not be accessed before initialization".

Thank you in advance.

This is my OMV system:

Versione 6.3.8-1 (Shaitan)

Processore Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz

Kernel Linux 6.1.0-0.deb11.5-amd64

I think my problem is that I have a subdomain with an unsupported provider of swag (https://docs.linuxserver.io/ge…tion-with-a-wildcard-cert). I'll try to get a Cloudflare domain.

Zitat von jobal

I think my problem is that I have a subdomain with an unsupported provider of swag

The internal error is from Nextcloud to MariaDB communication.

Zitat von jobal

ports: # uncomment this and the next line if you want to bypass the proxy

- 450:443

Did you made the initial configuration via http://IP_of_LAN:450 from a PC on the same LAN?

Thanks for your replay.

Zitat von Soma

Did you made the initial configuration via http://IP_of_LAN:450 from a PC on the same LAN?

No, I didn't! I uncommented the proxy line only to try another way: also with it commented I had the same problem.

In the meanwhile, I have troubles also with Cloudflare (but this is another thing).

So, abandoning Cloudflare, tomorrow I will reproduce the configuration that's on my previous post and connect to http://nextcloud_IP_LAN:450. After, I'll post here the result.