• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Unable to change administrator's password

C

clavoie

Guest
Hi,

I have just installed Plesk 8.1 on Debian 3.1. Although I was able to complete the installation and log into the system, I could not change the administrator password at the initial configuratios screen.

Code:
Unable to change administrator's password: copy_file failed: copy_file: System Error: invalid file paths in /opt/psa/admin/bin/copy_file /opt/psa/tmp/nsfULYAs6 /etc/psa/.psa.shadow:

0: /usr/opt/psa/admin/htdocs/server/configure.php3:172

The "/opt/psa/tmp/nsfULYAs6" file was missing, so I checked the file permissions on both the "/opt/psa/tmp/" directory and "/etc/psa/.psa.shadow" file:

Code:
www:/home/collin# ls -la /opt/psa/tmp/
drwxrwxrwt   5 root root   4096 2007-01-08 23:12 .

www:/home/collin# ls -la /etc/psa/.psa.shadow
-rw-------  1 psaadm psaadm 6 2007-01-08 02:00 /etc/psa/.psa.shadow

Furthermore, I could read the default password in the shadow file.

If we consider the error message, "invalid file paths" could be refferring to ""/opt/psa/tmp/nsfULYAs6", which I did not find. Could a component be missing? Could it be a cryptographical mechanism required to generate the encrypted password?

I appreciate any help that can be provided.

Collin Lavoie
System Administrator
 
Back
Top