Ok then maybe there was a temporary problem witht the aio-apache container and the reboot fixed it. By the way, I see that aio-apache uses port 11000. Anyway, I’ll see what happens next time.
Everything now works as before although there is a container in the root environment that uses port 443 (Nextlcoud AIO runs rootless in a user context).
It seems like a forced Windows reboot may have disrupted Apache’s functionality in the Nextcloud AIO instance, leading to a persistent 500 Internal Server Error when attempting to start Apache.
1 Like