• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Domain alias problem

godfather21

Basic Pleskian
Hello,

I have added a domain alias without 301 redirect and it acts as the 301 is enabled, i had resync the subscription restarted dns but nothing.
 
What is the output of

mysql> select seoRedirect from domain_aliases where name='alias_name.com';

?
 
Before my command above login to Plesk database with

# plesk db
 
Where do you know from that the alias behaves like a 301 redirect? Did you test this by analyzing the header that a request to the alias returns, e.g.

# wget yourdomain.com

returning

...
HTTP request sent, awaiting response... 301 Moved Permanently
...

?
 
Your 301 is likely not generated by the web server configuration, but by a Wordpress rewrite rule. It is difficult to test, because you are also running a security software that is responding a 403 (forbidden) on test. To verify that the web server is responding with a 301 on the intial connect, you must first turn off the security software (maybe ModSecurity?), then use a command like "wget" to be able to see the headers returned by your request. If at that point you still get a 301 on the inital request to santorini-bakery.com, then you are having an issue with the Plesk web server configuration. It is unlikely that this will be the case. More likely you are seeing a behavior by design of Wordpress. You can see the same behavior when you open the santorinipatisserie.com without the www.-prefix as that will rewrite to the spelling with www.
 
Thank you for your answer, but i have a lot off sites like this on my server with domain alias and i dont have any problem at all. This is the strange and the wordpress it does not have any special software - plugin
 
wget www.santorini-bakery.com
--2016-09-08 15:19:44-- http://www.santorini-bakery.com/
Resolving www.santorini-bakery.com... 144.76.76.174
Connecting to www.santorini-bakery.com|144.76.76.174|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.santorinipatisserie.com/ [following]
--2016-09-08 15:19:45-- http://www.santorinipatisserie.com/
Resolving www.santorinipatisserie.com... 144.76.76.174
Reusing existing connection to www.santorini-bakery.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “index.html”
 
I have configured your setup on a test machine of ours.

I have tried to first set an alias to a Wordpress website. This returns a 301 redirect in my test system, too. Then I used the same domain name and set it as an alias to a website that is not using rewrite mechanisms. There it did return a 200. Same alias, but different targets.

I have no doubts that the 301 you are reading is a Wordpress redirect. Try this to verify: Move your .htaccess file of your Wordpress installation into htaccess.txt (or another backup name), run the wget on your domain alias again. Does it return a 200 now? Rename your htaccess.txt back to .htaccess. For the time of your test your website will not be accessible, because the missing .htaccess will hinder proper processing of Wordpress pages/URLs.
 
i tried what you said but i get the same

wget santorini-bakery.com
--2016-09-09 09:49:27-- http://santorini-bakery.com/
Resolving santorini-bakery.com... 144.76.76.174
Connecting to santorini-bakery.com|144.76.76.174|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.santorinipatisserie.com/ [following]
--2016-09-09 09:49:28-- http://www.santorinipatisserie.com/
Resolving www.santorinipatisserie.com... 144.76.76.174
Reusing existing connection to santorini-bakery.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “index.html.2”
 
Back
Top