Hi — my custom domain fleet.mediccarellc.com (service web, project amused-peace, production environment) has been stuck on "Waiting for DNS update" for over 12 hours. The CNAME shows verified (green ✓); only the TXT verification record shows the warning. The DNS is correct and fully propagated. dig returns the single expected value, byte-for-byte matching what the Configure DNS Records modal shows: $ dig railway-verify.fleet.mediccarellc.com TXT +short "railway-verify=852bb542b82ceeb0b2a01c85199daee4d08afbf9fcdd04401d146d4f9b67a509" The CNAME also resolves correctly: $ dig fleet.mediccarellc.com CNAME +short → n3j1rpzm.up.railway.app DNS is hosted directly on GoDaddy (no Cloudflare proxy). The service is deployed and online (the .up.railway.app domain works fine). There was previously a duplicate/truncated TXT record, which I removed — dig now confirms only the single correct value is published. This appears to be a verification-state issue on Railway's side rather than a DNS problem. Could you manually re-trigger verification / clear the validation cache for this domain? I'd prefer to avoid removing and re-adding the domain due to Let's Encrypt rate limits, given prior cert attempts on it. Thanks! image.png

Hi, I'm trying to connect from my Railway app (Node.js) to the Spanish Ministry of Interior's SOAP API endpoint: https://hospedajes.ses.mir.es/hospedajes-api/ws/entrada The request fails with "fetch failed" error. This is a government API for tourist accommodation registration (required by law in Spain). Is this domain blocked on Railway's network? Would upgrading to a paid plan solve this issue? Thanks

Your workspace has been restricted. You cannot create new resources. Contact Support - whati need to do to get rid of the restriction? i saw that flaresolverr might be a problem?

I have my Railway deploys happening through a Github Actions deploy (https://github.com/XIVAuth/XIVAuth/blob/main/.github/workflows/component.railwaydeploy.yml), but this seems to come with a notable downside: I no longer have the environment variables like RAILWAYGITCOMMITSHA in my running services. Is there a way to restore this when using railway up or any other (controlled) CI flow? I'm using a CI flow specifically so I can control and gate when a release happens, rather than just firing things off of any commit. I could swap over to a release branch, though I'd somewhat prefer not to if it can be reasonably avoided. Or, an alternative way of asking this: is there a deploy command variant that states "deploy this repo at this commit hash"?

I'm subscribed to the hobby tier and I logged in today to do some maintenance on my deployments, but the dashboard says I'm on a trial and I don't see any of my projects. My account is connected to my GitHub (@tarunbod). I also saw that it said I don't have my discord account connected to Railway. I remember connecting it in the past, so I tried reconnecting and it said my discord is already associated with another Railway account, so I'm guessing this is a bug with the platform?

Hi, I'm trying to add a custom domain to my website, but for some reason, the setup instructions are wrong. I want to link my site to the domain www.vannisis.ro (note that the www is mandatory and not an error). Because I first tried to configure vannisis.ro directly instead of www.vannisis.ro, the Railway UI keeps displaying the setup instructions for vannisis.ro (non www) and insists they are not setup correctly. It waits for me to setup the record CNAME @ some.railaway.url but I want to setup CNAME www some.railaway.url I know this is possible because I have it setup for another site here in Railway. So, what can I do to fix this issue? Can I contact railway somehow?

I have some code that uses UNNEST for inserting data into my postgres DB. Over the last few days I am consistently seeing 'invalid byte sequence for encoding "UTF8": 0x00' errors when trying to insert data. It works both with a local DB, and the private network, however it also worked on the public url for weeks without issue until recently. Has anything changed with public TCP networking recently? I know the data is clean on the client, but is corrupting when in transit to the DB. Any help/info would be appreciated Deployment ID: 031d73cd-de05-43d2-ade1-caff029d8b69

11

Whenever we duplicate a service in a project, the target service gets created without the sealed variables from the original service. When we then manually re-create the sealed variable (still during the setup stage of the duplicated service, before it's been created), presumably due to some kind of bug, the service ends up being created with an empty value for that sealed variable. Because of how sealed variables work, you can't view them after they're saved. It's hard to notice this until production breaks later due to the missing variable, even though we entered the value correctly in the UI on our end. This has already broken production for us twice, and it's very difficult to catch before issues arise. Could this be fixed? Either by allowing sealed variables to carry over to duplicated services, or by fixing the bug that prevents them from being saved during service duplication?

hii I'm trying to use Cloudflare for SaaS (Custom Hostnames) with a Railway application to support multiple customer domains. My setup Railway application running normally. Railway default URL works. Added fwp.csam.in as a custom domain in Railway. fwp.csam.in points to my Railway app and returns HTTP 200. In Cloudflare for SaaS: Fallback Origin is configured. Custom Origin Server is set to fwp.csam.in. Customer domain example: si.sanyaji.top The customer completed all required DNS verification (TXT and CNAME). SSL certificate has been successfully issued by Cloudflare. Problem When I access: https://fwp.csam.in → Works (HTTP 200) https://si.sanyaji.top → Returns: HTTP/2 404 x-railway-fallback: true Railway shows: "The train has not arrived at the station." This suggests the request reaches Railway, but Railway does not route it to my service. My question Is Railway compatible with Cloudflare for SaaS Custom Hostnames without registering every customer domain as a Railway custom domain? If so, is there a required Host Header override or any additional configuration needed on Railway or Cloudflare? If not, is the recommended approach to place a Cloudflare Worker or reverse proxy in front of Railway? I'd appreciate any guidance from anyone who has successfully deployed Cloudflare for SaaS with Railway. Thanks!