Hello everybody, I have configured a Debian server based on this tutorial: https://www.howtoforge.com/tutorial/perfect-server-debian-8-jessie-apache-bind-dovecot-ispconfig-3/ I have made one adjustment - I am running ISPConfig as a virtual host on standard SSL port with valid certificate. Let's say I was accessing it on https://my.domain.org everything worked perfectly. Today I have upgraded my ISPConfig to latest stable version 3.1 using ispconfig_update.sh command. I let ISPConfig reconfigure my services and adjusted ispconfig.vhost to host ISPConfig as a virtual host on my.domain.org domain by adding ServerName my.domain.org directive. Since the upgrade I am not able to login and I am getting these error messages in log: Code: [Tue Oct 04 17:52:29.705065 2016] [:error] [pid 26331] [client 12.34.56.78:54679] script '/usr/local/ispconfig/interface/web/login/nav.php' not found or unable to stat, referer: https://my.domain.org/login/ [Tue Oct 04 17:52:29.707666 2016] [:error] [pid 26328] [client 12.34.56.78:54658] script '/usr/local/ispconfig/interface/web/login/nav.php' not found or unable to stat, referer: https://my.domain.org/login/ [Tue Oct 04 17:52:29.708352 2016] [:error] [pid 26334] [client 12.34.56.78:54694] script '/usr/local/ispconfig/interface/web/login/keepalive.php' not found or unable to stat, referer: https://my.domain.org/login/ [Tue Oct 04 17:52:29.710122 2016] [:error] [pid 26335] [client 12.34.56.78:54693] script '/usr/local/ispconfig/interface/web/login/datalogstatus.php' not found or unable to stat, referer: https://my.domain.org/login/ I am running Debian Jessie with all packages upgraded to stable version from official repository and configured according to manual mentioned above. Does anyone have an idea what might be wrong? There is an extra /login in the path to the scripts. All the scripts are in the /usr/local/ispconfig/interface/web directory, not /usr/local/ispconfig/interface/web/login/ directory, but I do not know, why I am facing this issue. Thank you very much for any hints. Best regards Tomas
I guess this has been answered about a dozen times now Try in the following order: 1) Restart browser. 2) Empty cache and delete cookies. 2) truncate (empty) the sys_session table. and if you sued a custom theme, then you might have to set the theme variable back to default in the interface config.inc.php file. The errors in the apache log are fine btw, nothing to worry about. There is nothing missing.
Ouch. Sorry for the duplicate thread then. My problem was a combination of two issues: Your three steps helped to resolve the login problem. I have also enabled apache-noscript jail in fail2ban which is detecting the errors posted above and banning my IP. As the login did not work, I tried to reload my browser and instantly got banned as the second reload exceeded the fails limit set in fail2ban. So the login works now, thank you very much. But the errors in my log seem that there might be something else wrong with my installation. I thing that there should not be any errors in apache logs, or? Thank you very much!! T.
The errors occur because the javascript loader from ispconfig tries to access files during login which are accessible only in the interface itself so that you see these messages is normal at the moment. we might add some code to block this requests when the user is not logged in yet.
