No, sorry, it did work for some time, but now the error occurred again. We are working on it…
Update: A statement from the people working now on it:
“We are working on an alternative, hopefully more permanent approach to resolve this issue.
Unfortunately, the time required is similarly high to the first attempt. Therefore I don’t expect visible results today. Nevertheless, we are making progress behind the scenes.”