-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Cloudflare dns: After deploy Proxy is set to disabled #4662
Comments
When I set
|
Ok, finally nailed it, but this feels like a hack..
I think it can be considered as a bug, when you set transform record on a |
Hey @webdeb - i'm also using Cloudflare with my SST stack and have used your suggested transform code above to set proxied to true. It technically works (in that my domains in CF are set to proxied) but when the proxy is turned on, none of my URLs load (i get the ERR_TOO_MANY_REDIRECTS error). Did you have to provide any further config details in the sst config file or do anything else to get CF proxied domains to play nicely with cloudfront etc? Any pointers would be hugely appreciated. |
I did a test w/ the following code: new sst.aws.StaticSite("Web", {
domain: {
name: "domain.com",
dns: sst.cloudflare.dns(),
}
}); And I'm seeing the same behavior as @benjamindell. |
I was able to get this working using @webdeb 's suggestion and setting SSL to full on cloudflare: |
Hello, I've deployed a cluster to aws, and created the service with
public.domain.dns: sst.cloudflare.dns()
In cloudflare the Proxy status is disabled. I can enable it manually, but when I redeploy, the proxy is disabled again, I guess it's always a new entry if some cluster configurations are changed.
So, after deploy/redeploy the service is unavailable.
The text was updated successfully, but these errors were encountered: