How to add alias for subdomain in Plesk for Linux?

Follow

Comments

10 comments

  • Avatar
    Unknown User (Edited )

    I solved this problem through "Apache & nginx Settings" of my subdomain

    Additional directives for HTTP:
    ServerAlias my.alias.subdomain.tld
    Additional directives for HTTPS:
    ServerAlias my.alias.subdomain.tld
    Additional nginx directives:
    server_name my.alias.subdomain.tld;

    Just make sure your alias subdomain resolves correctly to the same IP as your base subdomain you want to stick your alias to.

  • Avatar
    Ivan Postnikov (Edited )

    Hello @Sage, thank you for sharing an alternative way to achieve this goal.

    Have you tried the steps from the article? Why was this way not suitable for you?

    Thank you in advance.

  • Avatar
    Unknown User

    Hello, @Ivan,

    Article offers redirect, redirect is not alias, it's just a redirect which sends browser to another location.

    Alias is fully-functional another name that points to same virtual host of webserver which is visible under it's own name, not under base subdomain name (they could belong to different domains at all).

    In my case, IP from DNS record became inaccessible (it pointed at old load balancer which IP became unavailable) and I created temporary address that users could use until their cached DNS completely change to point to new address. But not to bother with different DocumentRoot trees i just made it alias of another (temporary inaccessible for some users) subdomain. Yes, probably it's square-wheeled bicycle solution, but at least it works.

  • Avatar
    Anzhelika Khapaknysh

    Hi @Sage!

    The article has been updated according to your recommendations.
    Thanks for taking part in improving our knowledge base!

  • Avatar
    Andrew Sassoye

    Hello,

    This solution is really great. But how do I have to make Let's Encrypt also register the alias in the certificate?

    Thank you in advance.

  • Avatar
    Unknown User

    Can anybody pleaaaaase, explain this workaround better ...?

  • Avatar
    Konstantin Annikov

    @Mohamed Kheddime

    I have added a screenshot of Apache additional directives screen. Hope this helps to apply the workaround.
    If you are a domain owner and Apache/nginx additional directives are hidden, it is needed to contact your service provider for assistance.

    Reply me if something else should be added to describe the workaround in a best way.

  • Avatar
    Jens Feierabend

    The solution only works partially:


    If the web space is to redirect from HTTP to HTTPS (HTTP-301), the Apache rules for HTTP (port 80) are not included in the configuration using Include. This meanst it does not redirect a HTPP-Request to HTTPS. It shows the HTTP default page.

    Let's Encrypt does not work either, because Plesk does not know the alias subdomains in the interface.

    Very unsatisfactory that such a simple function is missing.

    Translated with www.DeepL.com/Translator

     

    @Ivan: Perhaps I miss something, but your tip does not work for me.

  • Avatar
    Taras Ermoshin

    Hello @Jens Feierabend!

    Thank you for reporting this! The article was updated accordingly.

    The fact that additional HTTP directives are not used when the option Permanent SEO-safe 301 redirect from HTTP to HTTPS is enabled in Domains > sub.example.com > Hosting Settings is a known issue caused by the Plesk bug PPPM-9230.

    See the article https://support.plesk.com/hc/en-us/articles/360008854853 for more information on the issue.

Please sign in to leave a comment.

Have more questions? Submit a request