Hi, has there been any resolution to these issues by any chance?
I’ve been getting a similar error message this week after being able to use it reliably for quite a while (although it seems to be a sporadically reoccuring thing judging from similar posts in the forums).
