Multiple RingCentral websites have certificate errors (success.ringcentral.com, support.ringcentral.ca, etc)

Forum|Forum|5 years ago
July 5, 2021
12 replies
1139 views

For those of us behind a firewall that checks certificate validity, the site success.ringcentral.com has an error, which makes it inaccessible. Please fix this.

I want to submit a ticket regarding an RC Yealink that's giving choppy audio under certain circumstances, and under those circumstances the RC iPhone app does not suffer the problem. I captured a PCAP on the firewall and all the stats appear to be perfect, but you can clearly hear choppy audio -- starting with the second ring -- and this only occurs with a Yealink, not the iPhone app. It also appears that RTP down is not encrypted (I can listen to it in Wireshark's RTP playback) but RTP up is encrypted (It appears empty in Wireshark's RTP playback).

log in

Best answer by Michael466549020

Sorry for any confusion with those two domains. The domain "success.ringcentral.com" is an old decommissioned site which is why it is throwing errors. All of the current support material is now found at support.ringcentral.com.

Please delete all old bookmarks containing "success.ringcentral.com". If you do find any URL with the "success" subdomain, and it does not redirect you to a "support.ringcentral.com" URL, please copy and paste that URL, or the URL for the page in which the link is located, to this thread so we can address it. Thank you!

Show previous replies

W

wfolta

Author

The First Step

Here's another example. I go to support.ringcentral.com and look at my tickets. I click on Create a Case and it says I'm not logged in. (I am, but it thinks not.) It pops up a small browser window and prompts me to login. After I enter the password, it tries to jump to https://rc-portal.force.com and somehow support.ringcentral.ca is involved and I get a certificate error. Here is a screenshot from Safari with the Web Inspector at the bottom of the page. Note that the certificate is support.ringcentral.ca, which I do not have bookmarked and do not explicitly type in. Note at the bottom that https://rc-portal.force.com is also involved.

So this is a show-stopper for me where I cannot submit a ticket and I've been asked by RC -- on a VoIP issue to open a NEW ticket. (That's a matter for another day, but I've been able to deal with this so far because I could update tickets by email reply. I cannot make a new one. The original was created due to a phone call to support, not by me.)