Power surge hit, now page won't load

ℹ️ Support
1

Nextcloud version : 27.1.5.1
Operating system and version : Fedora Linux 39 (Server Edition)
Apache or nginx version : Apache/2.4.58
PHP version : PHP 8.2.13

I have was running my server (No active use, idling) before a power surge hit and tripped our power breaker, now the page won’t load anymore. I check systemctl httpd status and get :

Dec 16 16:42:25 fedora server systemd[1]: Starting httpd.service - The Apache HTTP Server...
Dec 16 16:42:25 fedora server (httpd)[4215]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS
Dec 16 16:42:25 fedora server httpd[4215]: AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::219:99ff:fea0:12a7%enp0s25. Set the 'ServerName' directive globally to suppress this message
Dec 16 16:42:25 fedora server httpd[4215]: Server configured, listening on: port 443, port 80
Dec 16 16:42:25 fedora server systemd[1]: Started httpd.service - The Apache HTTP Server.

Now I check my config files, because thats where I thought the issue was, and this is what I see

<VirtualHost *:80>
DocumentRoot /var/www/html/nextcloud
ServerName server.com
 <IfModule mod_headers.c>
      Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
    </IfModule>
RewriteEngine on
RewriteCond %{SERVER_NAME} =server.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
Include /etc/httpd/conf/httpd-le-ssl.conf

and for the port 443

<IfModule mod_ssl.c>
<VirtualHost *:443>
DocumentRoot /var/www/html/nextcloud
ServerName myserver.com
 <IfModule mod_headers.c>
      Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains"
    </IfModule>

SSLCertificateFile /etc/letsencrypt/live/nextcloudctwice.cloudns.eu/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/nextcloudctwice.cloudns.eu/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>

in short: Nothing out of the ordinary.

Is this the first time you’ve seen this error? Yes

The output of your config.php file in /path/to/nextcloud:

<?php
$CONFIG = array (
  'instanceid' => '',
  'passwordsalt' => '',
  'secret' => '',
  'trusted_domains' =>
  array (
    0 => 'ID',
    1 => 'server.com',
  ),
  'datadirectory' => '/var/www/html/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '27.1.5.1',
  'overwrite.cli.url' => 'IP',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'admin',
  'dbpassword' => 'password1',
  'installed' => true,
  'maintenance' => false,
  'theme' => '',

The output of httpd error_log:

[Sat Dec 16 13:19:08.806978 2023] [lbmethod_heartbeat:notice] [pid 1783:tid 1783] AH02282: No slotmem from mod_heartmonitor
[Sat Dec 16 13:19:08.809204 2023] [systemd:notice] [pid 1783:tid 1783] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Sat Dec 16 13:19:08.814992 2023] [mpm_event:notice] [pid 1783:tid 1783] AH00489: Apache/2.4.58 (Fedora Linux) OpenSSL/3.1.1 configured -- resuming normal operations
[Sat Dec 16 13:19:08.815046 2023] [core:notice] [pid 1783:tid 1783] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Sat Dec 16 16:19:00.088758 2023] [mpm_event:notice] [pid 1783:tid 1783] AH00492: caught SIGWINCH, shutting down gracefully
[Sat Dec 16 16:19:01.199343 2023] [suexec:notice] [pid 3686:tid 3686] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using  (my external.ip). Set the 'ServerName' directive globally to suppress this message
[Sat Dec 16 16:19:01.223702 2023] [lbmethod_heartbeat:notice] [pid 3686:tid 3686] AH02282: No slotmem from mod_heartmonitor
[Sat Dec 16 16:19:01.224753 2023] [systemd:notice] [pid 3686:tid 3686] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Sat Dec 16 16:19:01.228447 2023] [mpm_event:notice] [pid 3686:tid 3686] AH00489: Apache/2.4.58 (Fedora Linux) OpenSSL/3.1.1 configured -- resuming normal operations
[Sat Dec 16 16:19:01.228481 2023] [core:notice] [pid 3686:tid 3686] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Sat Dec 16 16:42:24.511530 2023] [mpm_event:notice] [pid 3686:tid 3686] AH00492: caught SIGWINCH, shutting down gracefully
[Sat Dec 16 16:42:25.625280 2023] [suexec:notice] [pid 4215:tid 4215] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using (my external.ip). Set the 'ServerName' directive globally to suppress this message
[Sat Dec 16 16:42:25.649573 2023] [lbmethod_heartbeat:notice] [pid 4215:tid 4215] AH02282: No slotmem from mod_heartmonitor
[Sat Dec 16 16:42:25.650698 2023] [systemd:notice] [pid 4215:tid 4215] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Sat Dec 16 16:42:25.653920 2023] [mpm_event:notice] [pid 4215:tid 4215] AH00489: Apache/2.4.58 (Fedora Linux) OpenSSL/3.1.1 configured -- resuming normal operations
[Sat Dec 16 16:42:25.653945 2023] [core:notice] [pid 4215:tid 4215] AH00094:

I’ve already tried restarting the httpd server and the database, and the entire server, no luck there either.

Any help much appreciated.

UPDATE: It works by typing in the ip address directly, accessing over http,
Security & setup warnings tell me:

Your web server is not properly set up to resolve "/nextcloud/ocm-provider/". This is most likely related to a web server configuration that was not updated to deliver this folder directly. Please compare your configuration against the shipped rewrite rules in ".htaccess" for Apache or the provided one in the documentation for Nginx at it's documentation page ↗. On Nginx those are typically the lines starting with "location ~" that need an update.

Will check out, update soon with more questions

2

What is the status of php-fpm? Is it running?

Much luck,
ernolf

1 Like
3

active and running,

thanks for the best wishes

4

Your webserver cannot determine its own A record. The IPv6 address it recognizes

does not match the servers FQDN as defined in the resolv and hosts file.

%{SERVER_NAME}% refers to a constant which is loaded in the apache config file. It can either be hardcoded in there or it can get it from the hosts own resolv or hosts file.

2 Likes
5

Thanks for the answer, after checking the /etc/hosts file to make any changes and:

# Loopback entries; do not change.
# For historical reasons, localhost precedes localhost.localdomain:
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

# My external IP address 
external.ip   server.com

It works now!!! Thanks alot again for the small hint.

6

Great to see that! I would recommend though that you keeps only LAN adresses in the hosts file. There is no need for the host itself to “move” all the way to your public IP to hit itself. The LAN adress should be enough. Usually there is more speed available up and down on LAN, than on the Public IP.

In fact then if you have your own DNS server, or can setup custom DNS records in your router, I would suggest to move this there. However as your setup now works, might be a good reason to not touch it.

7

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.