Nextcloud not working after proxmox lxc container backup restore

[CarstenB]

The Basics

• Nextcloud Server version (e.g., 29.x.x):
  30.0.4.1
• Operating system and version (e.g., Ubuntu 24.04):
  Proxmox LXC container
• Web server and version (e.g, Apache 2.4.25):
  Apache/2.4.62 (Debian)
• Reverse proxy and version _(e.g. nginx 1.27.2)
  • replace me
• PHP version (e.g, 8.3):
  PHP 8.1.17
• Is this the first time you’ve seen this error? (Yes / No):
  yes
• When did this problem seem to first start?
  After reapply of a lxc container backup onto a new ssd
• Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)

• followed youtube instructions

• Are you using CloudfIare, mod_security, or similar? (Yes / No)
  no

Summary of the issue you are facing:

Ive created a backup of my lxc container running nextcloud.
Then i replaced my ssd drive to install a bigger one.
Reapplied the lxc container onto the new ssd.
Container in proxmox is starting without any troubble like the other VMs and containers ive moved (Openhab, unifi and Shinobi, just as info).

But i cant get any informations of the nextcloud itself, the webapp is not loaded at all.

IP’s etc. seems like to be the same.

Webapp under https// is dead.

Also autosync on android does not find the host.

Looks like nextcloud is not “running” at all.

Searched in google. Apache2 is running.

Configuration

Nextcloud

Configuration is unchanged due to the backup of the container.
Trusted domains etc are correct. Also tried disabling fail2ban, just to be sure.

The hole nextcloud is down.

[jtr]

What do the container logs indicate?

What appears when you exec into the container?

Etc.

[CarstenB]

The container itself does not indicate anything wrong i would say.
But im also not a skilled person on this stuff. I can login als “root” and all files, configs etc are available. Systemctl claims a lot of running threads (apache2, mariadb etc)

Im also able to run the confconsole from NC.

My guess is that something with the webapp/interface is wrong.

Is there something where Nextcloud is a bit pitty when moving to an other drive? Something like hostnames, zertifikates or similar?

Thanks

[CarstenB]

What helped me:

I was drigging arround and found in the apache2 error logs the message:

localhost:443:0 server certificate does NOT include an ID which matches the server name

I cant say why that error now forces the nextcloud down (maybe some can?) but i found in my nextcloud config.php a trusted domain entry that was called

www.example.com

That config was running for month before, now it crashed.

Ive removed it and, , there is nextcloud again.

Webinterface, access via Android “Autosync”, everything.