You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have SSL set up with LetsEncrypt and forceSSL: true, and it works great. I use Cloudflare as a DNS provider and wanted to set up a redirection from www.xyz.com/* to xyz.com/*.
But as soon as I activated Cloudflare (as opposed to only using it for DNS) the site stopped working and I started running into an endless 301 redirect loop.
Turning forceSSL off stopped the loop, but if I do that I can only access the non-SSL version of the site (entering https just redirects me to it).
Is anybody successfully using Cloudflare with Mup's SSL? What does your config look like? Also does it make a big difference whether I use Mup's or Cloudflare's SSL?
So it seems like I need to turn forceSSL off and then enable SSL on Cloudflare's side. You can't use Cloudflare's caching, CDN, etc. unless you also use their SSL. You can then check "Always Use HTTPS" in Cloudflare's dashboard.
This seems to work except I'm now getting a 403 error when querying my GraphQL endpoint during the SSR process. Which is unrelated to Mup, but now I'm wondering if maybe I shouldn't just give up on Cloudflare for now…
I have SSL set up with LetsEncrypt and forceSSL: true, and it works great. I use Cloudflare as a DNS provider and wanted to set up a redirection from www.xyz.com/* to xyz.com/*.
But as soon as I activated Cloudflare (as opposed to only using it for DNS) the site stopped working and I started running into an endless 301 redirect loop.
Turning forceSSL off stopped the loop, but if I do that I can only access the non-SSL version of the site (entering
https
just redirects me to it).Is anybody successfully using Cloudflare with Mup's SSL? What does your config look like? Also does it make a big difference whether I use Mup's or Cloudflare's SSL?
My info:
Mup version (
mup --version
):1.4.5
The text was updated successfully, but these errors were encountered: