25 days ago
Hello Railway team,
I'm on the Pro plan and I need help urgently. Two custom domains on my project are being blocked by Railway's edge, and my live shops cannot be reached on their own domains. Requests never reach my service.
Affected domains:
- scribbler.cc -> service art-backend (project mikisi-art-backend, production)
-
- graceart.art -> service sacred-backend (same project; blocked for over a week)
What happens (checked today, 26 Oct):
- http://scribbler.cc/ returns HTTP 302 to https://www.safebrowse.io/warn.html?url=http://scribbler.cc/ ("Potential Threat Detected")
-
- https://scribbler.cc/ fails the TLS handshake; no certificate is served
-
- graceart.art behaves exactly the same
-
- Both domains show as verified (green check) in the dashboard; the CNAME and _railway-verify TXT records are live
-
- scribbler.cc resolves to 69.46.46.24 (AS400940 Railway), the same IP as its xz1d5h3i.up.railway.app target, so DNS is correct
-
- curl -H "Host: scribbler.cc" http://69.46.46.24/ also returns the safebrowse.io redirect, while Host: art.mikisi.co on the same edge gets a normal response and a valid certificate
So the block is applied by Railway's edge, not by DNS or my application.
These are two legitimate online art shops that I own (MIKISI LLC; domains registered at Namecheap; payments by Stripe and PayPal; prints made on demand). They are new domains with nothing harmful on them. I believe an automated reputation filter flagged them because they are new.
Please could you:
- Review both domains and lift the block as soon as possible.
- Tell me if there is anything I need to change so they pass the check.
- Confirm that TLS certificates will then be issued automatically, or whether I should remove and re-add the domains.
I emailed [email protected] on 24 Oct and was directed here. The shops are live, so every day on the warning page is costing real customers. Thank you very much for your help.
Dennis Mlay
MIKISI LLC
1 Reply
25 days ago
We don't add that warning redirect, and there are no restrictions on your account. When we test the first domain from outside your network, it reaches your art-backend service. Plain HTTP redirects to HTTPS, and HTTPS returns a normal 200 response with a valid Let's Encrypt certificate for that hostname. The safebrowse.io warning page is coming from a filter somewhere between your machine and us, such as a DNS filtering service, ISP filter, router or security software. Testing from a different network, like mobile data, will confirm that.
The second domain isn't attached to any service right now. Its DNS does point at us, so our edge answers, but it has no service to send the request to and returns a not-found page with no certificate for that name. To fix it, add the domain in the sacred-backend service's Settings → Networking. Then create the CNAME and TXT records the dashboard shows for it at Namecheap. Once those verify, the certificate is issued automatically.
Status changed to Awaiting User Response Railway • 25 days ago
18 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 18 days ago