DNS Provider that offers port 80 redirect?

[impalaguy1230]

I'm definatly not an expert when it comes to this stuff, but here's what I'm trying to do.....

 

Trying to setup Organizr on Unraid/Docker and have it accessable from outside my LAN.  I'm using Nginx Proxy Manager on Unraid as well.  I have a small management portal setup at my work with the same containers and it is all working just fine.  However we have the "business" internet plan that does Comcast is not blocking ports 80 and 443 there like they do at my house.  No-IP has a port 80 redirect, so I have it configured to redirect port 80 to another port, my firewall is then grabbing that and sending it through to the proxy.  However I'm having two issues at the moment.

 

1 - I can't generate any SSL certs with Let's Encrypt since No-IP doesn't have an API so I can generate one with an DNS challenge.  I know Cloudflare will work with Let's Encrypt, however they don't have a port 80 redirect that I can find anywhere.  Are there any DNS providers/Domain Registrars that will work with Lets Encrype AND offer a port 80 redirect?

 

2 - I have a subdomain setup that is getting to my IP address ok, but for some reason I can't figure out why its getting sent to the wrong place at my firewall  Nginx is setup to point emby.myurl.com to my emby sever and somehow its getting sent the IP address of my Dream Machine Pro.  These are on two seperate LAN IP's/machines.  Are there any ways I can trace what is going on here to see where is getting directed in the wrong place?

[Eigenvektor]

DNS translates a host name like "linustechtips.com" to an IP address like 1.2.3.4, that's it. DNS operates on port 53. It has nothing to do with the web server that is e.g. running on port 80 or 443.

 

To be able to get a certificate from Let's Encrypt you need: A host name and public IP address, a server that is reachable via that IP and the server must be reachable on port 80 to be able to complete their challenge/response mechanism. No-IP isn't really involved in this, other than translating your host name to an IP, so Let's Encrypt can contact your server.

 

So to get a certificate you need to run e.g. Certbot on your server. It has different modes depending on which web server you use. See: https://certbot.eff.org/

[Jarsky]

You're not talking about DNS redirect as @Eigenvektor has pointed out. 

 

To setup Organizr to run on a standard https port, you need to port forward your external port 80/443 connection to your Nginx Proxy. You can then create your virtualhost configuration files for the particular services you're trying to reverse proxy. 

 

As pointed out, you need to run certbot which you can do via the LetsEncrypt container. This guide everything would be under the same domain/subdomain, with 1 cert. This should give you a fairly good rundown on what to do:

https://cyanlabs.net/tutorials/the-complete-unraid-reverse-proxy-duck-dns-dynamic-dns-and-letsencrypt-guide/

 

Personally the way I have mine configured, is each of my apps has its own subdomain and cert. Then all of my subdomains, are CNAME's to my primary domain. So sonarr.myurl.com radarr.myurl.com organizr.myurl.com all point to myurl.com. Nginx will still interpret the referral URL and redirect as necessary.  Then I have each of them configured in Nginx. Heres an example of my Ombi configuration

jarsky@myserver:/etc/nginx/sites-enabled$ cat ombi
server {
        server_name ombi.myurl.com;

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/ombi.myurl.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/ombi.myurl.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

        location / {
    proxy_pass http://mediabox:3579;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Host $server_name;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Ssl on;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_read_timeout  90;
    proxy_redirect http://mediabox:3579 https://$host;
}


        error_page 502 /502.html;
        location = /502.html {

        root  /var/www/mysite;
        }

}
server {
    if ($host = ombi.myurl.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


        listen 80;
        server_name ombi.myurl.com;
    return 404; # managed by Certbot


}