Issues accessing LCR this week

Has anyone else had issues with LCR on the web this week? Wednesday night I could get in to the church site in general I think, but when I went to use LCR I often got either site not found, or certificate errors, or errors from the site itself saying the operation failed when trying to move records in and out for example. I tried on Firefox, Chrome, and Edge. It was intermittent though and different errors. I called support and they just said to clear my cache, which I tried and didn't help. So I gave up and tried last night and it was fine. But I'm having issues again tonight.

they often go to the Clear Cache solution... and often it works.. BUT sometimes the servers are just overloaded. That wouldn't explain the certificate errors though.. Unless it was just an internet connectivity issue on your end or thiers that prematurely ended the connection. Are you using Wifi? is so try with a cable or a different way to get internet. Also, try speedtest.net to see what your internet is like. it can sometimes be great and other times garbage, especially on Wifi.

Yeah I thought it might be an internet issue on my part, I am using wifi but I'll try a cable next time. My computer is right next to the router (netgear nighthawk), and I had it hardwired but had to take it with me recently. I work from home and have a 1G fiber connection and it's generally pretty reliable. The router that came with my service was garbage and speeds would often drop to nothing. When I do have an issue I usually check it and it always checks out fast, but I wonder if service providers prioritize speedtest so they look good. I wasn't having issues with any other sites though or the general church site I don't think, just LCR.

Having trouble again this morning. Internet connection and speed is fine, main church website is fine, just getting errors with LCR.

I continue to see errors. Some research suggested it might be caused by TLS key logging, but I could not find the setting to disable that. And today I experienced the exact same errors on our clerk computer at church.