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
Did you end up finding a solution for this? We're having the same issue
Lindsey wrote:Did you end up finding a solution for this? We're having the same issue
Yeah, we're on 19.5 now and I believe it got sorted at least two minor versions ago.
What version are you on?
We're on version 19.6. It's actually a slightly different error, but it is still for the realtime notifications and causing them not to appear:
lia-scripts-body-min.js:70 WebSocket connection to 'wss://live-lia-pushy-service-v1.stage.lia.usw2.lithcloud.com/realtime/notification/640193c6-ed50-4da4-989a-f9a03e10ba4d/14?auth=kl4KrFUmGz6UWiveb2UG__b0btew7iAUA1ynWrIFvM_zf1BcaekvxjcDT_XeQ9hC9heLhur7kaMK3qyG2QpcRkaz77y0mItAP8piV6GH4Ww&X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.2.1-javascript&X-Atmosphere-Transport=websocket&X-Cache-Date=0&Content-Type=application/json' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVEDWe are talking to a member of Khoros now, but they cannot track down the source of the error.
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?
