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

Resolved .htaccess not working within sub domain

RicardoF1RST

New Pleskian
Hi, any ideas much appreciated.
I have created a new sub domain, copied my files into it (including my normal .htaccess) and stuck a die("Hello Work"); at the top of my index.php. This works fine when directly addressed but if I stick anything else in rather than my index.php catching it, I get a 404 error as though the .htaccess isn't being used. Its the same .htaccess as I use in my other sub domain and that works fine. I have tried sticking some garbage at the top of the .htaccess in question, and I don't get a 500 error, just the same page not found which again indicates Apache isn't using the .htaccess. What am I missing!?
 
Is "Proxy Mode" enabled in the Apache & Nginx Settings? Else .htaccess is not interpreted.
 
I thought I had triple checked all settings. Correctamundo, Proxy Mode was disabled - many thanks for getting me to look again - only lost a day :-D
 
Back
Top