• 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.

Admin account doesnt work !

G

Goldline

Guest
Hello,

I just installed Plesk on Windows server 2003 everything went smoothly.

All services are up and running works excellent however..

In the installation readme its saying that you need to logon with
the username "admin" and the password "setup" (without the quotes)
to complete the installation. But when i try to login with the above info then its saying that the password is incorrect so i cannot login!

Anyone got a solution ?

Thanks in advance,

Goldline
 
try following:
cmd
cd %plesk_bin%
plesksrvclient -get

Use this to login to Plesk

John S.G.
 
Thanks alot that worked!

Theres one more thing:

I cant run apache on port 80 because im behind a NAT network.

Ive forwarded port 8080 to my lan static ip address but..

where can i change the default apache tomcat port(80) to : 8080 ?

Goldline

EDIT:
Oh sorry guys, i just found out that apache tomcat is allready running at port 8080 :)
 
Oh sorry guys, i just found out that apache tomcat is allready running at port 8080 :)

Hello Godldline,

Yep, you should update Tomcat's server.xml with new port.
However i don't reccomend use port 8080 as it is using by Tomcat localhost default engine.
 
Back
Top