After updating PhpPgAdmin on Debian users cannot log in to the control panel. The panel displays the following error messages
PhpPgAdmin by default displays all errors. Updates delete all the changes made by the control panel. To resolve the issue, change the following line in the configuration file /usr/share/phppgadmin/libraries/lib.inc.php:
Cannot log in with the password generated in ISPmanager
Perhaps, you run Mysql 5.7. Due to the changes in this version, you can log in as root only by connecting from the process which runs with permissions of the system root user.
To log into phpmyadmin enter user credentials of a certain database.
WWW domains are missing in the control panel
If a menu section is missing in ISPmanager, this means that the module is not uploaded. E.g. in ISPmanager the "WWW domains" module is not displayed, and the log file contains the following record:
- apachectl -M failed
- The WebModules, WebGroup, WebUser directives are missing in the ispmgr.conf configuration file.
- Configuration files of web-servers are missing in /usr/local/mgr5/etc/ispmgr.conf.d/.
IP address management
Cannot add the IP address to the server interface from the "IP address" section.
When adding an IP address from a new subnet, you need to add the address from the subnet to the server network interface. This error means that there are no IP addresses from the network 10.10.10.0/24 and you need to add one address manually.
The DefaultInterface directive in the ispmgr.conf configuration file (ISPmanager Lite) or ispmgrnode.conf (ISPmanager Business) defines the network interface where ISPmanager will search for the IP address.
Example: DefaultInterface bond0
Restart the control panel to apply the changes
Cannot start the control panel
Cannot start the control panel. When trying to start the panel from the console, we can see
Possible cause of this error is an invalid SSL certificate. Delete all the certificate files from the directory /var/www/httpd-cert/ and start the panel
PHP issues on CloudLinux
If PHP settings (such as memory_limit, etc.) are not applied in cron for user scripts, execute on the node
WordPress and SSL
ISPmanager doesn't configure Nginx for WordPress. You need to configure WordPress to avoid redirects. Set up the plug-in in WP "ssl-insecure-content-fixer" and select "HTTP_X_FORWARDED_PROTO" in the WP configuration form.