• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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