-
Notifications
You must be signed in to change notification settings - Fork 594
Clarity on SSL-support (Let's Encrypt/third-party) for custom domain #4240
Comments
If you want user to be able to access your application on your custom domain you need to add a route to Flynn for |
What path did you use for this:
? |
So for anyone needing (free) SSL for your flynn site, here are my instructions for doing so:
Success! |
@Kentoseth I've done exactly as said here. I have a fullchain (consist of 3 different certificates) and privatekey and a certificate file. I used fullchain.pem and privkey.pem in this case. it says: service provider gave me these: x.509, intermediate certificate, root certificate there are no docs on what is needed for route update for SSL. |
I have searched through a number of past issues and I don't think this question has been asked yet (specifically). Threads of ref are: #1995 #4225
Here is the breakdown from my side:
With #1995 and https://flynn.io/docs/apps#https , do I need to generate a Let's Encrypt certificate manually so that I can secure: subdomain.mydomain.com > https://subdomain.mydomain.com ?
If YES, can anyone explain the basic steps of doing this (as I am unsure if HTTPS should be done for both subdomain.mydomain.com && [subdomain].[xxxx].flynnhub.com) ?
PS. I understand that there exists multitudes of resources on how to certify a domain/subdomain (with Let's Encrypt) regularly, but the question above is for the Flynn-specific use-case
The text was updated successfully, but these errors were encountered: