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

host name problem with auto installer

G

gpdahl

Guest
My computer can resolve the host name. Other servers can resolve the host name.
The server I'm trying to install onto can resolve its host name.

BUT PLESK AUTO INSTALLER CAN'T!

What magic trick do I have to perform to get his piece of **** to install?
 
Are you using a fully qualified domain name (FQDN)? So, something like server1.example.com and not just server1?
 
Yes. However, it is an internal domain. Does the Plesk installer have to see it from outside my router?
 
Back
Top