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

Domain Aliases (or how to extend a license)

B

brooks

Guest
Domain aliases are a nice addition to Plesk but here are a couple of things to consider.
  1. There's no way to limit them (like you can with domains and sub-domains).
  2. By using some simple mod_rewrite rules you can easily host unlimited domains under a single account each with it's own content directory and name space.
    You could even to combine it with the "web user" feature to provide for individual quotas, etc. for each domain.
    [/list=1]
    I think it's a great new feature, but there should really be a way to limit them on a per (licensed) domain basis.
 
Big deal, like you couldn't already do the same thing manually?
 
I agree with you. You can actually run an entire hosting business based on command line configuration, but that's not the point. The point is that it's now it's available in the GUI, and fairly easy for customers exploit.
 
Go into your client permissions and turn off Domain Alias Management. (it's actually off by default)

They can only see their aliases then, they can't edit/add/delete them.

Working great on this end. I got 3 IM's this morning asking how to add more aliases :p

But I suppose if you want them to be able to manage their own, then yes, we need a limit capability. I do agree that it should be there.
 
I believe limits are coming, I requested this during the private beta phase of Plesk 8 so I would expect it to be in the next release.
 
Originally posted by brooks
I agree with you. You can actually run an entire hosting business based on command line configuration, but that's not the point. The point is that it's now it's available in the GUI, and fairly easy for customers exploit.

As a solution you can set the parameter "apache_allowoverride_default" in the misc table to <something differ from "All">, as result - value of this parameter will be used for apache directive in httpd.conf:
<Directory "/home/httpd/vhosts">
AllowOverride <something differ from "All">
</Directory>
 
I need to do this with PLESK 7.5, I found some tutorials but I still don't understand how mod_rewrite rules.

I want to redirect domain1 to domain2, but I want to see domain in the URL, I don't want frame redirection becuase I need to access directly to the files: domain1/users.php for example.

How can I do this?
 
Back
Top