mricardi Posted Tuesday at 01:39 PM Posted Tuesday at 01:39 PM Hi guys, how are you? I recently migrated my app to Morty and changed the main domain I've tried starting my app, but I'm seeing the following error: Web application could not be started by the Phusion Passenger® application server (screenshot attached). I checked the Passenger logs in logs section, but they are empty. I'm not sure what the issue could be since my app hasn’t changed after the migration could you help me find out what error Passenger is encountering when trying to start my app? Thank you very much!! domain https://covireus-api.helioho.st/ Quote
wolstech Posted Tuesday at 06:01 PM Posted Tuesday at 06:01 PM Krydos can check on this for you. 1 Quote
KazVee Posted Tuesday at 06:06 PM Posted Tuesday at 06:06 PM In the meantime, could you please change the environment to 'development' using the steps provided on our Wiki here and let us know what the error message says after you've done that? The error message should offer more details about what's happening after you've switched to dev mode. Quote
mricardi Posted Tuesday at 07:32 PM Author Posted Tuesday at 07:32 PM Hi @KazVee! I changed the app mode and restarted my app, but I still see the same page with no additional data could it take some time for the change to be processed? Quote
KazVee Posted Tuesday at 08:02 PM Posted Tuesday at 08:02 PM 7 hours ago, mricardi said: I changed the app mode and restarted my app, but I still see the same page with no additional data could it take some time for the change to be processed? Yes, toggling the 'Application Mode' between 'production' to 'development' requires an Apache restart for the new setting to take effect, and Apache restarts every 2 hours. We'll add this detail about the timeframe to the Wiki page, so it's a bit more clear. (We mention the timeframe to wait in the Ruby on Rails page, so it'll be quick enough to put it in the Node pages, too.) We recommend keeping this setting in 'development' mode until your application has been successfully deployed without any issues/errors. Quote
mricardi Posted Tuesday at 10:03 PM Author Posted Tuesday at 10:03 PM Guys! thank you so much for your help! I followed @KazVee advice, and in the details I saw that I was missing a config file that is ignored in the repo, my bad 😅 Thanks again for your support! we can mark this ticket as solved 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.