Skip to content
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

Closed
4 tasks
gerbrent opened this issue Aug 16, 2022 · 7 comments
Closed
4 tasks

IPv6 - add Cloudflare Proxy #292

gerbrent opened this issue Aug 16, 2022 · 7 comments
Assignees
Labels
enhancement New feature, enhancement, or request infrastructure Related to infrastructure JB - action needed action needed from a JB Team member
Milestone

Comments

@gerbrent
Copy link
Collaborator

gerbrent commented Aug 16, 2022

see #16

Intention is to support IPv6 via Cloudflare Proxy (alongside other Cloudflare feature, caching, etc)

JB to add Cloudflare Proxying to:

  • new.jb.com
  • dev.jb.com
  • jb.com (at time of new website publishing?)
  • ... ?
@gerbrent gerbrent added enhancement New feature, enhancement, or request infrastructure Related to infrastructure JB - action needed action needed from a JB Team member labels Aug 16, 2022
@gerbrent gerbrent added this to the JB.com 1.0 milestone Aug 16, 2022
@gerbrent
Copy link
Collaborator Author

@ironicbadger added proxying this AM, so just need some testing to confirm

@ironicbadger
Copy link
Collaborator

We were missing a setting in the Cloudflare dashboard for SSL/TLS encryption. After setting this to Full (strict) things are working as expected.

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.

telegram-cloud-photo-size-1-5177193968927091236-y

@ironicbadger
Copy link
Collaborator

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.

@elreydetoda
Copy link
Collaborator

There's no need to move it to the next milestone, it's working since you turned on the DNS proxying 😁

https://geekflare.com/tools/tests/vn4ympfvz

image

@elreydetoda
Copy link
Collaborator

We were missing a setting in the Cloudflare dashboard for SSL/TLS encryption. After setting this to Full (strict) things are working as expected.

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.

telegram-cloud-photo-size-1-5177193968927091236-y

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)

@ironicbadger
Copy link
Collaborator

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.

@elreydetoda
Copy link
Collaborator

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 🙃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature, enhancement, or request infrastructure Related to infrastructure JB - action needed action needed from a JB Team member
Projects
None yet
Development

No branches or pull requests

4 participants