Recent content by PeterK900

Spot on Peter! Pasting the entire contents into the password prompt gets mariadb-upgrade to run successfully. Thank you. And thanks to everyone else who've solved this for me. And increased my Plesk knowledge - never knew about auto-generated admin password or ever looked at .psa.shadow.

Thanks Maarten. And for the hashing explanation. I never realised Plesk had its own, internally generated, db access password. Your command line looked really hopeful but, sadly, it doesn't pick up the password location, it still prompts for entry.

Thanks, Peter. I have found .psa.shadow but it's a long string and I'm not clear which bit is the admin password. None of the characters correspond to any password I've created. Here's the string... I've tried the various bits separately but each time I get access denied. I found this post...

Thanks scsa20. When I run mariadb-upgrade as root, I get a fatal error... Same error when using PuTTY. When I insert the credentials ( user=, password=, host= ) for root or a user the administrator privileges, I get the same error. The instructions say the user must have write access to...

I'm sure you have the answer. Thanks. I read the message quickly and didn't see the connecting hyphen in mariadb-upgrade and so didn't pick up it was a utility, not an instruction to 'upgrade MariaDB'! mariadb-upgrade is documented here. Compicated, but it looks like most of the parameters are...

The Database Export option within Plesk shows this error. Exporting from phpMyAdmin works fine. Tools and settings > Database Servers shows the MariaDB version correctly as 10.5.22. It was manually updated from the default build version 5 which might well have been 5.05.22 - as per the error...

An update to complete the story on this... The ftp problem appears to be part of a bigger issue. Whether related to the nydus-ex and nydus-ex-api issue raised in the Web Host's (Heart Internet) warning message (see #5) I don't know. Shortly after the ftp problem SSH connectivity was lost. Heart...

Thanks. I think it was browser cache and/or DNS propagation as the site now displays correctly. But your checklist is useful if this reoccurs. Thanks again for your help.

I have deleted the default index.html as per this post but the default web page still shows. Another site on the same server correctly displays preview and web view. What am I doing wrong?

Thanks again.

Thanks Peter. Will do. I've just logged into Plesk via the hosting server panel, rather than directly as I normally do. I see this message... Server Dashboard Capability Is Limited This dashboard relies on agent applications running on your server for certain operations to work, called...

Thanks Peter, but I don't think this is the problem. I configured Firewalls as per your link and left the default rules in place, allowing all from FTP. But the problem remains. And I can connect with FTP without Firewall installation on an almost identical server - same Centos version, Plesk...

I'm trying to connect a domain using FileZilla. Connection is achieved but then rejected by the server. Here are the FileZilla log messages... Connection established, waiting for welcome message... Error: Connection closed by server Error: Could not connect to server I found this post...

Thanks Kaspar. Only just noticed your advice!

No apology needed. All part of my learning curve! The last article gave me the command string that worked. Here it is... [root@147 dev990]# /opt/plesk/php/7.4/bin/php /usr/lib64/plesk-9.0/composer.phar create-project drupal/recommended-project:9.3.12 dev990 It installed Drupal 9.3.12 in the...