#custom domains problem

27 messages · Page 1 of 1 (latest)

sonic vault
#

cause this error because

hidden frost
#

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?

sonic vault
#

it's ok rn

hidden frost
#

nice!

#

I will keep this thread open for some time in case the issue reappears

sonic vault
#

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

hidden frost
#

I must say that this looks code related

sonic vault
#

it's ok rn

hidden frost
#

I see some kick endpoint in the error here

sonic vault
sonic vault
#

yep again i have the problem

hidden frost
sonic vault
#

external

hidden frost
#

and that's the one giving you a 503?

sonic vault
#

now is ok

#

yep

#

on localhost is ok but on railway i recevied this after the issues

willow scroll
#

This issue has nothing to do with Let's Encrypt's outage.

willow scroll
sonic vault
#

okokok thanks guys

radiant geyser
#

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?