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 purely a Lithium code thing or can it also be dependent on their office's network policies?
Also found this discussion, which perhaps is related? Could it be a combo of Lithium and AWS not playing nice?
Strange, seems to be issue for CORS in pushy-sevice of realtime notification.
Did you end up finding a solution for this? We're having the same issue
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.
