railway up: Failed to upload code with status code 403 Forbidden
I did as always:
wasp build
cd .wasp/build
railway up
returns:
✅ --- Your wasp project has been successfully built! Check it out in the .wasp/build directory. ---
rootall@Nerox-LpTp:~/apps/AI-Doc-Chat/AI-Doc-Chat/app$ cd .wasp/build
rootall@Nerox-LpTp:~/apps/AI-Doc-Chat/AI-Doc-Chat/app/.wasp/build$ railway up
Indexed
Compressed [====================] 100%
Failed
Failed to upload code with status code 403 Forbidden
3 hours ago worked, did railway logout, login, link again but nothing. Still have credits14 Replies
Hi @NEROX. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources do not contain specific information about the "Failed to upload code with status code 403 Forbidden" error when running railway up after building a Wasp project. The available sources discuss deployment steps, environment variables, and some issues with Docker and dependencies, but do not address this particular 403 error during the upload step.
Given that you have already tried logging out, logging in, and linking again, and you still have credits, the issue might be related to Railway's permissions or a temporary service-side problem. However, I cannot confirm this based on the provided sources.
If the problem persists, I recommend reaching out to Railway support or checking their status page for any ongoing issues. If you find a Wasp-specific cause or workaround, please consider sharing it with the community for future reference.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai I have updgraded plan, created another service in the same project, another project and nothing (Failed to upload code with status code 403 Forbidden
).
I went to another Wasp app, built it and it started to upload.
Please reason.
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the knowledge sources provided, there is no explicit information about the cause of a 403 Forbidden error when running railway up after building a Wasp project, especially in the context of some apps working and others not.
However, here are some relevant observations and reasoning based on the available information:
- A 403 Forbidden error typically indicates a permissions issue, either with the Railway project/service or with the credentials being used. Since you mentioned that uploading works for another Wasp app, this suggests the problem is specific to the project or service you are trying to deploy, not your Railway account or global permissions.
- There is no mention in the sources of a Wasp-specific configuration or build artifact that would cause a 403 error during the upload step to Railway.
- The only related issue found in the sources is about HTTP status codes for authentication in Wasp apps, but this is about API responses from the app itself, not deployment errors from Railway or the CLI tool Discuss how we use authentication.
Given this, the most likely causes (based on general reasoning, not the knowledge sources) are:
- The specific Railway project or service may have a misconfiguration or a permissions issue.
- There could be a temporary issue on Railway's side affecting only certain projects/services.
- There may be a difference in the way the two Wasp apps are set up, but the knowledge sources do not provide details on what that could be.
Since the knowledge sources do not contain enough information to provide a definitive answer or a Wasp-specific solution, I recommend checking the Railway project's permissions, service settings, and possibly reaching out to Railway support for further assistance. If you discover a Wasp-specific cause, please share it for future reference.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
Well, it seems that there was some problem with the build of that app.
rm -rf .wasp
rm -rf node_modules
rm package-lock.json
and build again, fixed the problemDo you like railway better than fly? Is it cheaper?
In these 10 days I have been with Railway the expense has been $1.17. It looks like it would come out to less than $4 a month. And Railway DOES offer a $5 trial.
Fly comes out to about $12 per month.
Besides I like their interface much better, everything is sorted by projects (if I have 3 apps I see 3 sorted projects and not 9 single services as in Fly), you can have only one replica or as many as you want (Fly creates 2 per service), rollback or redeploy, they have railway ssh for quick connection, the panel works very fast (rather as it should be, Fly's seems very slow to me like getting data from Mars).
Maybe some of these features, Fly also have it but in all these months I didn't discovered them.
It feels much better. I can say that my experience in these 10 days with Railway has been better than with Fly and I hope I can keep saying the same.
Besides, when I opened this question here I also opened it in their help center and received possible solutions from the users themselves quickly, apparently they have an automatic Bounty system for solving tickets that rewards with $ credits.
On Fly I remember browsing through their deserted community and only seeing users replying to each other “Same thing is happening to me, any news?”
All this makes me more confident in Railway if I think about the future.
This is the server and the db.
The client I have it on Cloudflare for free.
Hmm I read some fly.io propoganda that railway was more expensive and have not switched thanks for the feedback!
Yeah, I also thought the same https://x.com/ImSh4yy/status/1762575172576428241 source https://getdeploying.com/reference/data-egress
But I'll see what happens in the next weeks
Data Egress: What is it and how much does it cost?
List of data egress costs for major cloud providers with tips on how to keep costs down.
Hey fellas, you should be happy to hear Wasp will soon support Railway deployments natively 🙂
https://github.com/wasp-lang/wasp/pull/2578
GitHub
Deploy with Railway support by infomiho · Pull Request #2578 · wa...
I've extracted some of the generic helpers to the top level
I've added support for deploying Wasp apps with the Railway CLI
We have to wait for this to be released before Wasp can ...
Btw, any problems still unsolved in this thread? Seems like there aren't but better safe than sorry
Uhm, I think I'll wait for the cli -- most everything is updated here https://wasp.sh/docs/deployment/deployment-methods/paas#railway
But some stuff is a bit confusing having to run another script the entire time was a bit 🥴
every time I update my app do I have to go to both my server and client and go type
ah I see I think you are going to make like
wasp deploy railway deploy yeah that would be really nice, I'll wait a little bit and work with fly
Cool! Would it also work to deploy for example only Server? With
wasp deploy fly deploy I think I remember that everything was deployed. But now I only have the server and db in Railway.I think you'll be able to mix and match but am not 100% sure
@miho Will it be possible to have some stuff on fly and other stuff on railway?
We will offer options like
--skip-server and --skip-client so you'd be able to call two commands to deploy the client to X and server to Y.