Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question
cpu from 13% to 100% in one minute Question Question

Question

Redirect HTTP domain A to HTTPS domain B (with lets encrypt cert installed already)

Posted June 22, 2017 4.5k views
UbuntuApacheLet's EncryptUbuntu 16.04

I would like to redirect domain A that is not secure (http) to domain B that is secure (https) that has a let’s encrypt ssl cert already installed. I believe the answer to my question is to utilize the rewrite rules. But, the documentation is a little difficult to understand -for me. Any help, with examples would be awesome.

Add a comment
michel92df116ca8bc0546fb67
By:
michel92df116ca8bc0546fb67

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question
cpu from 13% to 100% in one minute Question Question
Add a comment
2 comments

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
hansen June 22, 2017

Hi @michel92df116ca8bc0546fb67

You can use the following method to redirect by changing your VirtualHost:

<VirtualHost *:80>
  ServerName domainA.com
  Alias www.domainA.com
  Redirect / https://www.domainB.com/
</VirtualHost>

And the restart Apache with sudo apachectl restart
If everything works, then change it to Redirect permanent / https://www.domainB.com/

Reply Report
  • SporkWitch June 22, 2017

    In the case of nginx, you would use

    server {
    listen 80;
    server_name domainA.com;
    return 302 https://domainB.com/;
}

    Change to 301 for a permanent redirect.

    If you wish to include everything that might have followed the domain:

    server {
    listen 80;
    server_name domainA.com;
    return 301 https://domainB.com$request_uri;
}
    Reply Report

Related

Looking for something else?

Ask a new question Search for more help