New problem solver
•
38 Messages
Private Chat not working
Hello,
I've had some communication with @Comcast Business via Private Chat in these forums, but now if I click on the chat buble, the page turns white with 3 black dots in the middle that rotate black/grey/white like something is loading & it hangs. I can't view any of my messages.
I've tried IE/Chrome/Firefox, disabled all extensions, and tried multiple computers with the same behavior. Can someone look into this?
Thank you,
Robert
Comcast_Gabriel
Official Employee
•
297 Messages
4 years ago
Hi, @rob__jr! Thanks for communicating with us on our Comcast Business Forums page and for your patience while waiting for a response. We have made some updates recently. To send us a private message, please try again by clicking the "message" icon on the upper right page of our forum page. Once you click on that, input our shared handle Comcast Business to send us a private message. Please let me know if this helps.
0
0
rob__jr
New problem solver
•
38 Messages
4 years ago
If I click on that message icon in the upper right, I only get the 3 dots on a webpage as shown above.
1
0
rob__jr
New problem solver
•
38 Messages
4 years ago
I did try clearing my cache, but same issue. Anything else I should be trying? I've tried multiple browsers and cleared cache in all of them.
1
0
rob__jr
New problem solver
•
38 Messages
4 years ago
There was an upate for chrome. Went from Chrome 88->89 and still the same issue.
0
0
rob__jr
New problem solver
•
38 Messages
4 years ago
So this is working today after disabling my HE.Net ipv6 tunnel as well as ublock origin extension. Will see if it keeps working or not...
1
0
rob__jr
New problem solver
•
38 Messages
4 years ago
So I figured out how to work around this.
I have trouble getting to the ipv6 address of prod-community-mqtt.sprinklr.com which is part of the private chat web page. You can see this by using the ipvfoo plugin on chrome or firefox and navigating to private chat.
The ipv6 for prod-community-mqtt.sprinklr.com is over 30 hops away from me. If I null route 2601:1f18:af:af00/63 then it's forced to use ipv4 and works.
Might be worth reaching out to your webteam for them to do some testing under ipv6.
(edited)
0
0