[Solved] OpenMediaVault-webgui disapeared

Dear all,

Further to the copy of a 500 GB backup through usb 3.0 external drive, I noticed a huge sollicitation of my processor (as far as I remember, there were 70 to 80% of my processor used by a "user process"). Then I decided to reboot my server thanks to the top right menu in the web-gui interface.
After it, I could'nt reconnect to web GUI despite my Transmission GUI was working and ssh acces too.
When I try to connect to [OMV.server.IP]:80 I have the following page :

Quote

It works!
This is the default web page for this server.
The web server software is running but no content has been added, yet.

When I try to connect to [OMV.server.IP]:443 I have a page saying that the connexion failed

I connected to a root console and send the following command :

# omv-firstaid

and reseted the https only acces I created to acces my server but nothing was working.

No improvement

I noticed that there were only "000-default" file in /etc/apache2/sites-enabeled but no openmediavault-wegui, neither in "sites-available" folder

I uninstalled apache2

# apt-get remove --purge apache2*

and reinstalled it

# apt-get install apache2

But I still face the same problem and can't find a solution.
If someone could help me, I would be glad !

Thanks in advance.

Thanks tekkbb for your reactivity, I tryed both of these commands the second returned :

root@OpenMediaVault:~# service nginx start
Starting nginx: nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()
nginx.
root@OpenMediaVault:~#

Unfortunately I still have the same issue to connect trough web-GUI

Well,

My problem is half solved. I digged in several treads related to various issues with webgui and tryed to change port 80 to 81 in omv-firstaid webGUI config. And it worked , I don't know how, I don't know why ... I'll wait for feedback, of yours if anybody have an idea of why ?

Thanks for your help

Here it is :

root@OpenMediaVault:~# netstat -tulpn | grep :80
tcp6       0      0 :::80                   :::*                    LISTEN      2199/apache2
root@OpenMediaVault:~#

As far as I understood I was investigating thanks to older posts edited when apache2 was used as web server instead of nginx. I think the message I got is the one from apache2 replying on port 80 instead of nginx. Can-I remove apache2 (I also use OwnCloud) ?
Oh and by the way, I didn't activate ipv6 at any time, how the hell can it be possible that it gets mentionned in this result ?
Thanks for your time.

I prefer to post the content of my systctl.com before doing anythig as it is all starting by # (comment ?)

#
# /etc/sysctl.conf - Configuration file for setting system variables
# See /etc/sysctl.d/ for additonal system variables
# See sysctl.conf (5) for information.
#


#kernel.domainname = example.com


# Uncomment the following to stop low-level messages on console
#kernel.printk = 3 4 1 3


##############################################################3
# Functions previously found in netbase
#


# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks
#net.ipv4.conf.default.rp_filter=1
#net.ipv4.conf.all.rp_filter=1


# Uncomment the next line to enable TCP/IP SYN cookies
# See http://lwn.net/Articles/277146/
# Note: This may impact IPv6 TCP sessions too
#net.ipv4.tcp_syncookies=1


# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1


# Uncomment the next line to enable packet forwarding for IPv6
#  Enabling this option disables Stateless Address Autoconfiguration
#  based on Router Advertisements for this host
#net.ipv6.conf.all.forwarding=1


###################################################################
# Additional settings - these settings can improve the network
# security of the host and prevent against some network attacks
# including spoofing attacks and man in the middle attacks through
# redirection. Some network environments, however, require that these
# settings are disabled so review and enable them as needed.
#
# Do not accept ICMP redirects (prevent MITM attacks)
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
# _or_
# Accept ICMP redirects only for gateways listed in our default
# gateway list (enabled by default)
# net.ipv4.conf.all.secure_redirects = 1
#
# Do not send ICMP redirects (we are not a router)
#net.ipv4.conf.all.send_redirects = 0
#
# Do not accept IP source route packets (we are not a router)
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#
# Log Martian Packets
#net.ipv4.conf.all.log_martians = 1
#

I followed your instructions tekkb,

root@OpenMediaVault:~# service apache2 stop
Stopping web server: apache2 ... waiting .
root@OpenMediaVault:~# update-rc.d -f apache2 remove
update-rc.d: using dependency based boot sequencing
root@OpenMediaVault:~# service nginx restart
Restarting nginx: nginx.
root@OpenMediaVault:~#

Then I typed :

root@OpenMediaVault:~# omv-firstaid
Updating web administration settings. Please wait ...
root@OpenMediaVault:~#

To change the default web interface to 80 but still faced the same page ("It works ! ..."). For now I reconfigured webgui access on port 81 but am still looking for a solution if you have other ideas / suggestions.

Many thanks to both of you for your help.

My mistake !
You're right !

root@OpenMediaVault:~# service apache2 status
Apache2 is NOT running.
root@OpenMediaVault:~#

I didn't try to access it from an other device. But just accessed from my phone after reconfiguring webgui on prot 80 thanks to omv-firstaid. I purged the cache of my browser and it's now functionning. I'm ashamed of this mistake of mine .

Thanks a lot guys for the solution, I'll pass the post on solved after writing a shor summary for the next readers. Have you got an idea of how it occured ?
Thanks again !

Here might be the solution you're looking for (well, at least it worked for me ...)
My problem was due to aa apache service running in parallel of nginx and listening port 80 instead of nginx. The message "It works ! ..." was a default message from apache.

I ran the following commands to stop apache and avoid its restart :

service apache2 stop
 update-rc.d -f apache2 remove
 service nginx restart

Then you got to purge the cache as I faced a non refresh of the page I was looking for on port 80 in my browser.

Thanks a lot tekkb and tiste for your help !