NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Connection refused to administration page
Hello, I have a problem... I have updated my NAS from 6.10.3 to 6.10.4 and since the update, the administration page doesn't work and I get ERR_CONNECTION_REFUSED. I have tried two computers and thr...
hmm it looks like that adding the image in the post is not working properly... here it is as attachment
Some further information. This is the log retrieved with journalctl -xe from the boot:
Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: [Sat Jan 30 23:23:40.419530 2021] [so:warn] [pid 4747] AH01574: module cgi_module is already loaded, skipping Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: AH00558: apache2: Could not reliably determine the ser ver's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress th is message Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443 Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443 Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: no listening sockets available, shutting down Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: AH00015: Unable to open logs Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: Action 'start' failed. Jan 30 23:23:40 NAS4-CASA-GP apachectl[4743]: The Apache error log may have more information. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2.service: Control process exited, code=exite d status=1 Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Failed to start The Apache HTTP Server. -- Subject: Unit apache2.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has failed. -- -- The result is failed. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2.service: Unit entered failed state. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2.service: Triggering OnFailure= dependencies. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: systemd-journald-audit.socket: Cannot add dependenc y job, ignoring: Cannot send after transport endpoint shutdown Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2.service: Failed with result 'exit-code'. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Starting The Apache HTTP Server (Safe Mode)... -- Subject: Unit apache2-safe.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2-safe.service has begun starting up. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Starting ReadyNAS System Daemon... -- Subject: Unit readynasd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit readynasd.service has begun starting up. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Starting Service for ddclient... -- Subject: Unit fvapp-ddclientr6.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit fvapp-ddclientr6.service has begun starting up. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Starting Service for vpnserver... -- Subject: Unit fvapp-vpnserver.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit fvapp-vpnserver.service has begun starting up. Jan 30 23:23:40 NAS4-CASA-GP apache2[4752]: AH00558: apache2: Could not reliably determine the serve r's fully qualified domain name, using ::1. Set the 'ServerName' directive globally to suppress this message Jan 30 23:23:40 NAS4-CASA-GP apache2[4752]: (98)Address already in use: AH00072: make_sock: could no t bind to address [::]:443 Jan 30 23:23:40 NAS4-CASA-GP apache2[4752]: (98)Address already in use: AH00072: make_sock: could no t bind to address 0.0.0.0:443 Jan 30 23:23:40 NAS4-CASA-GP apache2[4752]: no listening sockets available, shutting down Jan 30 23:23:40 NAS4-CASA-GP apache2[4752]: AH00015: Unable to open logs Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2-safe.service: Control process exited, code= exited status=1 Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Failed to start The Apache HTTP Server (Safe Mode). -- Subject: Unit apache2-safe.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2-safe.service has failed. -- -- The result is failed. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2-safe.service: Unit entered failed state. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: apache2-safe.service: Failed with result 'exit-code '. Jan 30 23:23:40 NAS4-CASA-GP vpnserver[4759]: The SoftEther VPN Server service has been started. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Started Service for vpnserver. -- Subject: Unit fvapp-vpnserver.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit fvapp-vpnserver.service has finished starting up. -- -- The start-up result is done. Jan 30 23:23:40 NAS4-CASA-GP systemd[1]: Started Service for ddclient. -- Subject: Unit fvapp-ddclientr6.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit fvapp-ddclientr6.service has finished starting up. -- -- The start-up result is done. Jan 30 23:23:41 NAS4-CASA-GP readynasd[4754]: readynasd log started Jan 30 23:23:41 NAS4-CASA-GP ddclient[4780]: WARNING: cannot connect to checkip.dyndns.com: 80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.com'
while this is from an attempt to restart the service done manually:
Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: Starting The Apache HTTP Server... -- Subject: Unit apache2.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has begun starting up. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: Reloading. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: nut-monitor.service: Supervising process 5019 which is not our child. We'll most likely not notice when it exits. Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: [Sat Jan 30 23:49:11.285913 2021] [so:warn] [pid 8341] AH01574: module cgi_module is already loaded, skipping Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: AH00558: apache2: Could not reliably determine the ser ver's fully qualified domain name, using fe80::eafc:afff:fee7:5bc5. Set the 'ServerName' directive g lobally to suppress this message Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443 Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443 Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: no listening sockets available, shutting down Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: AH00015: Unable to open logs Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: Action 'start' failed. Jan 30 23:49:11 NAS4-CASA-GP apachectl[8337]: The Apache error log may have more information. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2.service: Control process exited, code=exite d status=1 Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: Failed to start The Apache HTTP Server. -- Subject: Unit apache2.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has failed. -- -- The result is failed. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2.service: Unit entered failed state. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2.service: Triggering OnFailure= dependencies. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: systemd-journald-audit.socket: Cannot add dependenc y job, ignoring: Cannot send after transport endpoint shutdown Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2.service: Failed with result 'exit-code'. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: Starting The Apache HTTP Server (Safe Mode)... -- Subject: Unit apache2-safe.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2-safe.service has begun starting up. Jan 30 23:49:11 NAS4-CASA-GP apache2[8344]: AH00558: apache2: Could not reliably determine the serve r's fully qualified domain name, using fe80::eafc:afff:fee7:5bc5. Set the 'ServerName' directive glo bally to suppress this message Jan 30 23:49:11 NAS4-CASA-GP apache2[8344]: (98)Address already in use: AH00072: make_sock: could no t bind to address [::]:443 Jan 30 23:49:11 NAS4-CASA-GP apache2[8344]: (98)Address already in use: AH00072: make_sock: could no t bind to address 0.0.0.0:443 Jan 30 23:49:11 NAS4-CASA-GP apache2[8344]: no listening sockets available, shutting down Jan 30 23:49:11 NAS4-CASA-GP apache2[8344]: AH00015: Unable to open logs Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2-safe.service: Control process exited, code= exited status=1 Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: Failed to start The Apache HTTP Server (Safe Mode). -- Subject: Unit apache2-safe.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2-safe.service has failed. -- -- The result is failed. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2-safe.service: Unit entered failed state. Jan 30 23:49:11 NAS4-CASA-GP systemd[1]: apache2-safe.service: Failed with result 'exit-code '.
Maybe enter
# netstat -plan | grep :443
and see if something else is already listening on the port.
Thanks StephenB, I was trying exactly the same after finding the description of the error but the instructions I was trying to follow were requiring "ss", which apparently is not available on OS6...
So yes, indeed, there is something:
root@NAS4-CASA-GP:~# netstat -plan | grep 443 tcp 0 0 0.0.0.0:14443 0.0.0.0:* LISTEN 4772/vpnserver tcp 0 0 192.168.1.100:37642 54.183.248.191:443 ESTABLISHED 4538/leafp2p tcp 0 0 192.168.1.100:55880 54.170.242.218:443 ESTABLISHED 4552/xagent tcp 0 0 192.168.1.100:35436 52.52.117.56:443 ESTABLISHED 4538/leafp2p tcp6 0 0 :::443 :::* LISTEN 4632/domoticz tcp6 0 0 :::14443 :::* LISTEN 4772/vpnserver
it's the domoticz that I have installed two months ago. Very odd, it never gave any problem, it's strange that this conflict has come out now.
Ok I'll try to find how to change that port on domoticz then... thanks!!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
