As you have noticed, the server was offline for almost 6 days. The reason was that the server didn’t boot up after I changed things, and to make matters worse, I locked myself out of the server. So, it was impossible for me to reach it.
Since we have a system running on our server that isn’t officially supported by the provider and the case had to be discussed internally with a supervisor.
Of course, this happened with a weekend in between, and they did contact me after the weekend that they were willing to resolve the issue after I signed a consent form.
Due to personal circumstances, I didn’t react instantly, so today the issue was fixed by the provider.
I am very sorry for my stupid mistake, which certainly occurred after the server was offline in June, but for a financial reason, and I’m completely aware how unprofessional this comes across.
This was a classic case of mistake after mistake on me and not anybody else, certainly not the provider, since they were very flexible and helpful handling this issue.
As allready said: Stuff happens. Thank you for all the effort, and: You mentioning it come unprofessional is super nice and all, buuuuuuut here is the thing: I ain’t paying you! You being way more professional than most services I have to pay for…
Thank you for the open and honest words. I always think to myself: better bad news than no news at all.
I was a system administrator myself and can empathize too well.
Unfortunately I can’t offer my services, but what I can do now is finally donate a monthly fee. This may not help with such errors, but perhaps it will help to pay for the provider’s good service - after all, that’s part of it.
Don’t worry about it, it only proves you are human and humans make mistakes (me included haha)
I am glad it is fixed and thanks for your effort to fix it.
But on the other side are there backups that could have been restored? Well if you locked yourself out it wouldn’t be possible i guess but lesson learned.
May be the team can think/discuss a strategy what to do in a case like this? Just a thought though
Errare humanum est. Don’t worry. An error is always an opportunity to learn and improve , and not to stay “stuck” in our “comfort zone”. @Bryanpwo , I am 100% sure you’ll remember this and thus , will NOT make the same error in the future, but a new one, to learn something new. All good, and happy EOS is back, alive and healthy.
