cancel
Showing results for 
Search instead for 
Did you mean: 
The Zoom Community will be placed in read-only mode January 9th, 2026 through January 22nd, 2026 to deliver you a new and improved community experience!

The community will still be accessible, however, the creation of any new discussions or replies will be temporarily unavailable. We appreciate your patience during this time.

Domain allow list issue: "Domain uses invalid SSL certificate" for youtube-nocookie.com

jz1
Newcomer
Newcomer

We have an app on the Zoom marketplace.

 

We're trying to add the www.youtube-nocookie.com domain in the allow list for privacy reasons (see https://support.google.com/youtube/answer/171780?hl=en#zippy=%2Cturn-on-privacy-enhanced-mode).

However, when trying to add this domain, we get the following error (see screenshot):

 

> Domain violates Zoom App Marketplace domain policy. Reason: Domain uses invalid SSL certificate.

 

Do you know why that happens and how to fix this?

 

Here's an example link:

https://www.youtube-nocookie.com/embed/jNQXAC9IVRw?rel=0

 

The 2nd screenshot shows the certificate is valid, so I'm not sure why Zoom displays that error.

2 REPLIES 2

drmikejones
Newcomer
Newcomer

Just landed on this report as I had a similar albeit non-zoom related issue.

The youtube certificate used, while it is valid for youtube.com and www.youtube.com, is also valid for www.youtube-nocookie.com but not for youtube-nocookie.com. Could that be the issue here?

It's been a long time, so I don't exactly remember all the details, but I see both domains are now approved in our Zoom apps:

jz1_0-1743839226014.png

 

I think we were able to get them approved by including additional information in the review notes for the Zoom admin reviewer. If I change the domain, I can see a field to include that information:

jz1_1-1743839387181.png

 

Note that when we experienced the problem, Zoom apps were still new, so the review process wasn't always straightforward. I imagine it's now much smoother.

 

The youtube certificate used, while it is valid for youtube.com and www.youtube.com, is also valid for www.youtube-nocookie.com but not for youtube-nocookie.com. Could that be the issue here?

 

I don't think it was the only cause back then because both domains were rejected at that time.