Kein Admin Panel nach Neustart

**web4you** · Jan 15th 2016

Debian 7.x neueste
i-mscp 1.2.10

Alles Domains laufen. Auch https://
Ich komme nun nach einem Neustart des Servers nicht mehr ins Admin Pannel. Siehe Anhang.

Gibts da irgend ne LOCK-Datei die ich löschen muss?

Ach ja und Kapazitätsprobleme dürfte ich auch keine haben siehe Anhang

**web4you** · Jan 15th 2016

Mein error log sagt:

root@web4you-server-02:/var/log/apache2/admin.web4you-server-02.web4you-gmbh.ch# tail -f error.log
[Fri Jan 15 13:09:35 2016] [error] proxy: HTTPS: disabled connection for (admin.web4you-server-02.web4you-gmbh.ch)
[Fri Jan 15 13:09:40 2016] [error] proxy: HTTPS: disabled connection for (admin.web4you-server-02.web4you-gmbh.ch)
[Fri Jan 15 13:09:40 2016] [error] proxy: HTTPS: disabled connection for (admin.web4you-server-02.web4you-gmbh.ch)
[Fri Jan 15 13:09:43 2016] [error] proxy: HTTPS: disabled connection for (admin.web4you-server-02.web4you-gmbh.ch)
[Fri Jan 15 13:09:43 2016] [error] proxy: HTTPS: disabled connection for (admin.web4you-server-02.web4you-gmbh.ch)
[Fri Jan 15 13:10:35 2016] [error] (111)Connection refused: proxy: HTTPS: attempt to connect to 5.9.210.214:4443 (admin.web4you-server-02.web4you-gmbh.ch) failed

Also ist da irgenwo ne Sperre - aber wo????

mafioso · Jan 15th 2016

Was sagt dein nginx-log?

**web4you** · Jan 15th 2016

Wow ist ja cool. Das Log redete seit dem Neustart gar nix mehr. Das Teil starten bringt den Freitag Abend wieder zurück.
Ehm da stellt sich die Frage, warum startet er das Teil nicht selber??

mafioso · Jan 15th 2016

Erstelle bitte mal ein Ticket. Anscheinend haben das Problem noch ein paar andere User..

**Nuxwin** · Jan 15th 2016

@Ninos

A ticket without further information will be totally useless.

@web4you

Did you tried to restart imscp_panel server at least?

**web4you** · Jan 16th 2016

I only startet nginx manualy. I did not restart my server again. I will check this later couse it is a "hot" server.

**Nuxwin** · Jan 16th 2016

Please see https://velenux.wordpress.com/…rarily-unavailable-error/

@Ninos I think it is related to redirect plugin. You could maybe have a look

mafioso · Jan 17th 2016

Hmm my plugin is just relevant to apache2, has not really something to do with nginx.. The problem is just, that nginx does not automatically start after server restart.

**Nuxwin** · Jan 17th 2016

@Ninos

With your plugin,, Apache proxy to nginx (proxy mode) but if nginx do not answer for any reason, Apache automatically turn off the proxy. Then, subsequent requests give error even if nginx can answer because Apache proxy is turned off... So please, read the link above and fix It is about retry and timeout parameters.

Kein Admin Panel nach Neustart

Share

Daily visitors