10 months ago
When I try to deploy my next.js project with CLI, which I am working on locally, it hangs at indexing and never starts. What could be the reason?2 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 📚 Migrate from Vercel to Railway
- 📚 Railway MCP Server (Experimental)
- 🧵 There is an error "RPC request failed with status 401 - Unauthorized" when using Thirdweb on the NFT minting page.
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 10 months ago
10 months ago
does it show that its compressing and uploading? if youre trying to push large files, indexing might take a while for it as well, typically any of these:
node_modules/
.next/
.turbo/
dist/
out/
shouldnt be pushed. you can try confirming by writing railway status and seeing if your project is linked and then writing railway up, but the entire cli docs are here. you should be getting Indexing -> compressing -> uploading. if you arent, then that's a separate issue