500 internal server error

Tartar Sauce Media

unread,

Aug 31, 2015, 6:06:06 PM8/31/15

to Coronium IO

I was using the recent build of Coronium Cloud 1.92 on a ubuntu 14.04.3 lts server yesterday. Then my power went out on the server, so I rebooted and tried to connect to the admin web page. All I get is the 500 internal server error / openresty/1.7.4.1 page?? I tried to restart coronium a million times but nothing works. The only thing that fixed it for me was to completely uninstall/reinstall ubuntu then coronium. Any better ideas on how to fix this?

develephant

unread,

Aug 31, 2015, 6:14:48 PM8/31/15

to Coronium IO

Hi,

Log in with the command line and try running:

sudo service coronium reload

And let me know.

Cheers.

Observer

unread,

Jan 17, 2016, 8:31:26 PM1/17/16

to Coronium IO

im having the same problem just now, yesterday it was running. i tried logging in to my console and there were updates, so i upgraded thinking it will resolve the problem. now i tried this sudo command that you posted but what it says "sudo: unable to resolve host ubuntu-14-04-x64"

develephant

unread,

Jan 17, 2016, 8:42:33 PM1/17/16

to Coronium IO

Hi,

Where are you hosting your instance?

Cheers.

Observer

unread,

Jan 17, 2016, 10:11:35 PM1/17/16

to Coronium IO

i am using droplet from digital ocean, i already tried rebuilding droplet with same ip, i even tried removing it completely and re-install coronium. it was successful upto mariaDB, also done restarting from console or power cycle from digital ocean admin tools, i cleared my browser's cache and cookies, i tried logging in using admin/coronium server, then still internal server error

develephant

unread,

Jan 17, 2016, 11:41:33 PM1/17/16

to Coronium IO

Hi,

I'm going to spin up an instance and see what's going on.

Cheers.

Observer

unread,

Jan 17, 2016, 11:58:01 PM1/17/16

to Coronium IO

yes pls..i only have limited time for debugging. i can't access mongoDB since my instance is down. tnx.

develephant

unread,

Jan 18, 2016, 12:19:23 AM1/18/16

to Coronium IO

Hi All,

This can be fixed by logging in via SSH and running these 2 commands:

sudo sed 's/planet.coronium.org/planet.coronium.io/' -i /usr/local/coronium/http/admin/view_index.lua

And...

sudo sed 's/planet.coronium.org/planet.coronium.io/' -i /usr/local/coronium/http/admin/view_index.tpl

All you should need to do is refresh your browser. Some domains have been retired, but the updates are only in 1.93 on Amazon right now.

Cheers.

Observer

unread,

Jan 18, 2016, 12:25:27 AM1/18/16

to Coronium IO

checking...

Observer

unread,

Jan 18, 2016, 12:30:17 AM1/18/16

to Coronium IO

working! but need to setup another mongoDB...so this is not droplet issue then.

Reply all

Reply to author

Forward