AH00558: apache2: Could not reliably determine the server's fully qualified domain name

Docker Nextcloud version (eg, 20.0.5):

Nextcloud was wunning perfectly on Docker on behind Nginx reverse proxy manager. I then upgraded to the latest 27 release and got the error I need to update one version at a time. I then loaded the Docker image 26 and got:

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using Set the 'ServerName' directive globally to suppress this message

I tried again the 27 image and the error remained. Now I can’t even revert back to the original version as it says it is below the data’s version. The error persists whether I specify a domain name or use a local IP.

Here is my config.php:

$CONFIG = array (
  'htaccess.RewriteBase' => '/',
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'apps_paths' =>
  array (
    0 =>
    array (
      'path' => '/var/www/html/apps',
      'url' => '/apps',
      'writable' => false,
    1 =>
    array (
      'path' => '/var/www/html/custom_apps',
      'url' => '/custom_apps',
      'writable' => true,
  'instanceid' => '***************',
  'passwordsalt' => '***************',
  'secret' => '***************',
  'trusted_domains' =>
  array (
    0 => 'sub.domain.net',
  'datadirectory' => '/var/www/html/data',
  'trusted_proxies' =>
  array (
    0 => '', //this is the server's IP address
  'overwritehost' => 'sub.domain.net',
  'overwriteprotocol' => 'https',
  'overwritewebroot' => '/',
  'dbtype' => 'mysql',
  'version' => '',
  'overwrite.cli.url' => 'https://sub.domain.net',
  'dbname' => 'nextcloud',
  'dbhost' => 'nextcloud_db',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => '***************',
  'dbpassword' => '***************',
  'installed' => true,
  'updater.secret' => '***************',
  'enable_previews' => false,

Did something change between v25 and v26/27 that I need to adjust my settings? How do I resolve the apache2 error above?


I’m not a Docker expert, but I did a quick search, and found this: Do I Need to Address the AH00558 Warning in Nextcloud Docker with Apache's ServerName Directive? · Issue #2055 · nextcloud/docker · GitHub

I also found the following link with a more in depth explanation: https://stackoverflow.com/questions/46266527/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-doma

I added hostname: to the Docker and that error disappered. Now I still keep getting “Internal Server Error” with absolutely no logs even if enable debugging level 0. Is my database corrupted from the update to 25->27->26->27? Can I downgrade it to 25?

So you also had an internal server error which you didn’t mention in your initial post because you wanted to take care of the purely cosmetic Apache error first? :wink:

Anyways, I don’t use Nextcloud in Docker myself so I can’t really help, but generally you can’t downgrade Nextcloud.

I would recommend opening a new thread, since this looks like a separate issue. Use the support template and describe in as many deatils as possible what you did and how your setup looks like (Docker Compose Files / Docker run commands, Reverse Proxy Config (if you use one) etc. etc.

I thought that error was causing the internal server one. Good to know that it is innocuous for future reference.

I ended up spinning AIO docker from scratch. I will rely on it for the future since it has backups and seems more resilient.