SSL routines:ST_CONNECT:tlsv1 alert protocol version
Running into an issue here with workers, where I cannot curl specifically in San Francisco. When I VPN somewhere else it works. I have tried on multiple different machine
WNot seeing a CAA record
only weird thing i'm seeing immediately
only weird thing i'm seeing immediately
Wwhat colo and what's your ray ID when hitting with the cert error?
JThanks @Walshy | Deploying for your message
I am not able to get any more information
The weird issue here is that I am able to deploy a new worker under a different domain and it works correctly... We actually have a bunch of domains pointing to the same worker...
Here are a few
# Some other weird notes and behavior
The issue is not operating system specific and is happening location specific.
When I join a VPN I do not run into this issue. Running from different computers, at different locations within San Francisco cause this issue to happen.
I have tried thes following environments
MacOS + Node + (Lower Haight SF)
MacOS + Curl + (Lower Haight SF)
Ubuntu + Curl + (Lower Haight SF)
MacOS + Node + (Downtown SF)
MacOS + Curl + (Downtown SF)
I have attempted on multiple devices and the issue persists. I tried clearing my computer's DNS cache as well and that did not help. I also was experiencing some issues with ipv6 and forcing it to be ipv4 does not help.
Right now I deployed another worker on another domain to unblock some customers
@Walshy | Deploying here are the Ticket IDs I have created
I am not able to get any more information
The weird issue here is that I am able to deploy a new worker under a different domain and it works correctly... We actually have a bunch of domains pointing to the same worker...
Here are a few
Domains that do not work
### Domains that do work# Some other weird notes and behavior
The issue is not operating system specific and is happening location specific.
When I join a VPN I do not run into this issue. Running from different computers, at different locations within San Francisco cause this issue to happen.
I have tried thes following environments
MacOS + Node + (Lower Haight SF)
MacOS + Curl + (Lower Haight SF)
Ubuntu + Curl + (Lower Haight SF)
MacOS + Node + (Downtown SF)
MacOS + Curl + (Downtown SF)
I have attempted on multiple devices and the issue persists. I tried clearing my computer's DNS cache as well and that did not help. I also was experiencing some issues with ipv6 and forcing it to be ipv4 does not help.
Right now I deployed another worker on another domain to unblock some customers
https://oai.helicone.ai@Walshy | Deploying here are the Ticket IDs I have created
#3276797 #3274350#3273394Wcan you do a
curl https://cloudflare.com/cdn-cgi/trace and send the output (but censor the ip=)Wi can check the tickets in a bit (please note, creating multiple just slows down the process)
Jthey are separate issues, maybe I can resolve them and put all my notes into 1 massive ticket?
Wok cool, if they're separate then it's all good
JWty - i tested sjc earlier and it seemed to work for me, i'll check it a bit more in a little. let me finish this hearthstone game
Wyeah not seeing anything weird, added myself to all 3 tickets and will chat to support folk tomorrow
JThanks Walshy - Happy to provide more information if needed
JHi @Walshy | Deploying still running into this isssue
