Proxmox VE TLS Certificate Replacement: Installing a Trusted Certificate for the Web UI

Proxmox VE ships with a self-signed certificate. The browser warning it produces is not just an annoyance — users clicking through “Your connection is not private” warnings train themselves to ignore certificate errors, which is dangerous. More practically: in environments with multiple admins, the self-signed certificate means you cannot distinguish a legitimate Proxmox node from […]

Proxmox VE TLS Certificate Replacement: Installing a Trusted Certificate for the Web UI Read Post »

QNAP NAS SSL Certificate: Replacing the Self-Signed Certificate with Let’s Encrypt or a Custom Certificate

QNAP NAS devices run QTS (or QuTS hero), which manages the web administration interface, file services, and applications like Qsync, myQNAPcloud, and others. Like Synology, QNAP ships with a self-signed certificate. This article covers replacing it with a Let’s Encrypt certificate through the built-in ACME client, uploading a custom certificate from an internal CA, and

QNAP NAS SSL Certificate: Replacing the Self-Signed Certificate with Let’s Encrypt or a Custom Certificate Read Post »

RabbitMQ TLS Configuration: Enabling HTTPS on the Management UI and Encrypting AMQP Traffic

RabbitMQ runs two network interfaces that benefit from TLS: the AMQP port (5672) that carries messages between producers, consumers, and the broker, and the management plugin’s HTTP API and web UI (port 15672). This article covers enabling TLS on both, configuring clients, setting up mutual TLS for producer/consumer authentication, and renewing certificates without message loss.

RabbitMQ TLS Configuration: Enabling HTTPS on the Management UI and Encrypting AMQP Traffic Read Post »

Redis TLS Configuration: Encrypting Client Connections on Redis 6 and Later

Redis added native TLS support in version 6.0, released in April 2020. Before that, TLS for Redis required a TLS proxy (stunnel, spiped, or nginx stream proxy). If you are still running Redis without TLS because “it is on a private network”, consider that Redis commands carry your application data — including session tokens, cache

Redis TLS Configuration: Encrypting Client Connections on Redis 6 and Later Read Post »

Redmine HTTPS Configuration: Running the Project Management Tool Behind a TLS Proxy

Redmine is a Ruby on Rails project management application. It does not include a production-ready web server — it is designed to run behind Puma or Passenger as a backend, with nginx or Apache as the TLS-terminating reverse proxy. This article covers configuring nginx with TLS for Redmine, setting the correct base URL so email

Redmine HTTPS Configuration: Running the Project Management Tool Behind a TLS Proxy Read Post »

Remote Desktop Gateway TLS Certificate: Replacing the Certificate Without Breaking RDP Access

Remote Desktop Gateway (RD Gateway) uses TLS for two purposes: the HTTPS tunnel that wraps RDP traffic, and the authentication handshake for RD Gateway policies. When the certificate expires, remote employees and administrators who connect through RD Gateway lose access immediately. This article covers replacing the RD Gateway certificate using the RD Gateway Manager, PowerShell,

Remote Desktop Gateway TLS Certificate: Replacing the Certificate Without Breaking RDP Access Read Post »

Rocket.Chat HTTPS Configuration: Running the Team Chat Platform Behind a TLS Reverse Proxy

Rocket.Chat is a self-hosted Slack alternative that handles real-time messages, file uploads, and video calls. Without TLS, all of that is visible on the network. Rocket.Chat is a Node.js application that does not handle TLS natively in most deployment configurations — TLS is the responsibility of a reverse proxy in front of it. This article

Rocket.Chat HTTPS Configuration: Running the Team Chat Platform Behind a TLS Reverse Proxy Read Post »

Securing Prometheus with TLS: HTTPS Configuration for the Metrics Scrape Endpoint

Prometheus is almost always deployed without TLS because the documentation used to treat it as an internal-only tool. By the time someone asks “is this metrics data sensitive?”, the server has been running for a year on port 9090 without encryption. This article covers enabling HTTPS on Prometheus itself — the scrape endpoint and the

Securing Prometheus with TLS: HTTPS Configuration for the Metrics Scrape Endpoint Read Post »

SonarQube HTTPS Configuration: Putting the Code Quality Platform Behind a TLS Proxy

SonarQube runs an Elasticsearch node internally and serves its web interface on port 9000. It does not handle TLS natively — it is designed to be deployed behind a reverse proxy. This article covers setting up nginx as a TLS reverse proxy in front of SonarQube, configuring the sonar.web.publicRootUrl property so that generated links are

SonarQube HTTPS Configuration: Putting the Code Quality Platform Behind a TLS Proxy Read Post »

SQL Server TLS Certificate Configuration: Encrypting Connections and Replacing Expired Certificates

SQL Server encrypts every connection when a certificate is configured — but if no certificate is installed, SQL Server generates a self-signed one at startup that is only trusted by the local machine. Remote clients get the “self-signed certificate” warning (or more dangerously, they silently accept it). This article covers installing a proper TLS certificate,

SQL Server TLS Certificate Configuration: Encrypting Connections and Replacing Expired Certificates Read Post »

Scroll to Top