Cloudflare are nice enough to provide a free tier to their CDN service which is perfect for those of us that still host websites at home. The free teir provides some basic benefits – DDOS protection and caching. Check out the details here – https://www.cloudflare.com/plans/#overview
If you utilize their tunneling solution, you’ll also be able to host websites behind a dynamic IP. You’ll no longer need a static IP. This means the traffic goes like so;
Your website <-> ACME <-> Cloudflare tunnel <-> Cloudflare <-> User
Double cool! Check out these resources to do it for yourself –
Crypto mining failed me (see coin hive here), ads are annoying and more and more likely to be blocked via various plugins and tools. The Brave browser blocks all ads by default and builds up a profile on where you are spending your time on the web. Contributions are then made to the various sites if they are registered to the “BAT” system, which is a way of rewarding the content providers.
My very brief experience so far has been positive, a fast browser which support all my chrome plugins – but with all ad-blocking etc built in. For the extra paranoid it also includes a private mode that utilizes ToR network. Oh and it has a web torrent client built in.
So the trial of coinhive and associated monero browser mining has come to an end. It seems most corporate firewalls and security appliances detect and block access to my domain just being associated with the coinhive java-script.
Even though i was being a polite net citizen and disclosing it on the site – firewalls with strict polices dont give it a chance. Several public DNS servers have also block listed the site – hopefully this will be undone soon.
There is a lot of fear around the word “crypto” due to the more malicious crypto-locker virus and it seems that coinhive has been associated to similar hysteria and panic.
Note : the amount of “wasted CPU” is trivial as i would only expect people visiting my site to be donating some cycles. i.e. in most cases i wouldn’t expect and entire company / business behind a firewall to browse my website and be under threat of mass “CPU stealing”
While setting up SSL reverse proxy using lets encrypt and nginx i had a few troubles with testing via googles Chrome browser.
Chrome caches some SSL responses which can be cleared by deleting your browsing data via settings or Ctrl+Shift+Del.
Chrome also caches http -> https redirects, you can see these by going to chrome://net-internals and select “HSTS” from the drop down. Enter the domain name under “Delete domain” and press the Delete button
The easiest thing to do during testing is use incognito mode. You will not need to clear the cache every time you change config or re-issue certificates.