Menu="Identification" Title="SSL Certificate Settings" Icon="ident.png" Tag="expeditedssl" ---
Use SSL/TLS: : > Determines how the webGui responds to HTTP and/or HTTPS protocol. > > Select **No** to disable HTTPS (but HTTPS is recognized and redirected to HTTP). > > Select **Yes** to enable HTTPS and redirect HTTP to HTTPS. > > With **Auto** selected, behaves like **No** if only a self-signed SSL certificate is present. If > a Lets Encrypt or other user supplied SSL certificate if present, behavies like **Yes**. > > A self-signed SSL certificate is automatically generated during start-up in the > file `/boot/config/ssl/certs/_unraid_bundle.pem` if it does not already exist. > > A Lets Encrypt or other user-generated SSL certificate, must be stored in the > file `/boot/config/ssl/csrts/certificate_bundle.pem`. *nginx* will prefer ths certificate if present. HTTP port: : > Enter the HTTP port, default is 80. HTTPS port: : > Enter the HTTPS port, default is 443.   :
Certificate issuer: : Certificate expiration: :   : > **Provision** may be used to allocate a *free* SSL Certficiate from [Let's Encrypt](https://letsencrypt.org/) and > then upload to your server. Note: We **highly** recommend using a static IP address in this case. > **Update DNS** may be used to manually initiate updating the DNS A-record of your server FQDN on unraid.net. Note > that DNS propagation change could take anywhere from 1 minute to several hours (we set TTL to 60 seconds). > Note: **Provision** may fail if your router or upstream DNS server has > [DNS rebinding protection](https://en.wikipedia.org/wiki/DNS_rebinding) enabled. DNS rebinding > protection prevents DNS from resolving a private IP network range. DNS rebinding protection is meant as > a security feature on a local LAN which includes legacy devices with buggy/insecure "web" interfaces. > One source of DNS rebinding protection could be your ISP DNS server. In this case the problem may be solved by > switching to a different DNS server such as Google's public DNS. > More commonly, DNS rebinding protection could be enabled in your router. Most consumer routers do not implement DNS > rebinding protection; but, if they do, a configuration setting should be available to turn it off. > Higher end routers usually do enable DNS rebinding protection however. Typically there are ways of turning it off > entirely or selectively based on domain. Examples: > **DD-WRT:** If you are using "dnsmasq" with DNS rebinding protection enabled, you can add this line to your router > configuration file: > `rebind-domain-ok=/unraid.net/` > **pfSense:** If you are using pfSense internal DNS resolver service, you can add these Custom Option lines: > `server:`
> `private-domain: "unraid.net"` > **Ubiquiti USG router:** you can add this configuration line: > `set service dns forwarding options rebind-domain-ok=/unraid.net/` > **OpenDNS:** Go to Settings -> Security and *remove* the checkbox next to > "Suspicious Responses - Block internal IP addresses". It is an all-or-nothing setting. > When all else fails, you can create an entry in your PC's *hosts* file to override external DNS and > directly resolve your servers unraid.net FQDN to its local IP address.