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

Issue Unwanted 301 forwarding for aliases

Movak

New Pleskian
Server operating system version
Ubuntu 18.04..6 LTS
Plesk version and microupdate number
18.0.69 Update #3
I have several aliases pointing to the same App. I have the "Redirect with the HTTP 301 code" option disabled, yet it is still 301 forwarding to the main domain.
1747777624847.png
I have deleted and re-crerated the alias but no change.
Does anyone have any idea
 
Hello, @Movak . What app is deployed under the primary domain name? I am asking because there are domain-specific applications, such as WordPress for example, where the domain name is hard-coded.
 
Hello, @Movak . What app is deployed under the primary domain name? I am asking because there are domain-specific applications, such as WordPress for example, where the domain name is hard-coded.
It is WordPress, but it worked correctly before I changed the primary domain name. Currently, when I hit the server with one of the alias domains it does the following;
- Redirects due to code in the .htaccess file
- mysteriously redirects with a 301 that is not coded in .htaccess.

The main point is that it used to work, and now it doesn't
 
Thank you for the update. The redirection most likely occurs on site-level rather than because the Plesk settings. Still, what else you might check is whether there are any additional directives in Subscriptions > Hosting & DNS > Apache & nginx.
 
Hello, @Movak .
Could you please also check the redirect using CURL, with command like
Code:
curl -I https://youralias.com
. The most tricky moment with 301 redirect - that it's a permanent redirect, so it could be cached by your browser.
 
Back
Top