There is a workaround listed at the bottom of that link. I did remove the link though because it contained an authentication token that is unique to your account.
At this time that is the only workaround we have available for this particular issue.
It looks like we weren't able to get access to the server in the ticket so we could not do any additional troubleshooting on our end. Can you reply to the ticket and continue working there to see if we can get better details?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.