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
Rails 4 PaperClip ImageMagick Content Type Error for Images Question Question
How to clean up ImageMagick Install in a Rails app with Paperclip? Question Question

Question

Nginx, SSL, multiple domains

Posted July 6, 2015 70.8k views
Ruby on RailsNginx

Hi folks!

Have been straggling around nginx.conf for multiple domains.

This is what I have

1) 3 domains
2) SSL cert
3) Droplet
4) nginx

I want to redirect all https, https://www, http, http://www to one of the domain from these 3. Simply saying, all should go to just https://www.example.com

ssl_certificate /var/www/domain1.com/shared/ssl/bundle.crt; 
ssl_certificate_key /var/www/domain1.com/shared/ssl/www_domain1_com.key;
ssl_verify_depth 3;

server {
    listen         *:80;
    server_name    www.domain1.com domain1.com www.domain2.com domain2.com www.domain3.com domain3.com;
    return         301 https://www.domain1.com$request_uri;
}

server {
    listen         *:443 ssl;
    server_name   domain1.com www.domain2.com domain2.com www.domain3.com domain3.com;
    return         301 https://www.domain1.com$request_uri;
}


server {
        server_name www.domain1.com;
        listen 443 ssl;
        root /var/www/domain1.com/current/public;
        access_log /var/www/domain1.com/current/log/nginx.access.log;
        error_log /var/www/domain1.com/current/log/nginx.error.log info;
}

these above config does not have any configuration issues. nginx -t give “ok”.

But the problem is that all https requests (which are not from domain1.com) trying to shake ssl hands which is not true. they should 301-ing to www.domain1.com

I have tried doing some playing around in default config, seemed do not help!

any suggestions - would be great!

Add a comment
kitchencoders
By:
kitchencoders
edited by kamaln7

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
Rails 4 PaperClip ImageMagick Content Type Error for Images Question Question
How to clean up ImageMagick Install in a Rails app with Paperclip? Question Question
Add a comment
1 comment
  • ronanb7cced4ff718fd337ac57 August 11, 2020
    Reply Report

    Hi. What block do we need to add to ensure no requests are taken directly from an IP number, a domain MUST be entered, or else return 444?
    E.g. server {
    listen 443 defaultserver;
    server    name “”;
    return 444;
    }
    Unlike port 80 where the above method works, unfortunately this blocks all HTTPS requests no matter whether the domain is used or not. Thanks.

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
kamaln7 June 15, 2016

Hi!

Because of the way TLS/SSL works, the whole handshake and encryption process must be done before receiving any HTTP headers or the response body (as all HTTP traffic is passed through the TLS/SSL ‘tunnel,’ so it has to be established first).

So you will have to create valid HTTPS server blocks for every one of the domains and configure that to redirect to the domain that you want.

server {
    listen         *:443 ssl;
    server_name   domain1.com;
    ssl_certificate /path/to/domain1.crt; 
    ssl_certificate_key /path/to/domain1.key;
    return         301 https://www.domain1.com$request_uri;
}

server {
    listen         *:443 ssl;
    server_name   domain2.com www.domain2.com;
    ssl_certificate /path/to/domain2.crt; 
    ssl_certificate_key /path/to/domain2.key;
    return         301 https://www.domain1.com$request_uri;
}

server {
    listen         *:443 ssl;
    server_name   domain3.com www.domain3.com;
    ssl_certificate /path/to/domain3.crt; 
    ssl_certificate_key /path/to/domain3.key;
    return         301 https://www.domain1.com$request_uri;
}
Reply Report

Related

Looking for something else?

Ask a new question Search for more help