# AH00558: apache2: Could not reliably determine the server's fully qualified domain name **URL:** \ **Category:** šŸ“¦ Appliances (Docker, Snappy, VM, NCP, AIO)\ **Created:** [August 21, 2023, 5:14pm UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612 "2023-08-21T17:14:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vankyan](https://help.nextcloud.com/user_avatar/help.nextcloud.com/vankyan/32/49834_2.png) [@vankyan](https://help.nextcloud.com/u/vankyan)\ **Post date:** [August 21, 2023, 5:14pm UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612/1 "2023-08-21T17:14:40Z")
Docker Nextcloud version _(eg, 20.0.5)_: `25.0.4.1` Nextcloud was wunning perfectly on Docker on 25.0.4.1 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 172.26.0.3. 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`: ```auto $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 => '192.168.102.238', //this is the server's IP address ), 'overwritehost' => 'sub.domain.net', 'overwriteprotocol' => 'https', 'overwritewebroot' => '/', 'dbtype' => 'mysql', 'version' => '25.0.4.1', '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? Thanks ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [August 21, 2023, 6:11pm UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612/2 "2023-08-21T18:11:34Z")
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](https://github.com/nextcloud/docker/issues/2055) 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](https://stackoverflow.com/questions/46266527/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-doma) ---
**Author:** ![vankyan](https://help.nextcloud.com/user_avatar/help.nextcloud.com/vankyan/32/49834_2.png) [@vankyan](https://help.nextcloud.com/u/vankyan)\ **Post date:** [August 21, 2023, 6:58pm UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612/3 "2023-08-21T18:58:32Z")
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? ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [August 22, 2023, 5:33am UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612/4 "2023-08-22T05:33:03Z")
> [@vankyan](#): > > Now I still keep getting ā€œInternal Server Errorā€ 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? šŸ˜‰ 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. ---
**Author:** ![vankyan](https://help.nextcloud.com/user_avatar/help.nextcloud.com/vankyan/32/49834_2.png) [@vankyan](https://help.nextcloud.com/u/vankyan)\ **Post date:** [August 22, 2023, 11:01am UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612/5 "2023-08-22T11:01:47Z")
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. ---
**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\ **Post date:** [December 14, 2024, 12:57pm UTC](https://help.nextcloud.com/t/ah00558-apache2-could-not-reliably-determine-the-servers-fully-qualified-domain-name/168612/6 "2024-12-14T12:57:07Z")