- Messages
- 6,381
- Location
- The Oregon rain forest
Me too....I was fine yesterday.
Me too...I bet Josh is super frustrated by now.It's still happening this morning.
I only encountered it once.I had a feeling. I was hoping for the best but I still can't reproduce it reliably so I wasn't sure. If anything else funky happens or any more info or patterns become apparent please LMK
If it helps troubleshoot it, I've been experiencing the error in Chrome and Edge, but not firefox. I haven't experienced it yet today, but I also only just was able to log in as I had work.I don't know if this helps any, but I've accessed the site through a Chromebook using the latest version of Google Chrome, a MacBook with Safari version 15.4, and an iPhone running whatever the latest version of Safari happens to be on the latest version of iOS. The issues that I've faced have been primarily on the Chromebook/Chrome browser. With that setup, any attempt to access any part of the site was almost immediately met with the Error 520 notification. For the most part, refreshing that screen would take me to the original webpage that I was looking to get to, though there were a handful of occasions when it would generate another 520 Error. I have had much fewer errors pop up while using Safari on MacBook and none while using the Safari app on iPhone. I'm not sure if the coding for the mobile browser on iPhone isn't affected, or if there is something in Google Chrome that keeps tripping that error.
I'm using the following:
Google Chromebook Go
Apple MacBook Pro
iPhone 13 Pro Max
I don't have a windows computer to try it on and I haven't tried accessing the site through Edge, Firefox, Opera, or any other browsers beyond Chrome and Safari. Chrome has produced the most consistent and numerous errors, though I use the Chromebook for the bulk of my internet usage.