angelo
Explore posts from serversBuild Possibly OOM on Builder V2
For customer NextBanana, the build suddenly fails: https://railway.app/project/a0dd0432-b630-4b33-9235-b63593fd7389/service/f5d52ff3-914f-4b41-b5af-281306fd040b/settings
58 replies
[WORKAROUND]: Eschew Railway Proxy connection via Cloudflare Tunnel
Hello everyone, we know its been a turbulent week for everyone on the platform. The Infrastructure team thanks you for your patience and your support as the Railway team has been fighting a number of network related fires on the platform.
We know that we will need to rebuild your trust in using some Railway networking products and our core product philosophy is to let you "take what you need and leave what you don't". This means allowing your use of Railway to be as modular as you need it to be to make sure that your business or workloads to be as resilient as possible.
A number of customers and the folks from the Network team validated a workaround that will let you tunnel connections via Cloudflare in case of any issues with Railway's proxy or if you want to have greater control over your networking experience on Railway.
We have published the following Template on Railway that you can deploy in your services that you can use to proxy traffic through Cloudflare.
Link here, guide is included in the template description: https://railway.app/template/cf-tunnel
75 replies
Payment Issues F.A.Q.
Hey there! Happy Holidays and Happy New Year! After recovering my company laptop from the sea, I couldn't help but notice that many of you might be having billing issues. Never fear, most everything in life has solution and so does this.
Why was I charged $1?
We hold a small amount (usually less than $1.00) to your card as part of a verification process. This charge is then immediately let go back to your card, so you won't see any change in your account balance.
The purpose of this charge is to verify that the card you provided is valid and belongs to you. It's a common practice used by many online payment platforms to confirm that the payment information you've provided is correct and that you're authorized to use the card. Railway gets many people who test cards from the scary web looking to host crypto-miners.
Why was my card declined?
Thats an answer best answered by contacting your bank but here are common errors we see some of our users face.
- Insufficient funds
- Incorrect card information: Railway checks for correct card information such as exp. date and ZIP code.
- Risk score: spamming transactions will trip up our systems.
If you run into an issue here, contact us via email: contact@railway.app
Why does it say subscription about to be renewed on the Dev Plan? I thought Railway was free?
Railway is not free. However, Stripe will notify you every month whenever you give authorization to a vendor that can charge you. You will recieve usage alert emails to see if you will go over the $5 credit grant.
I have an Indian bank card, how to do I give you my money?
The Reserve Bank of India (RBI) is the central bank of India and is responsible for regulating the country's monetary policy and financial system. In order to ensure the stability and integrity of the financial system, the RBI imposes certain restrictions on financial transactions in India.
In 2022, the RBI restricted Indian banks from giving autorization to vendors to charge ad-hoc amounts on the card. Because Railway is usage-based, you may have months where you have a bill, and some months where you don't. Railway offers credit based plans to help our Indian passengers on the platform pay for Railway and upgrade to the Developer plan.
These are the common issues we see, however, if you have an issue not resolved here. Email us, contact@railway.app - we utmost care about your privacy and use that channel to discuss sensitive personal information.
1 replies
OpenSSL Errors and Node
Hello everyone! Happy holidays!
We are near the new year, which means, its a perfect time for upstream breaking changes! Both mainline Alphine/Ubuntu have switched to OpenSSL 3, this means that your older Node projects (16 and below) might have issues. (Especially with Webpack and older versions of Prisma.) Fret not, there is a fix.
Troubleshooting
1. Enable the legacy Debian image
You can set an env var in Railway with
NIXPACKS_DEBIAN set to 1. This will make sure that OpenSSL 1.1 will be installed.
2. Enable OpenSSL 1.1 for Node. You can set this with setting an Env Var NODE_OPTIONS to --openssl-legacy-provider
You may need to check and pin some npm packages to certain versions, but know its not just you, a lot of builds have been messed by this change in mainline linux.
Happy Hacking and we will try our best to help you through this time. 🙂3 replies
