Yes, Vivaldi generally works well with Let’s Encrypt certificates—it's built on Chromium, just like Chrome, so its behavior with SSL/TLS should be nearly identical.
However, the error you're seeing (“connection to the site is not secure”) usually points to one of a few common causes, even if your certificate seems valid. Here are some things you should check:
Check the full certificate chainLet’s Encrypt certificates rely on intermediate certificates, and not serving the full chain is a common issue. Some browsers (like Firefox or Chrome) can fetch missing intermediate certs, but Vivaldi sometimes won't.
Make sure your web server is configured to serve both your cert and the intermediate (e.g., fullchain.pem, not just cert.pem).
Verify system trust storesSince you're seeing the issue on both macOS and Linux, it might be that the version of ISRG Root X1 (Let’s Encrypt’s root certificate) on those systems is out of date or mismatched.
Update your system's CA certificates:
On macOS: make sure the system is updated and Keychain Access trusts the ISRG Root X1.
On Linux: run sudo update-ca-certificates (Debian/Ubuntu) or the equivalent on your distro.
Check for hostname mismatches or mixed contentVivaldi may also throw security errors if:
Your SSL cert is for www.domain.com, but you're accessing domain.com without a redirect in place.
You're serving HTTP (non-HTTPS) assets on an HTTPS page (mixed content).
Check for HSTS preload or old STS headersIf your domain was previously submitted to the HSTS preload list or sent invalid HSTS headers, Vivaldi may enforce them differently.