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

plesk setup

E

exmadyn

Guest
i'm a newbie with plesk.

we just got a new vps with plesk. is it ok to use the default hostname (localhost.localdomain)?

i'm confused, if i'm going to provide our domain yet that domain is currently active and running and hosted in different server. there might be a conflict. am i right?

need help...

thanks...
 
You can make the hostname whatever you want, it doesn't really matter. The only thing is that if you send out automatic client creation emails, it will use the hostname as the server url so it would be best if it actually worked. For instance, you could make it server.yourhost.com. Then, once you update yourhost.com to point to your server, you could make a subdomain called server and then the url would actually work. There might be a better way to do it, but this is the way I know.
 
Back
Top