plugout.net

L.S.

I cannot enter into the webinterface after a powerfailure due to maintenance on the power network.
I can ssh into the NAS. The Transmission interface is also accessible...

Any suggestions?

There must be some files damaged preventing the apache server from starting
You could try to start it manually

Code: Select all

/usr/bin/httpd -f httpd.conf -d /etc

maybe it gives an error message if it fails.

If that doesn't work and assuming that the nas database is not corrupt, you could try to revert back to previous firmware version and install latest firmware version again.
Connect with ssh and check content of the the folder lacie-boot
It should contain 1 file with name "sda1boot" or "sda2boot"

If it is sda1boot
change it to sda2boot

if it is sda2boot
change it to sda1boot

reboot the nas, it will try to run the previous installed firmware version, check if the webinterface works. If not we need some more drastic measures

Found the problem... At the end of the httpd.conf the proxy.conf is included. This file went missing...
I commented it out and could start the webinterface with: /usr/bin/httpd -f httpd.conf -d /etc

So now I am looking for a more robust way of proxy- ing http://nas-hostname:9091/transmission/web/

Hi favroom,

Found the problem... At the end of the httpd.conf the proxy.conf is included. This file went missing...
I commented it out and could start the webinterface with: /usr/bin/httpd -f httpd.conf -d /etc

So now I am looking for a more robust way of proxy- ing http://nas-hostname:9091/transmission/web/

Instead of to use the directive "Include" you can try the directive "IncludeOptional"

Jocko,

Thanks. I have changed httpd.conf with your suggestion.

It also seems https is no longer working...
In the webinterface SSL/TLS has been enabled on port 443...

Any ideas?

Thanks!

Check if the file '/etc/SSL_fvdwsl.conf' is not empty.

if yes, you can try to disable the https feature and enable it again. Then, this file should be restored.