a year ago
Not sure what I did to cause this. I had the deployment working at https://app.useultrance.com/ for my frontend last week, but now its giving 525 errors?
2 Replies
a year ago
just checking, is your ssl configuration in "full (strict)" in Cloudflare?
a year ago
do you have universal ssl enabled?
the *.p domains are records for a CF worker, not sure if that matters but just for further context
the *.useultrance.com is pointed towards railway
a year ago
I'm having the same issue.
Attachments
joshuanitschke
I'm having the same issue.
a year ago
I think the instructions here were not quite right:
https://docs.railway.com/guides/public-networking#add-a-custom-domain
I have got it working now that I have configured the www.zabaan.app instead:
I was getting the error when I had railway configured to the root domain.
Attachments
Same problem here. No one touched on the service and cloudflare returns error.. using the railway private network it's working (we're lucky that it is a microservice that we use 98% internally.. so it's not impacting our business)
a year ago
do you get a 404 on the public service domain?
a year ago
what is the domain in question?
that service runs on railway a long time ago.. domain: [guardian.goldcare.com](guardian.goldcare.com)
a year ago
does it not have a service domain?
a year ago
the domain works for me?
a year ago
ah gotcha
a year ago
redeploy please
a year ago
no, douglas had a seprate issue, you have something miss configured somewhere
bruh I think i just forgot to disabling proxying on the acmechallenge DNS record…
a year ago
oof
a year ago
that would do it
a year ago
no problem!
a year ago
!s
Status changed to Solved brody • 11 months ago