Guys, I am trying to access coronium docs (http://coronium.io/), and site appears to be down. I am also trying to access my EC2 server and I am getting a 500 Internal Server Error. What is going on?
Guys, I am trying to access coronium docs (http://coronium.io/), and site appears to be down. I am also trying to access my EC2 server and I am getting a 500 Internal Server Error. What is going on?
The site coronium.io has been “discontinued”, as develephant has recently released a new, Corona Labs backed, server platform called Coronium LS (see the pinned posts in this forum for more info).
As far as the internal server error, make sure that your launch security groups (find it in the AWS console -> Security Groups -> launch-wizard -> Inbound), are still the correct IPs, specifically the SSH key.
That link is still not working. It’s very frustrating that Coronium would just take down the docs server. Will anything change going forward due to this?
My EC2 just stopped working all of a sudden and I can’t login to my coronium admin anymore.
My inbound ip’s are:
HTTP
TCP
80
0.0.0.0/0
SSH
TCP
22
0.0.0.0/0
Every was working fine for many months up until now. Any ideas?
Ok this is very frustrating. Coronium - is there anything I need to do to get my EC2 / app working again? I can’t access my mongoDB etc and I am almost certain its due to this new change over to Coronium LS. Please advice, it is extremely urgent
I have an EC2 instance that has been running since early June, before the release of Coronium LS. The fact that you can log in to the EC2 server through the AWS console makes me think that the issue lies somewhere in your connection to the server.
To make sure that the server is working, are you able to go to the admin page on your server? In other words, are you able to get on the server dashboard?
@david668 Looking now.
My guess is you might be running an older version of Coronium Cloud which has an external dependency (which was removed for this exact reason). Do you remember what version you are running?
Just so you know the server is running, the 500 is only due to not finding the admin page. I’ll see what I can do to still support those versions.
The docs will be back up shortly, as in today.
My apologies, I’m sure it’s frustrating.
Back soon.
I can get into my Amazon EC2 console (https://ap-southeast-2.console.aws.amazon.com/ec2/v2/home?region=ap-southeast-2#Instances:sort=instanceId)
but I can’t get into my admin http://ec2-********.ap-southeast-2.compute.amazonaws.com/admin
Really need this working today… thankss!
And obviously I don’t want to lose my data 
I have been running my Coronium server since around Feb 2016. How would I even go about moving to the new server, while preserving my data? I am not that much of a backend server engineer and have very limited server knowledge. Also, if I were to go over to the new Coronium server, would this offer me any performance benefits?
It just depends. I’m only concerned because of the admin dependency. It’s bound to cause issues at some point in the future.
Let me get this fixed up and we’ll discuss that part next.
Cheers.
Your a legend, thanks!!
I have been going through the new Coronium LS docs and can’t seem to find support for logging in users, registering users, (mc:loginUser(myEmail, myPassword, function( event ) etc…) . Have you guys completely changed the way coronium used to work? Starting to get a little worried
coronium ls does not have a login system, you have to make your own(at least until it is added or a plugin is made)
ls is more open sources
That’s great. So the app I have been building for the past 8 months that relies on the original coronium features is now obsolete?
I don’t think coronium cloud is going to break for awhile. A lot people use coronium cloud and I am not going to put words in Chris’ mouth but I think he is going to support it for a while.
Any update Chris? I know you are flat out busy but I realllly need to login to my admin.
I see it is back up and running again… Thanks Chris!! Much appreciated. What should I do to avoid this happening again? If I upgrade to a newer Coronium Cloud version, will I lose any data? I don’t want to upgrade to Coronium LS because I lose all my Coronium cloud features (login, register, admin etc). How can I make this as future proof/long term as possible without having to change over? I have put a lot of money and time in my app and it uses ALOT of Coronium Cloud features. I can’t afford to start over and “build my custom cloud” on CLS.
Hi David,
My apologies for the time it took, DNS wasn’t updating as quickly as I would have liked. But I’m glad it came back up for you. In the near future I may give you a patch to run, but for now I have it set up so that you (or anyone) won’t have that issue again.
Coronium LS is still very early in release, so the components are still being dev’d out, but there are a group of folks here that are putting a lot of energy into it, so don’t count it out yet. 
Cheers.