19 days ago
I setup an account, but my trial expired and I haven't tested anything yet. I tried the free plan, but the deploy fails. The 'Diagnose' button is showing, but clicking it does nothing. In the logs it says on the free plan I have to set the deployment to serverless, but mine IS set to serverless, and the deploy still fails?
4 Replies
19 days ago
Your Wiki.js service does have serverless enabled, but your project also contains a Postgres service, which also needs serverless enabled on the Free plan. Every service in the project must have serverless turned on - you can enable it on the Postgres service in its Settings under the Deploy section (look for "App Sleeping"), then redeploy both services.
Status changed to Awaiting User Response Railway • 19 days ago
19 days ago
The postgress service DOES have serverless enabled. and it has deployed successfully. I tried re-deploying both the postgres, and the wiki.js, and the postgress redeployed successfully, but the wiki.js still fails.
Status changed to Awaiting Railway Response Railway • 19 days ago
Status changed to Open brody • 19 days ago
mayori
Do you have any errors on your Deploy Logs on your wiki.js service?
18 days ago
In 'Details' it says deployment failed, and there is a ´diagnose' button, but when I click it, it animates for a second but doesnt show anything. Where do the diagnosis results go? In 'Build logs' it just says 'Free plan deployments must be serverless. Please go to your service settings and turn on the serverless flag.' But both the wiki.js and the postgress ARE set to serverless. In Deploy Logs it just says "No logs in this time range Logs will show up here as they are found '. Even though I've tried to redeploy multiple times.
But, I just created a new environment, called 'Test' , and both services deployed successfully in there. They just wont deploy in the 'production' one. Can I make the test environment the active one?
Ahh, don't worry. I got it to work. I turned serverless off for wiki.js and redeployed, which failed, then I turned serverless back on again and deployed again, and it worked! I'm sure I tried that last time? Oh well. I think it's OK now.