#custom domains problem
27 messages · Page 1 of 1 (latest)
I don't think the error you sent is related to the outgoing incident
Could u give a bit more info on what's happening? What are you trying to do?
I have a chat overlay for Kick streaming and I’m using Axios for fetching. I didn’t have any issues until your recent problem with custom domains appeared.
it's ok rn
actually was solved for 2-5 minutes '[7TV] cosmetics for name failed (try 3/3): ECONNRESET: read ECONNRESET' again
console.log
[7TV] cosmetics for name failed (try 1/3): 503: Request failed with status code 503
[7TV] cosmetics for name failed (try 1/3): ETIMEDOUT: Error
I must say that this looks code related
it's ok rn
What are you trying to do here? a req to an external service?
I see some kick endpoint in the error here
I'm trying to fetch the API and I got those errors, could it be from my code? Or… (now is ok)
yep again i have the problem
I'm trying to understand your infra, this 'API' is hosted on Railway or is an external service
external
and that's the one giving you a 503?
This issue has nothing to do with Let's Encrypt's outage.
^
okokok thanks guys
Hi I have a frontend service connected to a custom domain like OP but the deploy logs aren't showing any errors. But I keep getting 502 errors when trying to access the domain? Let's Encrypt looks like it's back up now too so not sure what could be the problem?