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

More than one domain name for one physical hosting account

O

oglimmer

Guest
Hi,

I want to use many domain names in one physical hosting account.

For example:
funny-pics.com
funnypics.com
funny-pics.org
funnypics.org

in one account. I don't want to use redirects or forwardings.

What do I have to do?

Thanks
Oli
 
It is not possible to do this in plesk without manual file modification. It's been a while since I tried, but IIRC you could create a VirtualHost container in your vhost.conf for the "primary" domain.
 
You have to consider how you want the aliasing to function...

If its only a question about making the webserver answer to those aliases it can be done by adding the servers IP adress to DNS (a or cname record) and then manually editing the vhost.conf / vhost_ssl.conf settings for the physical domain to also include the alised domains.

(it can not be done native from within the Plesk interface)

If its also a question about aliasing mail then you have to edit some qmail settings.

One product that will do this for you is
4PSAs Total Domains.
 
Thanks.

Manually editing vhost.conf is of course an option, but I was afraid that Plesk could overwrite this file in the future.
 
Using the vhost.conf is exactly the point here - as if you read the documentation... You'll see that the idea with the vhost.conf is exactly to add customized settings that will not be overwritten by Plesk...
 
Back
Top