How to redirect a sub-domain to a different droplet?

Hi there,

It looks like the certificate issue could be due to Nginx not being configured correctly or not running on your Droplet-2. It is crucial to make sure that your Nginx server is correctly set up and running before attempting to generate SSL certificates using Certbot.

Before you proceed, double-check your DNS records. Here’s how they should be:

• pontres.com A record pointing to the IP of Droplet-2 (165.232.184.246)
• www.pontres.com A record pointing to the IP of Droplet-2 (165.232.184.246)
• in.pontres.com A record pointing to the IP of Droplet-1 (167.71.238.180)
• www.in.pontres.com A record pointing to the IP of Droplet-1 (167.71.238.180)

When you attempt to generate the certificate on Droplet-2, use the -d flag to specify the domain(s) you want the certificate for:

sudo certbot --nginx -d pontres.com -d www.pontres.com

This is telling Certbot that you want a certificate for pontres.com and www.pontres.com. It will try to validate that you own these domains by making a request to them. This request must hit your server (Droplet-2) for validation to succeed.

If the requests can’t reach your server, you’ll see the “connection refused” error that you’re seeing now. Make sure Nginx is running and properly configured to respond to requests for pontres.com and www.pontres.com.

You can verify if Nginx is running with:

sudo systemctl status nginx

Also, check your Nginx server block configuration for pontres.com and www.pontres.com and make sure it’s correct. It should be something like:

server {
    listen 80;
    server_name pontres.com www.pontres.com;

    location / {
        proxy_pass http://localhost:8000;  # Replace with actual configuration
        # ...
    }

    # ...
}

This configuration should be in a file in /etc/nginx/sites-available/, and there should be a symbolic link to that file in /etc/nginx/sites-enabled/.

If your Nginx setup is correct and you’re still having issues, there might be a firewall blocking incoming connections. If you’re using UFW, you can check the status with sudo ufw status verbose and make sure it’s allowing incoming connections on ports 80 and 443.

Let me know how it goes!

Best,

Bobby