HALP!
Hey Raekye,
I ran into a problem using gamocosm & now my server is in an error state that I can not resolve myself:
After starting the server I got an DO API error 404. Looks like the request used an ID that wasn't known to DO. I suspect it tried to querry the server IP and could not reach the droplet, since the droplet was never created. (Why that happend I do not know, the snapshot ID is correct & reachable over the API, money is there etc.)
All other servers on gamocosm work as intendet & can be turned on and off - so I do not belive that this is a general API problem like yesterday.
On the DO side everything looks fine: the snapshot is sitting there, but gamocosm refuses to start the snapshot as a new droplet.
Gamocosm shows the "Turn off" & "Reboot" buttons, but those just cause another 404 since there is no related droplet to turn off.
So I need a way to set the server back to the state where the "start server" button appears again, but that functionality isn't there. I guess you could change the state of my server back to "not running" so I can test if it would start up fine now.
If I should provide any further information like screenshots please contact me.
I hope you can help me,
Konrad
2022 Jan 26 (08:33:00 PST)
app/workers/wait_for_starting_server_worker.rb:19:in `perform'
Error communicating with Digital Ocean while starting server: Digital Ocean API HTTP response status not ok: 404: {"id":"not_found","message":"The resource you were accessing could not be found."} . Aborting
- You can PM me your server URL (like gamocosm.com/servers/abcd....) and I can reset the digital ocean remote ID, which should let it start from the snapshot properly
- Effectively recreate the server: Under the "advanced" tab of your server, copy and delete the snapshot ID (like set it blank and save). Also copy/save the MCSW key. Then delete the server. On the delete page, it should list the digital ocean resources Gamocosm will delete. It will probably list a droplet ID if I understood the problem (but the droplet doesn't exist) but it should delete fine. But make sure it's not deleting the snapshot. Then create a new server (like from Gamocosm), but don't start it. Go to advanced tab, set "remote setup stage" to 5, and update the snapshot ID and MCSW key to be your snapshot and old MCSW key. Also update SSH port to 4022 (or whatever else you had changed it to in your old server). Everything else can remain the same (again, unless you also changed it yourself in your old server). You should be able to start it now