CORS errors for notifications
Hey folks. We're not running any weird integrations, but our moderators in a remote office are seeing this a lot in the console. It seemt eh OOB Lithium notifications are having issues. Is this pure...
Forum Discussion
Curious if you're getting the same issue from different locations, or just one. Tried a VPN?
Just asking since this looks like a server/DNS error and not something on your side.
Yeah, so I tried on our company wifi, our guest wifi, and at my home wifi, and all locations I see the error. The Khoros support member told us he is not seeing the error on his end, but when I asked him to try on his home wifi, he saw the error. This makes me think there is something on Khoros's wifi that is allowing them to bypass something that would cause this?
Interesting. So when they were on their work/Khoros network they could connect. Can they VPN to work from their home? Wondering if that works.
Cuz if you gotta be at a Khoros office to be able to connect I'd suggest that may be a problem 🙂
Yeah I'm not sure. But yeah they can still connect, it's just the realtime notifications don't show up and give us the WebSocket exception unless they are connected to Khoros wifi
And yes this is on stage
