SSL Error for WSS
i am getting ssl error
unable to get local issuer certificate while connecting to a wss. it works fine when running in local. it used to work fine so far on railway too. suddenly stopped working32 Replies
Project ID:
N/AYou might find these helpful:
- cal.com railway error
- SSL certificate does not match custom domain
- socket.io error
⚠️ experimental feature
N/A
I dont have a custom domain
any misconfiguration in railway?
whats the domain youre getting the ssl error from?
it didnt
wss://eth-mainnet.g.alchemy.com/<api_key>
Cloudflare config issue
anything i should change?
Idk cloudflare has a lot of options surrounding SSL, play around
but i am not using cloudflare for anything
do you mean the url i am connecting to?
eth-mainnet.g.alchemy.com is registered on cloudflare
it works when connecting from local tho
what ws library
ethers - Rust
Complete Ethereum & Celo library and wallet implementation.
oh thats not even your domain
please be more clear in your questions
oh no. thats not my domain. its just the ws endpoint that i'm connecting to from the rust application that i'm running on railway
my application doesnt have any domain
i get it now
i tried setting the autogenerated domain. its still the same with that too
though this would be an issue with the crate / code, not specifically railway
i dont think so tbh, its working in local. and it used to work fine before too on railway itself
not sure what changed
railway hasnt changed anything with the rust provider itself, they've only bumped base images, try to rollback to a known working deployment and let me know how it goes
hmm an older version seem to be working fine
i'll check whats going wrong
now would that be running the same codebase as you are now, or have you since made changes?
an older version of the same codebase is running. newer version of the codebase is failing
older version of codebase, and not just a rollback?
i didnt try a rollback. i dont really know which deployment i had to rollback to
okay just reverted github or however that works on github?
not on github. just on my local. switched to another branch and
railway upwell i guess that does mean its a code issue then, if a earlier version of your code works
yeah guess so. looking into it
alright, good luck!
it was because the docker container was missing ca-certificates
added this and fixed:
You where building your own Dockerfile, you should have said that!!!