I emailed this to support, and they referred it to their 3rd line support. I guess they will fix it - or not. There is not much I can do now but wait and see if it starts working at some point.
I guess this is not a common problem, otherwise some user-agent spoofing option could fix this more generally(?)