Kevin Crawley

In summary the error messages have reduced significantly today and RM know where the issues are.

When the Chromebooks were trying to authenticate, the sessions were going out to a Google IP address range/ranges. Unbeknown to us/RM, sessions to one of the Google IP addresses: 142.250.117.95 were timing out. Users were then seeing the 400 error message.

On further investigation, the Google server/IP in question has a certificate error

Google need to fix this by updating the certificate. RM have reported this to them, but when Google fix this, we cannot say..

In the meantime, RM have created various rules to work around this in the short term. The error reports have reduced significantly and things are much better…. RM will be pushing out a further change over night and this fix this for all sessions

Once Google install their certificate onto their server, RM will be able to revert these rules back to normal.

I’d also like to take this opportunity to thank the school community out there, who have worked so well with us, to help troubleshoot this. You efforts are very much appreciated!

Kev

I am told this issue should now be fixed. Thanks to the schools who reported this and apologies once again for the disruption.
Regards,
Kev

Good morning, Some users are getting proxy error pages today. RM confirm that there is an issue with the certificate on some of RM proxy servers.  An update is currently being rolled out.

You may wish to subscribe to receive updates from RM on this issue from their status page https://status.rm.com/

Apologies for the disruption. Hopefully it will be resolved soon.

Following on from several reports this morning, the transparent proxy fault is now resolved.

One of the proxies were misbehaving for transparent HTTPS traffic. RM restarted this and all is working correctly now. If anyone wishes to discuss this further, please get in touch.

Thanks