Kyp

Show the actual (or perceived) error message. I wrote that installer, as is said above that is normal. It is reading your registry to see if you have that installed/available and then saying "yup". What part is repeating?

First the GMs and Devs (by and large) can't do anything about it. Only 3 of us can because it requires access to the back end, and it's all new post migration so we don't have any of the tools that made it easier for them in the past (yet). I was made aware of this just a few minutes ago. I will look in a moment.

First i've heard of any odd behaviors with the launcher client in a long time (we haven't updated the code behind it in quite a long time to boot). That said if anyone can replicate it might help to capture some details if we can. Even if just procmon data from the process to show where it might have "died" or hung up without resulting in an error state

It's on my list too, whichever of us is bored enough first. But yes, this is planned, the last expiration period we had was mostly due to my inattention to it after the migration.

It's back. Sorry about that.

sorted out now, should be.

Nah I announced it in the general chat channel about 20 mins ahead. Doing maintenance. Almost done. Should be coming back up now.

The languages we use are C++, C#. MySQL/SQL, PHP, some other odds and ends, but no Java I'm afraid, at least not since way back in the first iterations of the project long before it became multiplayer.

Back up, but i'm probably off for the night, i've attached a process monitor instance to watch the game server and see what happens when the alert I was seeing spawns. Try to let me know as soon as server is down (only once please since this pages both Zack and I). If I can isolate when it goes down I might be able to see what the actual fault is.

Suspect this had to do with a new security feature from the OS vendor. I have added an exception for this service and restarted the game server. I will check back to see if we have another crash in a little while.

I see it. This might be a little bit longer while I see if I can nail down what's happening.

Coming back up.

Coming back up / up.

Back up again. Let's see if it crashes again.

also, the maintenance is now done. I wasn't able to do it this morning as I'd mentioned last night on the game chat, but when it came to my attention it was down a short bit ago, I went ahead and completed it all before bringing things back up so you don't have to suffer *another* outage (hopefully) for a while. Let us know if anyone sees any highly unusual behaviors.

I believe what happened this time had more to do with the operating system than the game. I'd pre-installed patches intending to make maintenance faster when I did it, it decided I must have forgotten and rebooted itself. At any rate, Sunrise is back.

The certificate/inv-300 issue has been corrected on the server side. If you did any tweaking to 'workaround' it i would undo those tweaks now.

IF you used the workaround about disabling revocation checks, PLEASE go re-enable that. That opens you up to potential bad guys to not be checking for revoked certificates.

Might be some further maintenance when I get it all figured out.

Some issue with the new certificate I was trying, gonna look into that, restored the "Broken" ones that everyone was working around for now. Any workarounds should be functional again, let me know if this is not the case until I figure it out.

We're aware that the fix didn't work. Working on it.

Greedy? We don't get anything at all for doing any of this. The funds strictly pay for servers and IF we need some kind of software for further development. It is what it is though, I suppose. If you feel that way about the game, then you do.

Server is now up.

This was for support following a catastrophic issue thanks to some ransomware and some outdated software. Tehre is a "Server Status" thread pinned at the top of general discussion. If there's outage/downtime, report there and we should get notified to do something with it and do so at earliest convenience.

I was referring more to a 2nd instance. I gave a promise when we went live that there'd be no further wipes if we could possibly help it.