Hey @tonyd I can’t offer any help but can report that I experienced this as early as two days ago in both Chrome and Firefox as well, but it seems to not be an issue today.
Our IT was performing some maintenance on our network at the time, so I’m not sure of what the cause issue actually was. The error points to a localhost IP so the network maintenance may have been coincidence…