Can access through IP but can't with domain

Hi, @stgonzales

Before we deep dive into troubleshooting this, can you confirm that the domain name is pointed to your droplet’s IP address?

You can use our DNS lookup tool in order to check if the domain name is resolving from your droplet:

https://www.digitalocean.com/community/tools/dns

Let me know how it goes,

Regards, Alex

Heya,

here is an update on an older topic in case someone stumbles upon it

Based on the configuration and description, there are a few key points to consider:

1. SSL Configuration for Nginx:

   • Your Nginx configuration listens on both ports 80 (HTTP) and 443 (HTTPS), but it doesn’t include the SSL certificate and key for handling HTTPS traffic.
   • If you want to serve your site over HTTPS (which seems to be the case since browsers are defaulting to HTTPS), you need to specify the SSL certificate and key in your Nginx configuration.

2. Let’s Encrypt SSL Certificate:

   • If you don’t already have an SSL certificate, you can obtain one from Let’s Encrypt. You mentioned a container name letsencrypt-nginx-container, but it’s unclear if you’re actually using a tool like Certbot to obtain an SSL certificate.
   • If you have already obtained an SSL certificate from Let’s Encrypt, make sure it is correctly referenced in your Nginx configuration.

3. Nginx Configuration:

   • You should separate your server blocks for HTTP and HTTPS.
   • The HTTP server block (port 80) should ideally only handle HTTP traffic and potentially redirect it to HTTPS.
   • The HTTPS server block (port 443) should handle SSL termination and serve your content over HTTPS.

4. Docker Configuration:

   • Ensure that the SSL certificates (if obtained) are correctly mapped into your Docker container.

Here’s an example of how you might adjust your Nginx configuration:

server {
    listen 80;
    listen [::]:80;
    server_name iamgonzales.dev www.iamgonzales.dev;

    location ~ /.well-known/acme-challenge {
        allow all;
        root /usr/share/nginx/html;
    }

    # Redirect all HTTP traffic to HTTPS
    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl;
    listen [::]:443 ssl;
    server_name iamgonzales.dev www.iamgonzales.dev;

    ssl_certificate /path/to/fullchain.pem; # Adjust with your SSL certificate path
    ssl_certificate_key /path/to/privkey.pem; # Adjust with your SSL key path

    root /usr/share/nginx/html;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

In your docker-compose.yml, ensure the SSL certificates are correctly mapped:

volumes:
  - ./nginx.conf:/etc/nginx/conf.d/default.conf
  - ./letsencrypt-site:/usr/share/nginx/html
  - /path/to/letsencrypt:/etc/letsencrypt # Map the directory containing your SSL certificates

After making these changes, restart your Docker container:

docker-compose down
docker-compose up -d

Remember:

• The SSL certificate (fullchain.pem) and key (privkey.pem) paths must be correctly set in your Nginx configuration.
• If you haven’t obtained an SSL certificate yet, you’ll need to do so. Tools like Certbot can automate this process. You may need a separate Docker container for managing Let’s Encrypt certificates or run Certbot on the host.
• DNS should be properly configured for iamgonzales.dev and www.iamgonzales.dev to point to your server’s IP.