Some of your registrants say the join link shows a "Not Secure" (or "Your connection is not private") warning and won't let them in, even though it works fine for you and for most people.
In almost every case this is not a problem with AEvent or with your webinar. It is a certificate (SSL) gap on the www version of your own website, which only a portion of clicks land on. Here is why it happens and how to fix it.
How the join link actually behaves
Your join link is smart. Where it sends someone depends on when they click it:
During the live event: the link takes registrants straight into your webinar. For a Zoom event, that means directly into Zoom. There is no separate web page in the way, so nothing there can show a "Not Secure" warning.
Before it starts, or after it ends: there is no live room to send people to, so the link instead redirects them to a page on your website. That is your Replay Page or Expired Page (the pages you configure in your campaign's Advanced settings), or your Custom Domain.
A note on automated and evergreen sessions: each registrant is tied to a specific session time, so someone can be sent to your Replay or Expired page even when they click close to the start time, if the exact session they signed up for has already finished. So this is not only about people who are clearly late.
Either way, the "Not Secure" warning never comes from the Zoom side. It only appears on this second path, when the link hands a visitor off to your own site.
Why only some people see it
A website can be reached two ways: the bare domain (yourdomain.com) and the "www" version (www.yourdomain.com). Each one needs its own valid security certificate.
Often the bare domain has a valid certificate but the www version does not. When that is the case:
Visitors who land on yourdomain.com are fine. This is why it works for you and for most people.
Visitors who land on www.yourdomain.com get a full-page "Not Secure / Your connection is not private" warning that blocks them.
Why do only some people hit the www version? Some phones, email apps, link scanners, and bookmarks automatically add "www" in front of a link. Those clicks resolve to the www version and get blocked, while everyone else goes straight through. That is why it looks random and only affects a portion of your audience.
How to check if this is the cause
In any browser, open the www version of the site your link redirects to, for example:
You should see: if a full-page security warning appears there, and the non-www https://yourdomain.com loads fine, you have confirmed the cause. The www host is missing a valid certificate.
How to fix it
The fix is on your website host, not in AEvent:
Log in to wherever the redirect page is hosted (for example Vercel, your funnel builder, or your web host).
Add the www version of your domain as a domain or alias so it is issued its own SSL certificate.
Set it to redirect to your primary (non-www) domain, so both addresses work and are secure.
If you use AEvent's Replay Page or Expired Page URLs, double-check that the address you entered points to a fully secured (https) page. If you use a Custom Domain with AEvent, see Custom Domains.
If it still happens after that
A small number of "Not Secure" reports can come from the recipient's side instead: their own antivirus or email-security software, or a corporate mail gateway that rewrites and re-scans links. AEvent cannot control those.
If you have fixed the www certificate and someone still reports a warning, ask them for the exact wording of the message plus a screenshot (including the web address shown), then send it to our support team through the chat widget. That tells us whether it is a certificate issue or something on their own device.