Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI Companion사용자 그룹은 커뮤니티 구성원들이 비슷한 관심사와 전문 지식에 대해 협업하고, 교류하고, 지식을 주고받을 수 있는 특별한 공간입니다.
도움말 및 리소스는 유용한 Zoom 지원 리소스를 찾고 Zoom 커뮤니티 사용 방법 문서를 검색하며 최신 커뮤니티 공지 사항을 볼 수 있는 공간입니다.
이벤트 페이지는 다가오는 웨비나, 플랫폼 교육 세션, 대상 사용자 이벤트 등을 위한 목적지입니다. 기술을 향상시키고 다른 Zoom 사용자와 연결할 수 있는 기회에 대해 최신 정보를 유지하세요.
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.
날짜: 2025-04-04 09:30 AM
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?
날짜: 2025-04-05 01:05 AM
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:
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:
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.