NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Apache Boot
After setting up remote access on port 8086 I found apache wont boot. (In all honesty I had no idea how to setup remote access so surprise surprise something broke!)
This is the error I get...
Now I can't access frontview, is there any way of disabling remote access via ssh?
This is the error I get...
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.6 for ServerName
(98)Address already in use: make_sock: could not bind to address [::]:8086
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:8086
no listening sockets available, shutting down
Now I can't access frontview, is there any way of disabling remote access via ssh?
5 Replies
Replies have been turned off for this discussion
- Port 8086 is already used by ReadyNAS Photos II. You can't have two services using the same port.
You could use vi to edit /opt/p2p/conf/lnconfiguration.xml then reboot the NAS and you should regain access to the Dashboard. - Learning the hard way; thanks for the help. I've configured ReadyNAS photo's II to port 90 I presume that's ok and unlikely to cause more shutting down issues with apache? I nearly used 22 but someone had once told me ssh listens on that port?
- Yes SSH is on port 22.
So you edited the apache config file for ReadyNAS Photos II to use port 90 (note the port number is in two separate places in its config file)?
If you were to remove Photos II removing the config then re-install it it would be back to port 8086 again. That's why I preferred the option of changing the port used for Remote. - briefly...
To make it work I edited the /opt/p2p/conf/lnconfiguration.xml to tell it to do it's thing on port 90 rather than 80 and,after rebooting the NAS, I was able to restart apache
In detail
In trying to get this to work had editied the httpd.conf file to listen on port 90 before I read your post
I thought this would work but this had no effect which makes no sense to me
Q: why could the /lnconfiguration.xml be changed to port 90 and that work when changing the httpd.conf from 80 to 90 didn't?
The point is moot though because simply changing lnconfiguration.xml to port 90, changing the httpd.conf back to listen on 80 and restarting apache using the code below worked just fineapache-ssl -f /etc/frontview/apache/httpd.conf
It all worked happily ever after in the end. Big thank you. - Port 80 is used by http. Even if you could change that port it would be overridden either on the next reboot (perhaps) or on the next update.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
