Nginx on sigtar.com

moving wordpress to http2 (via https)

Mon, 15 Oct 2018 00:00:00 +1300

I just moved my wordpress site to http2 (via https). Some advice on steps to moving your site ;

Run it behind nginx + lets encrypt - offload ssl certs and get http2 performance
Setup nginx default to redirect all http -> https
update your WordPress site to correct URL (via admin / settings / general) i.e.
Run WP plug-in to change all media / links to new https links. Else you get mixed secuirty (some http, some https)
- I used - https://wordpress.org/plugins/velvet-blues-update-urls/

SSL caching and redirects in chrome

Mon, 15 Oct 2018 00:00:00 +1300

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.

bye bye http - hello letsencrypt

Thu, 11 Oct 2018 00:00:00 +1300

I’ve been a fan of HTTP and caching since my dial-up modem.

Skip to today where google returns HTTPS sites higher in its search results. Its could also be possible that you cannot trust a man in the middle HTTP cache any longer either right? :)

SSL certs have traditionally been expensive, but say welcome to lets encrypt which provides a free way of securing all of your websites. If you haven’t heard of it check it out here - https://letsencrypt.org/

nginx - setup as reverse proxy

Sat, 08 Feb 2014 00:00:00 +1300

Previously to take down this wordpress site all you needed to do was hold down F5 for about 20 seconds then the site would take about 5 mins to recover.

There were a few factors causing this and quite a few different methods to solving the problem. Wordpress itself is run on php / apache, apache has an evasive mod which can block certain IPs depending on the defined abusive behavior (typical DDOS attack). Since i like to run a few websites behind a single IP i looked at fixing the issue closer to the perimeter….