phpMyAdmin auto-update script deletes folder in ISPConfig 3.3 – need safe update method

Hello,

I’m running a web server with ISPConfig 3.3 multiserver setup. phpMyAdmin is installed separately on the web server.

After the latest ISPConfig upgrade, I noticed that the phpMyAdmin folder sometimes disappears. When I run the auto-update script manually, it says that phpMyAdmin is up-to-date, but the folder does not exist.

Currently, the script tries to fetch the latest version number and URL from a deprecated source, so it cannot download the latest phpMyAdmin package.

Current workaround: I manually downloaded and installed phpMyAdmin version 5.2.3 to the proper folder, and it works, but I want to:

1. Make the script update automatically in the future
   
   
2. Ensure it never deletes the phpMyAdmin folder if the download fails
   

Questions:

1. What is the safe method to update phpMyAdmin using this script?
   
   
2. How can I modify the script to avoid folder deletion if the download fails?
   
   
3. Any recommended best practices for keeping phpMyAdmin updated on ISPConfig servers without risking deletion?
   

Thanks in advance for guidance!

 

The script is fine, and should 1st check the version in PMA repo and compare to local, if it's the same latest, abort, otherwise, update.

The problem suspected in ISPConfig Auto Installer which was taken from this script and reported here was reaching the version txt from some servers, and the small suggested fix was to check the version from alternative permanent source.

I'm currently on mobile and cannot easily navigate to that post of mine, but you can try finding it and apply to your current script, but no guarantee that will fix it though.

 

Thanks for the info! That explains it well.
I’ve set the script to use a fixed version (5.2.3) for now, and phpMyAdmin works fine again.
I’ll wait for the permanent solution you mentioned.

 

I have the same problem.

The directory containing phpMyAdmin was renamed with the backup information, and the new directory wasn't created.

I followed the instructions in a post by th0m in a 2023 thread yesterday, but it's gone now.

 

Today, phpmyadmin is working again. I don’t know why!

 

I deleted/uninstalled all default phpmyadmin stuff and created a website phpmyadmin.domain.tld with latest chrooted php in which the latest phpmyadmin release is uploaded.
(I'm running all databases, including all ispc db's of nodes, in a 2 node and arbitrator galera cluster to which phpmyadmin connects)

If your running multiple webservers and want phpmyadmin on each server just create a website phpmyadmin.servername on every server.
Set phpmyadmin url in the panel's interface configuration to:
https://phpmyadmin.[SERVERNAME]/index.php?route=/database/structure&db=[DATABASENAME]

I now have 2fa capabilities (among other things) which I could not get working in the original phpmyadmin install.

 

Today, the phpmyadmin directory have disapear

 

You mean the one install via apt?

 

To add 2fa functionality in ispc's default phpmyadmin installation takes way more than just one install via apt.

 

Default is now no longer via apt, as mentioned in other threads. The only problem is, it is not always working as version txt is not always reachable.

Have you tried this after this new non-apt install via ISPConfig Auto Installer? Because what I understood is that the apt install would not allow 2FA, but manual install will, only you opted it via web site install instead, and haven't tried the latest ISPConfig Auto Installer.

 

True, it were older nodes from when autoinstaller didn't exist yet and from when apt install was still used. No point doing the latest auto installer on already fully installed and running servers.

On those web-db nodes I replaced it with a manual install in /usr/share to preserve /phpmyadmin in the webserver config.

The website install is on my own multi node playground where every and all databases are hosted in a 2 node (and arbiter) galera cluster.
So I only need one phpmyadmin install to connect to the cluster and don't need /phpmyadmin on every web node.

 

No worries. I was thinking the OP is about apt install that can be backed up, uninstalled and reinstalled with full package as what @Th0m's script is doing except that it failed to connect and get version txt from the default link was the main issue but manually doing that in another web site is fine too.

Also agreed that one can opt for no /phpmyadmin for each web node but I think a proxy site to that /phpmyadmin also may achieve that as well, where they are both one install, except one is in its own website, while the other is in /usr/share, a built in, for newer ISPConfig Auto Install, or a replacement, using Th0m's script for already installed ISPConfig server.

 

Not installed with apt, only with ispconfig installer.

When i launch apt command, the system add many php-* package and i don't know there are some conflict with ISPConfig