Adding feed from lan address

Tiny Tiny RSS Support
1

I’m running ttrss on my raspberry pi.

I’ve created a few web scrapers and using Django I’m serving the stored items as an atom feed from the same pi. The resulting feed has passed validation on validator.w3.org and I can add it on my laptop using feedreader and Akregator with the lan address 192.168.1.xxx:xxxx/rss, however when I try to add it to ttrss using the same address I get hit with ‘Couldn’t download the specified URL: HTTP Code: 404’

I’m just wondering what, if anything, I’m doing wrong.

A sample of the generated xml:

<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Scraped</title>
    <link>http://192.168.1.xxx:xxxx/</link>
    <description>Updates on scraped items.</description>
    <atom:link href="http://192.168.1.xxx:xxxx/rss" rel="self"/>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Feb 2022 05:00:00 +0000</lastBuildDate>
    <item>
      <title>Title goes here.</title>
      <link>http://192.168.1.xxx:xxxx/220</link>
      <description>Description goes here.</description>
      <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Author name goes here.</dc:creator>
      <guid>http://192.168.1.xxx:xxxx/220</guid>
    </item>
    <item>
      <title>Title goes here.</title>
      <link>http://192.168.1.xxx:xxxx/219</link>
      <description>Description goes here.</description>
      <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Author name goes here.</dc:creator>
      <guid>http://192.168.1.xxx:xxxx/219</guid>
    </item>
    <item>
      <title>Title goes here.</title>
      <link>http://192.168.1.xxx:xxxx/218</link>
      <description>Description goes here.</description>
      <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Author name goes here.</dc:creator>
      <guid>http://192.168.1.xxx:xxxx/218</guid>
    </item>
  </channel>
</rss>
2

https://community.tt-rss.org/t/heads-up-several-vulnerabilities-fixed/3799/40

I believe if you use dns instead of an IP it works, but I do not recall.

3

“Non-standard” port perhaps?

https://community.tt-rss.org/t/problem-subscribing-to-feed-on-custom-port/4203
.

4

Thanks, everyone for the answers. I believe it was likely the non-standard port issue.
For anyone looking to accomplish the same thing (including future-me if something goes to hell).

  1. Created an entry in my pihole’s local dns records pointing a domain name to pi’s ip.
  2. Updated the nginx entry to use that domain name as the server name.
  3. Also had to change /etc/dhcpcd.conf to have the pi use its pihole as primary dns, otherwise got hit with “unable to resolve” error.
  4. Forgot, I also had to add the domain name to the allowed hosts in django’s settings.