Quote:
Originally Posted by Brad Mitchell
Hi David,
We take posts and feedback like this very seriously. It's always our goal to provide quick and accurate technical support. While this is typically the case, infrequently mistakes are made by people. We take pride in owning these mistakes if they happen and in providing a truthful, honest discourse with our customers. I'd like to provide some of that transparency here since we are having an open discussion.
I'm typically not keen on pointing fingers, but I feel the need to clear the air here. The broader, outage inducing issue that you faced was not brought about by lack of action from our team. Our technical team made the appropriate changes to files as necessary to support the changes you were trying to make. We performed these actions quickly and accurately, verifying our work after it was complete. The files in question were subsequently overwritten by your team via a git code push. Your team then raised a separate support ticket indicating that some thumbnails were not loading and that they suspected there was a CDN issue. Our team jumped into action and began diagnosing this issue.
I absolutely would have liked to have seen a faster resolution to your problem. I would have liked for our team to have provided you with more transparency on what they were working on behind the scenes. In a perfect world, this could have been a very quick fix. We didn't immediately jump to the conclusion that our customer had overwritten critical site files with incorrect values.
We've worked together for quite some time now, and I would expect that you would be familiar with the many ways in which you can contact us or escalate an issue. Starting a post on a forum isn't solution oriented or even the fastest way to resolve an issue. I am, however, glad that we are having this discussion so that others are able to recognize just how accessible our team is. Our team is available via the traditional ticketing system, but they are also available via phone 24x7. Our phone number is readily available on our website and every technician signs their replies with their direct extension (management team members include their mobile numbers). Additionally, you can raise an alarm by logging into our secure support portal and pressing the "emergency button" that pages all on-duty staff members. When this happens, it's expected that our support team has eyes on the issue within 60 seconds.
Sincerely,
Brad
|
No, that's incorrect this was from the 21st. That code overwrite issue was from today. Which was quickly solved, so thanks.
We are talking about yesterday. Dev notified Mojo team. 4 hours passed with no response from MojoHost.
Suggestion:
If there were some account "latest actions" notes or something maybe then the tech would have seen that the secret was updated the previous day by a different Mojo tech, then wouldn't have wasted time going down a rabbit hole to the CDN provider which was not the issue.
Yesterday, even after our developer reached out saying "Hey content isn't loading" - the developer didn't know the secret was changed.
Because you guys changed it.
Then your tech obviously had no notes on the account. So he assumed it was the CDN provider. And didn't reply to our developer for 4 hours. It wasn't until I came in (4 hours later) and started raising hell that anyone replied.
(In any case, no matter who's at fault,
4 hours to reply/update on an issue is totally unacceptable, but here you guys are again making excuses.)
I am shocked that anyone here would be ok with a website not displaying its content (which is the product) for over 4 hours.
----
Also, there is the matter of another issue (which started all this and why we had to change the secret anyway) which recently happened. We learned that our videos were being downloaded by people through Mojo/Highwinds CDN somehow circumventing a .htaccess file which only allows the videos to be served through an alternate CDN.
So people were able to download these videos and avoid having the tracer tag (username) embedded in the video to avoid pour piracy protection.
So we want to know why is it the default of your system to ignore .htaccess files? The whole point of them is to place rules to be abided by.