Thank you. I suspect you had enable automatic https rewrites? If so, cloudflare was a bit of a “bandage” over you site code. Where your code specifies http, the rewrite will ensure it loads over https.
There is a CommunityTip that explains the issue from the point of view of customers that see a mixed content error, I think part of that tip may help resolve the problem, Community Tip - Fixing mixed content errors
This part in particular
- To fix this, you will need to edit your source code and change all resources to load over a relative path, or directly over HTTPS. For example, if you load your images with a full URL,
<img src="http://example.com/image.jpg" />, you would want to change this to<img src="//example.com/image.jpg" />. By removing the http:, the browser will use whichever protocol the visitor is already using.
I see that nameserver change is still propagating, DNS Propagation Checker - Global DNS Testing Tool. (Was DNSSEC active on the domain when it was using cloudflare nameservers?)
I see one with a TLD of .cc that is still using cf but that does not matter wrt what you’re seeing on the .cw domain. WRT that domain, it’s difficult to troubleshoot once it’s moved from cloudflare and I suspect the issue you’re encountering now are not related to cloudflare.