<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
  <channel>
    <title>Blog entries tagged self-hosting :: mwop.net</title>
    <description>Blog entries tagged self-hosting :: mwop.net</description>
    <pubDate>Tue, 07 Jul 2026 10:12:23 -0500</pubDate>
    <generator>Laminas_Feed_Writer 2 (https://getlaminas.org)</generator>
    <link>https://mwop.net/blog/tag/self-hosting</link>
    <atom:link rel="self" type="application/rss+xml" href="https://mwop.net/blog/tag/self-hosting/rss.xml"/>
    <item>
      <title>Nextcloud SSRF rules and internal address ranges</title>
      <pubDate>Tue, 07 Jul 2026 10:12:23 -0500</pubDate>
      <link>https://mwop.net/blog/2026-07-07-nextcloud-ssrf-and-internal-address-ranges.html</link>
      <guid>https://mwop.net/blog/2026-07-07-nextcloud-ssrf-and-internal-address-ranges.html</guid>
      <author>contact@mwop.net (Matthew Weier O'Phinney)</author>
      <dc:creator>Matthew Weier O'Phinney</dc:creator>
      <content:encoded><![CDATA[<p>I use <a href="https://nextcloud.com">Nextcloud</a>, and have used the <a href="https://apps.nextcloud.com/apps/news">Nextcloud News</a> app as my feed reader for a number of years.</p>
<p>Since moving all my hosting to a home lab, I noticed that Nextcloud News was unable to retrieve feeds from my own website, which was weird. Looking at the logs, I saw notes about &quot;host violates local access rules&quot;.</p>


<p>This was a DNS issue (it's always DNS), right? Well, kind of.</p>
<p>In order to help prevent <a href="https://owasp.org/www-community/attacks/Server_Side_Request_Forgery">SSRF attacks</a>, Nextcloud, by default, has protections against domains that resolve to internal IP address ranges. When I moved my sites to my homelab, I also setup DNS such that when on the local network, the services resolve to the local address range instead of the public external IP. This was the root of the problem.</p>
<p>Fortunately, there's a configuration setting for that:</p>
<pre><code class="language-php hljs php" data-lang="php"><span class="hljs-comment">// in the Nextcloud config.php:</span>
[ <span class="hljs-string">'allow_local_remote_servers'</span> =&gt; <span class="hljs-keyword">true</span> ]
</code></pre>
<p>After making that change and restarting Nextcloud, I was able to get it to resolve and access my feeds.</p>


<div class="h-entry">
    <img class="u-photo photo" width="50" src="https://avatars0.githubusercontent.com/u/25943?v=3&u=79dd2ea1d4d8855944715d09ee4c86215027fa80&s=140" alt="matthew">
    <a class="u-url u-uid p-name" href="https://mwop.net/blog/2026-07-07-nextcloud-ssrf-and-internal-address-ranges.html">Nextcloud SSRF rules and internal address ranges</a> was originally
    published <time class="dt-published" datetime="2026-07-07T10:12:23-05:00">7 July 2026</time>
    on <a href="https://mwop.net">https://mwop.net</a> by
    <a rel="author" class="p-author" href="https://mwop.net">Matthew Weier O&#039;Phinney</a>.
</div>
]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
  </channel>
</rss>
