Q: SSL issues after DNS setup – does the WordPress plugin avoid this?
I tried setting up CloudFilt via DNS (A record), but it caused major SSL issues: browsers say “connection not private,” and the certificate doesn’t match the domain. I also got 502 Bad Gateway errors. I tried all protocol options (HTTP, HTTPS, both) and used the CloudFilt SSL, but no success. My site has been running with a valid SSL from the host for years. Now I’m wondering: if I install the WordPress plugin instead of changing DNS, will it work without breaking SSL? Or is the plugin a limited solution? I’d love to use CloudFilt but had to roll back for now. Any help appreciated!
Oumkaltoum_cloudfilt
Jul 21, 2025A: Hello, Thank you for your message, and sorry to hear about the issues you’ve experienced.
The “connection not private” SSL errors and 502 Bad Gateway messages can happen when the CloudFilt SSL certificate hasn’t yet fully propagated, or when your host’s existing SSL is still active and conflicting with the new DNS setup. These situations are temporary and resolvable, but we understand they can be frustrating.
If you prefer not to change your DNS, the WordPress plugin is a fully functional option. It works well, especially on shared hosting, and does not interfere with your existing SSL. So yes, it should work without breaking SSL. This method provides solid client-side protection without any DNS change.
However, to unlock the full benefits of CloudFilt, such as network-level protection, advanced bot filtering, and reduced latency, we still recommend the full CDN/WAF setup when possible.
For personal assistance and to help resolve your current setup issue, feel free to contact us via email or through the chat. We’ll guide you step by step.
We appreciate your interest in CloudFilt and are here to help you get the best experience.
yorgokastriPLUShad the same issues with the ssl, emailed them, asked in chat, no response after 10 days
Stefan_Hamburg
Verified purchaser
Thanks for your reply, yorgokastri – that matches my experience, unfortunately. I haven’t heard back from support either. Since the SSL issues couldn’t be resolved and there’s been no response, I’ve decided to return the software. A pity, because I actually really like the concept.