<?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 Support Tools</title><link>https://support.tools/categories/nginx/</link><description>Recent content in NGINX on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 21 Nov 2024 05:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/nginx/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up a Reverse Proxy with Nginx and Docker-Compose</title><link>https://support.tools/nginx-docker-compose-reverse-proxy/</link><pubDate>Thu, 21 Nov 2024 05:00:00 -0500</pubDate><guid>https://support.tools/nginx-docker-compose-reverse-proxy/</guid><description>&lt;p&gt;Setting up a reverse proxy with &lt;strong&gt;Nginx&lt;/strong&gt; and &lt;strong&gt;Docker-Compose&lt;/strong&gt; is an essential skill for DevOps and developers. A reverse proxy enhances application performance, security, and scalability by managing tasks like SSL termination, caching, and request routing—all while isolating your application.&lt;/p&gt;</description></item><item><title>Change Default HTTP Port for Bitnami/nginx Web Server Using ConfigMap in Kubernetes</title><link>https://support.tools/change-nginx-port-configmap-kubernetes/</link><pubDate>Sat, 12 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/change-nginx-port-configmap-kubernetes/</guid><description>&lt;p&gt;When running a &lt;strong&gt;Bitnami/nginx web server&lt;/strong&gt; in Kubernetes, you might need to change the default HTTP port (which is typically port 80) to a different port for various reasons, such as security policies, port conflicts, or custom routing requirements. In this post, we’ll show you how to modify the default port of an NGINX web server using a &lt;strong&gt;ConfigMap&lt;/strong&gt; in Kubernetes.&lt;/p&gt;</description></item><item><title>How to Run NGINX for Root &amp; Non-Root Users</title><link>https://support.tools/nginx-root-non-root/</link><pubDate>Thu, 10 Oct 2024 19:26:00 -0500</pubDate><guid>https://support.tools/nginx-root-non-root/</guid><description>&lt;p&gt;Running &lt;strong&gt;NGINX&lt;/strong&gt; as both a root and non-root user can be crucial depending on your deployment requirements. While root privileges allow full control over system resources, running NGINX as a non-root user enhances security by limiting the scope of potential vulnerabilities.&lt;/p&gt;&#10;&lt;p&gt;In this post, we will walk through the steps to run NGINX in both &lt;strong&gt;root&lt;/strong&gt; and &lt;strong&gt;non-root&lt;/strong&gt; configurations, allowing you to balance flexibility and security in your web server environment.&lt;/p&gt;</description></item><item><title>How to enable legacy TLS versions in Rancher's ingress-nginx</title><link>https://support.tools/post/how-to-check-default-coredns-configmap-of-rke-k8s-version/</link><pubDate>Fri, 23 Oct 2020 14:28:00 +0000</pubDate><guid>https://support.tools/post/how-to-check-default-coredns-configmap-of-rke-k8s-version/</guid><description>&lt;p&gt;This article details how to enable TLS 1.1 on the ingress-nginx controller in Rancher Kubernetes Engine (RKE) CLI or Rancher v2.x provisioned Kubernetes clusters.&lt;/p&gt;</description></item><item><title>How to enable legacy TLS versions in Rancher's ingress-nginx</title><link>https://support.tools/post/how-to-enable-legacy-tls-versions/</link><pubDate>Fri, 23 Oct 2020 14:28:00 +0000</pubDate><guid>https://support.tools/post/how-to-enable-legacy-tls-versions/</guid><description>&lt;p&gt;This article details how to enable TLS 1.1 on the ingress-nginx controller in Rancher Kubernetes Engine (RKE) CLI or Rancher v2.x provisioned Kubernetes clusters.&lt;/p&gt;</description></item><item><title>Rancher SSL Passthrough for NGINX ingress</title><link>https://support.tools/post/rancher-nginx-ssl-passthrough/</link><pubDate>Wed, 20 Nov 2019 00:03:00 +0000</pubDate><guid>https://support.tools/post/rancher-nginx-ssl-passthrough/</guid><description>&lt;p&gt;Recently while setting up Vault inside Rancher. I ran into an issue with the NGINX ingress terminating TLS and forwarding traffic unencrypted to Vault.&lt;/p&gt;</description></item></channel></rss>