<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cloudflare on 🛠️ blog.yrhsk.work</title>
    <link>https://blog.yrhsk.work/tags/cloudflare/</link>
    <description>Recent content in Cloudflare on 🛠️ blog.yrhsk.work</description>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 10 Aug 2025 17:50:59 +0300</lastBuildDate>
    <atom:link href="https://blog.yrhsk.work/tags/cloudflare/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automating a no-cost zero-trust RDP solution for Windows Server - Cloudflare in-browser RDP</title>
      <link>https://blog.yrhsk.work/posts/cloudflare-access-rdp-demo/</link>
      <pubDate>Sun, 10 Aug 2025 17:50:59 +0300</pubDate>
      <guid>https://blog.yrhsk.work/posts/cloudflare-access-rdp-demo/</guid>
      <description>&lt;h3 id=&#34;a-small-intro&#34;&gt;A small intro&lt;/h3&gt;
&lt;p&gt;Although my main stack is far from this now, throughout my professional career I have had to work with the Windows Server stack, and the issue of secure RDP access has always been important. One of my favorite customers with Windows Server stack was a medium-size company in the financial sector, who&amp;rsquo;ve managed their custom software across multiple Windows Server environments, and their go-to solution for secure RDP access was Azure VPN. With all my love for Azure, their VPN (especially cert-based one, which required a lot of management overhead) was not the most user-friendly solution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cloudflare R2 registry as an extremely cheap solution for DockerHub rate limits</title>
      <link>https://blog.yrhsk.work/posts/cf-registry-pull-through/</link>
      <pubDate>Mon, 30 Dec 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.yrhsk.work/posts/cf-registry-pull-through/</guid>
      <description>&lt;h1 id=&#34;dockerhub-rate-limits&#34;&gt;DockerHub rate limits&lt;/h1&gt;
&lt;p&gt;DockerHub has a &lt;a href=&#34;https://docs.docker.com/docker-hub/download-rate-limit/&#34;&gt;strict rate limit policy&lt;/a&gt;, especially for anonymous pulls.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;for anynomyous users: 100 pulls per 6 hours per IP address.&lt;/li&gt;
&lt;li&gt;for authenticated users: 200 pulls per 6 hours per IP address.&lt;/li&gt;
&lt;li&gt;=&amp;gt; if your usage exceeds these limits, your requests are denied until the six-hour window elapses.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Despite the fact that for authenticated users the rate limit is higher, these limits can easily break the CI/CD pipelines which use DockerHub as a source of base images, especially if runners aren&amp;rsquo;t ephemeral and use the same IP address for multiple builds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
