Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
I upgrade to 18.0.30 and after that phpmyadmin is not working. When I select database/Phpmyadmin show me a message "File not Found". This message show me on every domain.
Hi,
I've tried the step mentioned (restart the service, and plesk repair installation) but I still can't access phpmyadmin on domain page.
I'm on Plesk 18.0.30 (upgraded from 18.0.29) and CentOS 8.
Hi,
I've tried the step mentioned (restart the service, and plesk repair installation) but I still can't access phpmyadmin on domain page.
I'm on Plesk 18.0.30 (upgraded from 18.0.29) and CentOS 8.
Those that had a problem and restarting sw-cp-server service helped, could you post your OS, please? Did you have any errors or warnings on update to 18.0.30 (at least in /var/log/plesk/install/autoinstaller3.log)?
Operating system Debian 9.13
Mariadb:10.3.24
Plesk: 18.0.30 last update included
I found this entry in the logfile:
Trying to upgrade phpMyAdmin (files stage)... 'phpmyadmin' DB or 'phpmyadmin' DB user already exists, so phpMyAdmin configuration storage cannot be created. To create it, drop the respective DB and user, then run 'plesk repair installation' or reinstall the package.
This happened during upgrade from previous configuration storage, which was not removed: 'phpmyadmin_1HU90hTilWDF' DB and 'pma_1HU90hTilWDF' DB user.
Previous phpMyAdmin config was also preserved at /opt/psa/tmp/phpMyAdmin.config.php.save.
if I interpret this correctly, this entry must/should be deleted in the DB.
Note:
had this problem too, but I restarted the server and it worked again.
if I interpret this correctly, this entry must/should be deleted in the DB.
Note:
had this problem too, but I restarted the server and it worked again.
It's slightly weird that a restart was required.
Anyway, the message means that your phpMyAdmin installation now operates without configuration storage (settings will not be saved on server side, only in your cookies), unless you've already addressed this somehow. The message explains why this happened and how to resolve this situation. Please make sure no important data will be lost before dropping the pre-existing phpmyadmin DB.