HTTP and HTTPS
Variants of how to use fylr with and without TLS certificate
Automated HTTPS Certificate
Let fylr get an certificate for you and renew it automatically:
In fylr.yml
:
You provide the HTTPS certificate
Put your certificate and private key in the same directory as
fylr.yml
, in this example the file names arecrt.pem
andkey.pem
.If you need additional certificates of a certificate chain, like intermediate certificates, put them into
crt.pem
, as well. In our test worked to put the most specific certificate first (like for fylr.example.com) and then follow with the certificate that was used to sign the first one (and then the certificate that was used to sign the second one).In
fylr.yml
:
You provide the service that does HTTPS
We do not recommend this. Using additional proxies and services in front of fylr often leads to hard to debug problems where we cannot help.
In fylr.yml
:
No HTTPS
Recommended only for internal use.
In fylr.yml
:
No HTTPS and domain is localhost
This is the default.
Further reading
Related topic: Multiple DNS domains and changing DNS domains
Last updated