<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nginx on jfx's site</title><link>https://jfx.ac/tags/nginx/</link><description>Recent content in Nginx on jfx's site</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 03 Aug 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://jfx.ac/tags/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>How to secure your nginx &amp; Cloudflare configuration to stop any origin leaks</title><link>https://jfx.ac/blog/securing-nginx-origin-with-cloudflare/</link><pubDate>Mon, 03 Aug 2020 00:00:00 +0000</pubDate><guid>https://jfx.ac/blog/securing-nginx-origin-with-cloudflare/</guid><description>&lt;p&gt;I decided to write this as although a lot of guides on the internet provide a
solid configuration for an nginx server, most of these guides will result in an
IP leak somewhere under their configuration for the origin server somewhere.&lt;/p&gt;
&lt;p&gt;So you got your nginx server setup (hopefully) and it&amp;rsquo;s serving your files (or
being an effective reverse proxy), but maybe you&amp;rsquo;ve noticed loading static
content (images, media, etc) load slowly&amp;hellip; or maybe you realised that anyone
can get the IP address of your website and therefore the box which is hosting
it, and that creeps you out a bit. Or maybe your website doesn&amp;rsquo;t have that
padlock everyone else&amp;rsquo;s has and it&amp;rsquo;s &amp;ldquo;not secure&amp;rdquo;. Luckily all these issues can
be solved by Cloudflare! Or maybe your website is going through Cloudflare but
sometimes you notice your origin server is still publicly displaying the
website, and you want to stop this leak.&lt;/p&gt;</description></item></channel></rss>