Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't default to coldbird adhoc server, it doesn't run anymore (?) #9984

Merged
merged 1 commit into from
Sep 28, 2017

Conversation

hrydgard
Copy link
Owner

@hrydgard hrydgard commented Sep 27, 2017

If I've understood things correctly. See #7268.

@hrydgard hrydgard merged commit 479eb48 into master Sep 28, 2017
@hrydgard hrydgard deleted the remove-coldbird branch September 28, 2017 06:31
@asl97
Copy link

asl97 commented Oct 29, 2017

The issue you linked doesn't (no longer?) said anything about the server being down, it's about tunneling through one port.


Coldbird's aemu server went down on 09 Jun 2017 (the modified date on the status page), It was down for at least 3 month.
It was brought back up some time before 10 Sep 2017, the status server remains down but it's not require for the aemu feature to function.

Afaik, The dev team gone AWOL, nobody announced anything when it was down, nobody announced anything when it was partly brought back up.

There is no telling when it will go back down again.

@MrColdbird
Copy link
Contributor

@hrydgard The dedicated server was managed by our former team-member Belldandu which went rogue on us, installing backdoors on our server before going into hiding and secretly mining us for resources... I've discovered this not so long ago and took the appropriate steps to ensure things were done properly this time around.

In hindsight I could slap myself in the face for ever trusting the guy, or handing over control / management of the server in the first place...

I've spent most of my time scratching together the bits and pieces of data and have since then taken control of my own server and domains again, moving them to a new host and manually sifting through every bit of data to ensure not a single piece of malicious code survives the move.

Sadly, due to my busy job I haven't had the time to do an all-nighter and get all of this done in one blow, however, the adhoc server is back up and running and pro.coldbird.net is undergoing DNS propagation this very moment, meaning that the status page for active connections should be back up with it within the next 24 hours.

@hrydgard
Copy link
Owner Author

Oh, yeah, I know all about trusting the wrong people to manage sites for you... Glad you've got it sorted.

Happy to restore the default setting, good timing too as I'm about to make a release. Should I set it to "coldbird.net" or "pro.coldbird.net" ?

@MrColdbird
Copy link
Contributor

@hrydgard Up to you, they both point to the same host and I don't plan on pulling up a separate dedicated box just to split them.

pro.coldbird.net will take a bit to propagate though (at least for some users), as not all DNS servers update as frequently as they should.

@hrydgard
Copy link
Owner Author

Okay, I just made it coldbird.net.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants