-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 - add Cloudflare Proxy #292
Comments
@ironicbadger added proxying this AM, so just need some testing to confirm |
We were missing a setting in the Cloudflare dashboard for SSL/TLS encryption. After setting this to A couple of notes. This requires a valid certificate from a trusted CA. We are using lets encrypt which qualifies but self-signed certs or certs from non trusted CAs will not work. |
With regards to IPv6 I'm reticent to even touch it for now - especially as part of the 1.0 milestone I would argue it's not important. Very few ISPs even support IPv6! My vote would be to defer this beyond 1.0 milestone. |
There's no need to move it to the next milestone, it's working since you turned on the DNS proxying 😁 |
So, in regards to this...shouldn't flexible also work? It'll also not require you have a cert on the jb.com server (which is still good to do, but isn't necessarily required) |
Yes, however for prod stricter is better imho. |
Ya, but when you put it to strict mode it'll be for the whole domain not just jb.com but even the new.jb.com, dev., etc..., which isn't a bad thing IMO (I'm all for more security) but just want to make sure you/JB are aware of that 🙃 |
see #16
Intention is to support IPv6 via Cloudflare Proxy (alongside other Cloudflare feature, caching, etc)
JB to add Cloudflare Proxying to:
The text was updated successfully, but these errors were encountered: