On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

How to create a domain forwarder in Plesk?

Follow

Comments

6 comments

  • Avatar
    Денис Кораблев

    Здравствуйте!

    Как сделать редирект входа в панель управления?

    Моя панель Admin Pelsk сейчас доступна по IP без SSL и по домену с SSL.

    Мне необходимо чтобы была переадресация с ip на домен.

    Либо предложите другой вариант защиты админки.

    Спасибо!

    0
    Comment actions Permalink
  • Avatar
    Anton Maslov

    Денис, добрый день, вот эта статья должна вам помочь.

    0
    Comment actions Permalink
  • Avatar
    Abdul Haseeb Kamal

    Hey I want to redirect my domain mangastream.cc to mangapan.com but i can't see any option in my plesk panel where to redirect it. Also how can i change my root password? when i am going to change my root password the old password also works. 

    0
    Comment actions Permalink
  • Avatar
    Diane Sutton

    Our experience has been: this works for forwarding a non secured domain to a SSL-secured website only if the address is typed into the browser address bar as example.com or http://example.com, but not if entered as https://example.com. In that case, a security warning appears in the browser. It's a likely scenario for someone to retain https:// in the address bar, when they backspace and insert a new URL.
    Even if we apply a permanent http to https redirect to the (non secured) domain, example.com or http://example.com successfully redirects to the https target website, without triggering a security warning.
    This puzzles me: there is no content on the forwarding domain in transit & thus nothing that can be encrypted between browser and server. How is there a security risk? Why does the browser look for a certificate?
    Is there a way to forward a domain, or use a domain alias, to redirect to a secured website (hosted on the same server):
    - without triggering the security warning message, and
    - without maintaining a (useless?) security certificate on a redirected domain?
    We use Plesk Obsidian for Linux v18, Centos 8.
    And if we have to use domain alias to achieve this (which will entail moving the forwarding domain to another subscription): can we move a domain without losing its mail accounts? I can't find a recently updated article on this.

    0
    Comment actions Permalink
  • Avatar
    Obaro Alidou K.
    I need these redirects:
    1- My home page example.com to redirect to example.io 
    2- example.com/a-specific-page to redirect to example.io/a-specific-page
    Note: I want to keep the content of example.com. This is because example.com hosts the actual script and example.io hosts the promotional content (homepage, TOS, Contact page.....etc)
     
    So i tried the fourth method in the article
     
    location = / {

    return 301 https://example.io/;
    }

    // for the first redirect
    but it didn't work. it shows the error below:
     
    Invalid Apache configuration: AH00526: Syntax error on line 1 of /var/www/vhosts/system/example.com/conf/vhost_ssl.conf: Invalid command 'location', perhaps misspelled or defined by a module not included in the server configuration
     
    Of course i replaced the actual domain with example.com in the error message.
     
    0
    Comment actions Permalink
  • Avatar
    Yulia Plokhotnikova

    Hello @Obaro Alidou K..

    Invalid Apache configuration: AH00526: Syntax error on line 1 of /var/www/vhosts/system/example.com/conf/vhost_ssl.conf: Invalid command 'location', perhaps misspelled or defined by a module not included in the server configuration

    This error may appear when the 'location' directive was specified for HTTP/HTTPS (apache) and not for nginx. As the 4-th method says, it is needed to add the directives in Additional nginx directives 

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request