400 Bad Request returned by Apache (no Web GUI)

Mike · 28. September 2015

Hi guys, I recently rebooted my NAS and have come across this problem. I'm sure I've seen a similar problem before when it was rebooted but can't find the thread or a procedure to fix it.

Could anyone provide some help?

Thanks

Bad Request
Your browser sent a request that this server could not understand.

Size of a request header field exceeds server limit.

Cookie
/n

Apache/2.2.22 (Debian) Server at NAS.home Port 80

Mike · 28. September 2015

I've just found the fix by entering these commands:

omv-mkconf nginx
omv-mkconf php5fpm
service apache2 stop
service php5-fpm restart
update-rc.d -f apache2 remove
service nginx restart

Does anyone know if there's a permanent fix for this?

subzero79 · 28. September 2015

apt-get remove apache2

raulfg3 · 28. September 2015

the point is that you do not need Apache and Nginx on same machine.

PD: Post your OMV version, latest OMV use Ngix, OMV 0.x use Apache as web server.

TiredHornet · 31. Oktober 2015

I think I'm having the same or a similar problem here. Also got the "400 Bad Request" prompt when I try to open the webGUI. But I'm not quite sure about what the solution is. Do I just enter

Code

apt-get remove apache2

through CLI? Or do I need to do all the stuff that Mike did?

tekkb · 31. Oktober 2015

See if apache was enabled with this:
service apache2 status

If it is do this:
service apache2 stop
update-rc.d -f apache2 remove
service nginx restart

TiredHornet · 31. Oktober 2015

Okay,

I managed on my own. Just saw that there was another thread with a similar problem and I ran the following commands as suggested by subzero79.

Code

service apache2 stop
update-rc.d apache2 remove
service nginx start

Now everything is back to normal.

subzero79 · 31. Oktober 2015

Remove Apache with apt-get, is gonna come back and enable again in the next Apache package update

Jetzt mitmachen!