<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>tunnel on Digital Archive Systems Tech Blog</title><link>https://tech.ldas.jp/en/tags/tunnel/</link><description>Recent content in tunnel on Digital Archive Systems Tech Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 07 Apr 2026 10:00:00 +0900</lastBuildDate><atom:link href="https://tech.ldas.jp/en/tags/tunnel/index.xml" rel="self" type="application/rss+xml"/><item><title>Securely Exposing Academic Servers with Cloudflare Tunnel</title><link>https://tech.ldas.jp/en/posts/cloudflare-tunnel/</link><pubDate>Tue, 07 Apr 2026 10:00:00 +0900</pubDate><guid>https://tech.ldas.jp/en/posts/cloudflare-tunnel/</guid><description>&lt;h1 id="securely-exposing-academic-servers-with-cloudflare-tunnel">Securely Exposing Academic Servers with Cloudflare Tunnel&lt;/h1>
&lt;h2 id="background">Background&lt;/h2>
&lt;p>When running Elasticsearch (full-text search) or Cantaloupe (IIIF image delivery) on an academic research server, you typically need to open ports to the outside world. However, opening ports introduces the risk of attacks exploiting vulnerabilities.&lt;/p>
&lt;p>With Cloudflare Tunnel, you can &lt;strong>securely expose services to the public without opening any inbound ports&lt;/strong> on your server.&lt;/p>
&lt;h2 id="what-is-cloudflare-tunnel">What Is Cloudflare Tunnel?&lt;/h2>
&lt;p>In a conventional server setup, the server opens ports and listens for incoming connections (inbound connections). Cloudflare Tunnel reverses this model.&lt;/p></description></item></channel></rss>