Tiny Tiny RSS: Community

Public.php links not public?


Hello, all;
very likely not “a bug” but some stupid n00b oversight on my part:

[Describe the problem you’re having:]
I’m running my tt-rss instance with the goal to remix feeds for re-use on other platform/s (website embed/s) + offer to other users. Hence, I would much like to use links as issued by tt-rss via the public.php interface. However, I must still be doing something wrong, because my public.php-links are not public(ly usable) yet (going by the assumption that “public” implies ‘available without having to be logged in’; maybe that’s the error in my thinking already. Be that as it may, I have not been able to confirm or refute either way, having searched here and in the FAQ related to “public.php”, 403 etc.; also checked the config-php if there maybe some setting was jumping out at me that needed adjustment. [If I missed something utterly obvious, kindly bear with me; I’m not being stupid on purpose :wink: here.]

[If possible include steps to reproduce the problem:]

[tt-rss version (including git commit id):]
var __ttrss_version = “18.8” (I’m sorry, I don’t know how to locate the git commit id; I installed yesterday and am still in testing)

[Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:]
|cPanel Version|76.0 (build 8)|
|Apache Version|2.4.37|
|PHP Version|5.6.38|
|MySQL Version|5.6.41|
|Operating System|linux|

I truly hope this is not too dumb a question + I’m sorry I could not figure it out by myself;
your help is greatly appreciated.

Best - LX

Purge after {n} days apparently not working for me

your sample link opens fine for me both in browser and using CURL.

maybe your hosting provider prevents access by those services for whatever reason, try using tt-rss myfeedsucks (https://fakecake.org/myfeedsucks/)

regardless of the actual cause it’s definitely not tt-rss.


Thank you, fox;
I’m already happy it wasn’t me being dense. :slight_smile:

Then let me see what I can get out of my hoster on that topic.


hello all;
so I’ve talked some rounds with support at OrangeWebSite (our hoster) about this + so far we have not been able to nail what’s causing this.
It makes no difference if we run it http or https (we thought maybe a rewrite rule in the .htaccess might be causing the difficulties, but with some rounds of testing e established it makes no difference); we even gave disabling mod_sec a shot, just to be sure.

Perhaps someone has an idea how we can drill down to what hampers access here?
Thank you some more. Cheers - LX

P.S. I realize this might be the wrong place to ask, since simply throwing the feedlink into FireFoxes address bar serves back proper output. So I’d be in agreement that tt-rss itself is highly unlikely to be at the root of this. Maybe the w3c validator is just shot :confused:


The validator may be busted. If the feed exists, the server is fine, and the problem is reproducible, let us know on the feedvalidator-users mailing list.