Learn how to use Railgun with Origin CA certificates.
Using Railgun with Origin CA Certificates
While using Railgun and configuring Origin CA certificates, please note that additional steps are needed to avoid service impact for HTTPS requests being sent from the Listener to the site's origin (where the origin CA certificates are installed). This is due to the default trust store that is shipped with the Railgun listener being a identical copy of the root certificates that it trusts (identical to what NSS/Mozilla trusts).
This means that when enabling Full SSL (Strict) in the dashboard while Railgun is enabled, the Listener will no longer consider the origin presenting the Origin CA certificate as trustworthy, resulting in a 520 error.
Here is an example of the error generated when
validate.cert = 1, the origin uses an Origin CA leaf, and the Origin CA roots are not in the trust store for Railgun specified by
rg-listener: [2a074d8b36f00000-ATL] www.example.com origin request failed 126.96.36.199:443 to %!!(MISSING)s(MISSING): x509: certificate signed by unknown authority
Here are the following options available to avoid these errors:
validate.cert = 0in the
- Add to the trust store specified in the
ca.bundleparameter in the
railgun.conf. This can be done by simply adding these root certificates at the end of the file using a text editor.
By default, railgun.conf defines the Listener's trust store as (for Debian/Ubuntu):
ca.bundle = /etc/ssl/railgun-ca-certs.crt