• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Plesk is unavailable

Oktay

Oktay

New Pleskian
I have updated my Plesk to onyx 17.0.17

If I want to login to Plesk, I become an error:

An internal error occurred in Plesk.
Due to security reasons the option \'-show-password\' is no longer supported. Use \'--get-login-link\' to generate a one-time login link

what can I do now?

thank you
 
Could you show the output of the following command?
plesk bin extension --list

Maybe you have some incompatible extension or custom integration.
 
[root@v7062 ~]# plesk bin extension --list
configurations-troubleshooter - Webserver Configurations Troubleshooter
fileserver - Samba Fileserver Configuration
firewall - Firewall
panel-migrator - Plesk Migrator
vpn - Virtual Private Networking
wp-toolkit - WordPress Toolkit
 
I am a only front panel user. And now I can not see my Plesk panel anymore. No one has any idea?
 
Hi Oktay,

pls. be informed, that Plesk invented as well a pretty good "Plesk repair utility", which can be used to fix quite a lot of issues.


In your case ( that you recently updated/upgraded ), it is recommended to use first the "installation" ASPECT - option, before you would consider to use the "all" aspect - option:

plesk repair ASPECT [OPTION]​

Examples:

plesk repair installation -y -v

plesk repair all -y -v

Pls. be informed, that EACH repair - process will create as well a depending log - file at "/var/log/plesk", which can help to investigate errors/issues/problems.​


In addition, it could help to investigate your Plesk Control Panel - log - files:


Sometimes, it is as well a good idea to change the log - level, to get more informations in psa - log - files:

 
Unfortunately without success
please look


...

[2016-12-03 20:02:27] Checking the structure of the Plesk database
[2016-12-03 20:02:28] ........................ [OK]
[2016-12-03 20:02:28]
[2016-12-03 20:02:28] Checking the consistency of the Plesk database
[2016-12-03 20:02:28] ...................... [OK]
[2016-12-03 20:02:28]
[2016-12-03 20:02:28] Checking system users
[2016-12-03 20:02:28] ............................................... [OK]
[2016-12-03 20:02:28]
[2016-12-03 20:02:28] Checking Linux system files
[2016-12-03 20:02:30] ......................................... [OK]
[2016-12-03 20:02:30]
[2016-12-03 20:02:30] Checking virtual hosts' file system
[2016-12-03 20:02:30]
[2016-12-03 20:02:30] There are incorrect permissions on some items in the WWW root
[2016-12-03 20:02:30] directory of the domain 'sitename' .......................... [ERROR]
[2016-12-03 20:02:30] - Incorrect permissions on
[2016-12-03 20:02:30] /var/www/vhosts/sitename/httpdocs/.: expected is one of
[2016-12-03 20:02:30] 0750, 0755, actual is 0770
[2016-12-03 20:02:30] Repairing incorrect permissions .................................
[2016-12-03 20:02:30] [FIXED]
[2016-12-03 20:02:31]
[2016-12-03 20:02:31] There are files or directories with suspicious permissions in the
[2016-12-03 20:02:31] root directory of the domain 'sitename' ..................... [WARNING]
[2016-12-03 20:02:31] - /var/www/vhosts/sitename/httpdocs/external_c
...more files here...

...

[2016-12-03 20:02:35] Repairing web server configuration
[2016-12-03 20:02:35] Reinstalling SSL/TLS certificates ...............................
[2016-12-03 20:02:35] [OK]
[2016-12-03 20:02:35] Applying the default SSL/TLS certificate to all IP addresses ....
[2016-12-03 20:02:35] [OK]
[2016-12-03 20:02:35] Repairing server-wide configuration parameters for web servers ..
[2016-12-03 20:02:40] [OK]
[2016-12-03 20:02:40] Updating the file of sharing passwords and permissions of users
[2016-12-03 20:02:40] according to actual information .................................
[2016-12-03 20:02:40] [OK]
[2016-12-03 20:02:40] Repairing web server configuration for all domains. This aspect
[2016-12-03 20:02:40] can be used with individual domains ("plesk repair web
[2016-12-03 20:02:40] example.com"), and on the server level ("plesk repair web") .....
[2016-12-03 20:02:47] [OK]
[2016-12-03 20:02:47]
[2016-12-03 20:02:47] Checking the usage of PHP handlers
[2016-12-03 20:02:48] .................................. [OK]
[2016-12-03 20:02:48]
[2016-12-03 20:02:48] Repairing the mail server configuration
[2016-12-03 20:02:48] Reconfiguring all domains and mailboxes .........................
[2016-12-03 20:03:34] [OK]
[2016-12-03 20:03:34]
[2016-12-03 20:03:34] Checking the DNS configuration file
[2016-12-03 20:03:34] ................................. [OK]
[2016-12-03 20:03:34]
[2016-12-03 20:03:34] Restoring DNS server configuration
[2016-12-03 20:03:34] Synchronizing DNS zones with the DNS server .....................
[2016-12-03 20:03:34] [OK]
[2016-12-03 20:03:34]
[2016-12-03 20:03:34] Checking MySQL database servers
[2016-12-03 20:03:35] ..................................... [OK]
[2016-12-03 20:03:35]
[2016-12-03 20:03:35] Repair databases on available servers
[2016-12-03 20:03:35] ............................... [OK]
[2016-12-03 20:03:35]
[2016-12-03 20:03:35] Repair database users on available servers
[2016-12-03 20:03:35] .......................... [OK]
[2016-12-03 20:03:35] Error messages: 1; Warnings: 2; Errors resolved: 1
 
Hi Oktay,

you seem to overread a quite essential part of my answer, so I will repeat that:

UFHH01 said:
Pls. be informed, that EACH repair - process will create as well a depending log - file at "/var/log/plesk", which can help to investigate errors/issues/problems.

In addition, it could help to investigate your Plesk Control Panel - log - files:

Plesk for Linux services logs and configuration files ( KB - article: 111 283 )
Sometimes, it is as well a good idea to change the log - level, to get more informations in psa - log - files:

How to enable/disable debug logging in Plesk 11.5 and up? ( KB - article 120 101 )
Click to expand...
 
I am not a professional.

I'm afraid that I might lose all my content ..

I have run command. I have tried repair function.

There were 2 warnings. Server restarted but i can not still see my panel.
 
With this method I can login but every time I do not want to do that :)

Repair does not help either.

What solution for me?

thank you

--------
[root@v7062 ~]# /usr/local/psa/bin/admin --show-password
Due to security reasons the option '-show-password' is no longer supported. Use '--get-login-link' to generate a one-time login link.

[root@v7062 ~]# /usr/local/psa/bin/admin --get-login-link
https://v7062.xxxxxx.com:8443/login?secret=***

--------
 
Hi Oktay,

did you consider to CHANGE the current password over the Plesk Control Panel, in order to see, if that solves your issue?

What happens, when you use the ( non-https ) login - page at : v7062.xxxxxx.com:8880 ?
 
It seems like I found the explanation for your situation :) An error message "An internal error occurred in Plesk." is shown in some other control panel that belongs to your hoster, right? Probably you have some button to perform the autologin to Plesk. In such case you can contact your hoster and notify them that their integration should be updated in order to support Plesk Onyx release.
To access the Plesk you can use direct URL https://v7062.xxxxxx.com:8443/
If you don't remember the password you can change it using the following command:
plesk bin admin --set-admin-password -passwd <your-password-here>
 
I would like to tell you that I have vServer:)

http://www.xxxxxxxx.com:8880/admin/domain/list?context=domains works already :)

But i want use as usual 4643 port. On parallels panel, i click on Control panels > Manage > Log in to Plesk > and then

Plesk is unavailable
Screen ID: 03.05.00.01.04
Help Refresh
An internal error occurred in Plesk.
Due to security reasons the option \'-show-password\' is no longer supported. Use \'--get-login-link\' to generate a one-time login link.

But i have changed already my pass
 
Hi Oktay,

Oktay said:
But i want use as usual 4643 port.
Click to expand...
The standard Plesk port is "8443", are you aware of that?

Port "4643" is mostly configured for the "Virtual Automation Control Panel".

So for a better understanding, you would use

For Plesk ( https ):

https://v7062.xxxxxx.com:8443
https://XXX.XXX.XXX.XXX:8443 ( where XXX.XXX.XXX.XXX is your server IP )​

For Plesk ( http ):

http://v7062.xxxxxx.com:8880
http://XXX.XXX.XXX.XXX:8880 ( where XXX.XXX.XXX.XXX is your server IP )​

For Virtuozzo:

https://v7062.xxxxxx.com:4643
https://XXX.XXX.XXX.XXX:4643 ( where XXX.XXX.XXX.XXX is your server IP )​


Consider to use the following commands over ssh ( as user "root" ) to check your current port usage:

Code: 
netstat -tulpn | grep :8443
netstat -tulpn | grep :8880
netstat -tulpn | grep :4643

lsof -i | grep 8443
lsof -i | grep 8880
lsof -i | grep 4643
 
Hallo Oktay,

I landed on your post because I am experiencing the exact same error after having updated to Onyx, not to mention many other problems, which have been solved in the meantime.

I have come to the conclusion that this is a Virtuozzo template problem. You need to have permissions to run vzpkg or yum. If you are on a virtual server, like we are, then you probably don't have access to the Virtuozzo installation and you cannot update the template (du kannst sehr wahrscheinlich den Template nicht updaten) unless you host your own physical server. If not, then you need to contact your hoster as @SibProgrammer and @Linulex suggested.

If you are only a front panel user, compliment to you for figuring out how to run admin with the correct variable and value.

freundlichen Grüssen
 
Last edited:
Thank you at all here.

I have not solved the problem yet. But firetruckmama has understood my problem very well because he has experienced the same problem.

I wrote to my host. Then let's see.

I can not update virtuozzo with vServer maybe. Danke schön firetruckmama!
 
Hasina Patrick said:
Hello, I'n new in Plesk. I have updated Plesk 12.0.18 to Plesk 17.0.7.
All my websites run but I can't log on https://nsxxxxxx:8443. How can I do to solve this?
Thank you
Click to expand...
Make sure, at least, that sw-cp-server is up and running. Contact Plesk Support Team if you are not familiar with Linux command line interface.
 
Ok ,thank you. For now, I commented all the lines in /etc/sw-cp-server/conf.d/ssl.conf
it runs now but I'd like to know how to use SSL in Plesk.
Thank you for your quick reply.
 
You must log in or register to reply here.

Similar threads

Manuel Kuhn
Issue Problems from debian 10 to 12
Replies
2
Views
562
Sebahat.hadzhi
Sebahat.hadzhi
E
Resolved Using subdomain as plesk login Url
Replies
1
Views
195
ertcm
E
P
Question Plesk login 8443 cannot be called up
Replies
8
Views
945
Kaspar@Plesk
Kaspar@Plesk
A
Question login url
Replies
1
Views
2K
webserverforum
W
kristobal1969
Issue Migration problem with roundcube 1.6.9
Replies
0
Views
150
kristobal1969
kristobal1969
Back
Top