New as of 0.4.0
Dokku supports SSL/TLS certificate inspection and CSR/Self-signed certificate generation via the
certs plugin. Note that whenever SSL/TLS support is enabled SPDY is also enabled.
certs:add <app> CRT KEY # Add an ssl endpoint to an app. Can also import from a tarball on stdin. certs:generate <app> DOMAIN # Generate a key and certificate signing request (and self-signed certificate) certs:remove <app> # Remove an SSL Endpoint from an app. certs:report [<app>] [<flag>] # Displays an ssl report for one or more apps certs:show <app> <crt|key> # Show the server.crt or server.key on stdout certs:update <app> CRT KEY # Update an SSL Endpoint on an app. Can also import from a tarball on stdin
# for 0.3.x dokku nginx:import-ssl <app> < certs.tar
Adding an ssl certificate before deploying an application will result in port mappings being updated. This may cause issues for applications that use non-standard ports, as those may not be automatically detected. Please refer to the proxy documentation for information as to how to reconfigure the mappings.
Dokku provides built-in support for managing SSL certificates on a per-application basis. SSL is managed via nginx outside of application containers, and as such can be updated on-the-fly without rebuilding containers. At this time, applications only support a single SSL certificate at a time. To support multiple domains for a single application, wildcard certificate usage is encouraged.
certs:add command can be used to push a
tar containing a certificate
.key file to a single application. The command should correctly handle cases where the
.key are not named properly or are nested in a subdirectory of said
tar file. You can import it as follows:
tar cvf cert-key.tar server.crt server.key dokku certs:add node-js-app < cert-key.tar
Note: If your
.crtfile came alongside a
.ca-bundle, you'll want to concatenate those into a single
.crtfile before adding it to the
cat yourdomain_com.crt yourdomain_com.ca-bundle > server.crt
When an SSL certificate is associated to an application, the certificate will be associated with all domains currently associated with said application. Your certificate should be associated with all of those domains, otherwise accessing the application will result in SSL errors. If you wish to remove one of the domains from the application, refer to the domain configuration documentation.
Note that with the default nginx template, requests will be redirected to the
https version of the domain. If this is not the desired state of request resolution, you may customize the nginx template in use. For more details, see the nginx documentation.
Note: Using this method will create a self-signed certificate, which is only recommended for development or staging use, not production environments.
certs:generate command will walk you through the correct
openssl commands to create a key, csr and a self-signed cert for a given app/domain. We automatically put the self-signed cert in place as well as add the specified domain to the application configuration.
If you decide to obtain a CA signed certificate, you can import that certificate using the aforementioned
dokku certs:add command.
certs:remove command only works on app-specific certificates. It will
rm the app-specific tls directory, rebuild the nginx configuration, and reload nginx.
certs:show command can be used to show your configured certs for an app. The show command can be used for example to export Let's Encrypt certificates
after they've been generated. You can export it as follows:
dokku certs:show node-js-app crt > server.crt dokku certs:show node-js-app key > server.key
New as of 0.8.1
You can get a report about the apps ssl status using the
=====> node-js-app Ssl dir: /home/dokku/node-js-app/tls Ssl enabled: true Ssl hostnames: *.node-js-app.org node-js-app.org Ssl expires at: Oct 5 23:59:59 2019 GMT Ssl issuer: C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA Ssl starts at: Oct 5 00:00:00 2016 GMT Ssl subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.node-js-app.org Ssl verified: self signed. =====> python-app Ssl dir: /home/dokku/python-app/tls Ssl enabled: false Ssl hostnames: Ssl expires at: Ssl issuer: Ssl starts at: Ssl subject: Ssl verified:
You can run the command for a specific app also.
dokku certs:report node-js-app
=====> node-js-app ssl information Ssl dir: /home/dokku/node-js-app/tls Ssl enabled: true Ssl hostnames: *.dokku.org dokku.org Ssl expires at: Oct 5 23:59:59 2019 GMT Ssl issuer: C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA Ssl starts at: Oct 5 00:00:00 2016 GMT Ssl subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.dokku.org Ssl verified: self signed.
You can pass flags which will output only the value of the specific information you want. For example:
dokku certs:report node-js-app --ssl-enabled
The HSTS header is an HTTP header that can inform browsers that all requests to a given site should be made via HTTPS. Dokku does enables this header by default for HTTPS requests.
See the NGINX HSTS documentation for more information on how the HSTS configuration can be managed for your application.
Certain versions of nginx have bugs that prevent HTTP/2 from properly responding to all clients, thus causing applications to be unavailable. For HTTP/2 to be enabled in your applications' nginx configs, you need to have installed nginx 1.11.5 or higher. See issue 2435 for more details.
Your application has access to the HTTP headers
X-Forwarded-For. These headers indicate the protocol of the original request (HTTP or HTTPS), the port number, and the IP address of the client making the request, respectively. The default configuration is for Nginx to set these headers.
If your server runs behind an HTTP(S) load balancer, then Nginx will see all requests as coming from the load balancer. If your load balancer sets the
X-Forwarded- headers, you can tell Nginx to pass these headers from load balancer to your application via
dokku nginx:set node-js-app x-forwarded-for-value "\$http_x_forwarded_for" dokku nginx:set node-js-app x-forwarded-port-value "\$http_x_forwarded_port" dokku nginx:set node-js-app x-forwarded-proto-value "\$http_x_forwarded_proto"
Only use this option if:
X-Forwarded-headers (this may be off by default)
If it's possible to make HTTP(S) requests directly to Nginx, bypassing the load balancer, or if the load balancer is not configured to set these headers, then it becomes possible for a client to set these headers to arbitrary values.
x-forwarded-ssl property may also be set for application frameworks that require this value. Note that this is a non-standard version of setting
https, and should only be done as a last resort.
# force-setting value to `on` dokku nginx:set node-js-app x-forwarded-ssl on # force-setting value to `off` dokku nginx:set node-js-app x-forwarded-ssl on # removing the value from nginx.conf (default) dokku nginx:set node-js-app x-forwarded-ssl
When your app is served from port
80 then the
/home/dokku/APP/nginx.conf file will automatically be updated to instruct nginx to respond to ssl on port 443 as a new cert is added. If your app uses a non-standard port (perhaps you have a dockerfile deploy exposing port
99999) you may need to manually expose an ssl port via
dokku proxy:ports-add <APP> https:443:99999.