Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 20 2019 19:15

    Raekye on master

    (compare)

  • Jan 20 2019 19:15

    Raekye on release

    temporary fix for digital ocean… (compare)

  • Jan 20 2019 19:05

    Raekye on master

    misc changes more misc changes fix minor bug that's been aroun… and 1 more (compare)

  • Jan 20 2019 19:03

    Raekye on release

    temporary fix for digital ocean… (compare)

  • Jan 06 2019 19:10
    memtech3 commented #85
  • Jan 05 2019 23:58
    Raekye commented #85
  • Jan 05 2019 23:56
    Raekye commented #86
  • Jan 04 2019 02:05
    memtech3 commented #55
  • Jan 04 2019 01:54
    memtech3 edited #85
  • Dec 31 2018 21:07
    memtech3 closed #87
  • Dec 31 2018 21:07
    memtech3 commented #87
  • Dec 30 2018 21:38
    memtech3 opened #87
  • Dec 26 2018 22:19
    billybones1234 opened #86
  • Dec 26 2018 20:28
    memtech3 commented #55
  • Dec 26 2018 16:27
    memtech3 closed #84
  • Dec 26 2018 16:27
    memtech3 commented #84
  • Dec 26 2018 16:26
    memtech3 opened #85
  • Dec 26 2018 16:25
    memtech3 commented #17
  • Dec 26 2018 16:24
    memtech3 commented #17
  • Dec 04 2018 20:46
    Raekye commented #83
Raekye
@Raekye
hmmmm
Micah Guttman
@memtech3
GAMCOSOM IS DOWN!!!!
SSL probably expired
cloudflare says bad ssl
PLZ HELPZ
Must play minecraft!
Micah Guttman
@memtech3

MARKDOWN!

HALP!

Elizabeth
@ehllie_gitlab
is even using this?
Raekye
@Raekye
Sort of :P
TiTo418
@TiTo418
Hey raeye
Can I contact you through discord?
Raekye
@Raekye
Sure
Raekye#1149
TiTo418
@TiTo418
Just added you on discord
:)
tinker1234
@tinker1234
hi
is there a video on the project?
Bitan Saha
@BitanSaha13_twitter
Gamocosm not working after the update of 1.17....tried making multiple servers but they just wont run....getting the error - (Unable to start Minecraft: MCSW API error: HTTP response code 500, {"status"=>"badness"}. Please contact the server admin about this)
Saladino
@Saladino

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

Saladino
@Saladino

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

Which is destined to happen since the droplet was never created. I guess this is caused by an issue in the file Gamocosm/app/workers/setup_server_worker.rb that caused it to fail to create the server but didn't throw an error.
Raekye
@Raekye
Hi @Saladino , sorry for the trouble and thanks for all the details and your patience!
If I understood, I can think of two quick fixes (before going into the root problem or a permanent solution)
  • 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
Raekye
@Raekye
  • 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