<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Network-Diagnostics on DRM HSE</title><link>https://www.drmhse.com/tags/network-diagnostics/</link><description>Recent content in Network-Diagnostics on DRM HSE</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 09:15:16 +0300</lastBuildDate><atom:link href="https://www.drmhse.com/tags/network-diagnostics/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing a VPS Reverse SSH Tunnel Without Losing Rollback</title><link>https://www.drmhse.com/posts/replacing-vps-reverse-ssh-cloudflare-tunnel/</link><pubDate>Fri, 10 Jul 2026 17:00:00 +0300</pubDate><guid>https://www.drmhse.com/posts/replacing-vps-reverse-ssh-cloudflare-tunnel/</guid><description>&lt;p>My self-hosted applications ran on a desktop at home. Cloudflare sent public traffic to a VPS, and the VPS forwarded it through a reverse SSH tunnel to Nginx on the home server. The design avoided inbound port forwarding and gave me a familiar SSH-based recovery path.&lt;/p>
&lt;p>Then Mattermost messages began arriving late. API calls paused before returning, and WebSockets felt sticky. Nothing was fully down, so every component looked innocent on its own.&lt;/p></description></item></channel></rss>