Before that I was using Gibbon on local server with https, but now I moved to cloud in heroku with clear DB, I moved database and config file there, but after few hours whenever I go to my domain it redirects me to the installer and I put the DB keys, it starts working, again after few hours it redirects me to the installer. Why?
Hi Faizan, that is a very interesting issue, and not one I’ve encountered before. Please can you check, once you notice the redirection to the installer re-commencing, is your /config.php file still in place, and readable by the web server process? Thanks! Ross
Also when I re-run the installer it gives me error on step 2 i.e ‘Errors occurred in populating the database; empty your database, remove …/config.php and try again.’
but when i hit the URL again by removing ‘/installer/install.php’ it works fine for next few hours
@admin said:
Hi Faizan, that is a very interesting issue, and not one I’ve encountered before. Please can you check, once you notice the redirection to the installer re-commencing, is your /config.php file still in place, and readable by the web server process? Thanks! Ross
Hi Faizan, sorry for the delay. Busy times here in Hong Kong at the moment.
The only reason a redirect to the installer should occur is that /config.php is missing, and so I am at a loss to explain what you are seeing.
When you get back to the installer, step 2 will give an error if you are using the same database name as the first time you installed.
At this point I think it would be best if you delete you entire installation, including the database, download the code anew, and then try a fresh installation.
After 24 hours it redirects me to installer again, then I add the same DB credentials, it takes me to step 2, then I remove ‘/installer/install.php’ and it works fine
I did a couple searches about Heroku and it sounds like this may be something with the cloud platform, rather than in Gibbon. According to some search results, “Heroku’s Cedar stack has an ephemeral filesystem which is cleared every 24 hours”. Here are some of the results I found (they sound familiar to what you’re seeing): django - Heroku app database resetting - Stack Overflowhttps://docs.bastionbot.org/install/install-on-heroku
Hmm, your situation sounds unique, I don’t think we’ve seen anything like it. Gibbon doesn’t have a mechanism to delete the config.php file, so I’d be tempted to say there’s something in the system configuration that may be causing this. You may need to try some more troubleshooting, such as: if you add a plain test.php file to the root, does it also disappear? Are there any error logs that occur before the re-install prompt? Any error longs on the cloud platform side of things?