So, the guy that was in charge of making sure the certificates were up to date, he left the company?
Really bush league. What about all the people who didn’t get on to the forum who were confronted with this problem? Not a very good advertisement for Roon’s competence.
Its unfortunate but these things happen.
Maybe they weren’t measuring what they thought they were measuring and didn’t get an alert. Or maybe they forget to measure it.
Either way, this happens to all Ops at some point. I’m pretty sure they are on top of it now though.
It’s not easy and it is not hard. But it is a process that makes it easy for renewals to fall through the cracks. You can bet that Roon will adopt some new procedures or at the very least do a better job of following the ones currently in place. Again, it’s not the end of the world.
The problem is that by splitting it out and titling it as you did, it was (unintentionally) made to seem much more cutting than it originally was when it was just one simple comment in reply to your post that the certificate problem was fixed.
Still don’t understand how re-certification fell thru the cracks. That’s what task lists and calendars are for, but not worth any more back and forth.
Some things happen and are unavoidable. When they do, you fix them and apologize. However, something such as an expired certificate should never happen. How hard is it mark this on a calendar and assign a couple people to make sure it gets updated? I have the same reaction when people complain about Roon requiring a credit card for a trial. They say they might “forget” to cancel in time. No excuse for “forgetting.” Go buy yourself a pencil and paper if necessary.
Looks like they are using free Let’s Encrypt certificates. Let’s Encrypt certificates expire after just a few months. But, they have utilities to keep them automatically updated/refreshed. I guess, though, like most software including roon, it doesn’t work 100% reliably. Maybe 99.99% of the time, but pretty bad timing for the .01% sometimes.