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

Question Subdomains with Document root inside /httpdocs/

jonny512379

New Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.55 Update #2
Hello All (new to plesk)
OS: Ubuntu 22.04.3 LTS
Product: Plesk Obsidian 18.0.55 Update #2

what i want is:
example.com with the root of /httpdocs​
sub1.example with the root of /httpdocs/sub1​
sub2.example with the root of /httpdocs/sub2
etc​
possibly also:
images.example with the root of /httpdocs/images​
js.example with the root of /httpdocs/js​
​
I want this as my main files/coding, includes, etc are all within /httpdocs so are easy to get relative paths too.
/sub1 will basically contain an almost identical site (well using the same code/database/etc), but with a slightly different config.php file, so that the content/search criteria will display different results

Every time i set up a subdomain (currently using a temporary domain!!!) i get "500 internal server error", even if all i have in httpdocs/sub1 is index.html (hello world, etc)

Is this something possible? or something i am doing wrong. Or will it work without the temporary domain (which is already a subdomain provided by plesk)

Thank you
Jon
 
Please check your error_log for details on the error no. 500 entry. Normally, the reason is given, too. It could be caused by a wrong .htaccess syntax.

Generally it is not such a good practice to nest domains and subdomains, because for example .htaccess settings from /httpdocs will affect all that is stored in /httpdocs/sub1, /sub2 etc.
 
Back
Top