Describe the problem you’re having:
Feed fetch returning error “unable to fetch: 0 ”
If possible include steps to reproduce the problem:
I’m cannot reproduce externally, have tested with fakecake
tt-rss version (including git commit id):
Tiny Tiny RSS v17.12 (fdde115)
Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
Ubuntu 14.04.5 LTS, PHP 7.0.27, PostgreSQL 9.6.6, curl 7.35.0
Please provide any additional information below:
After a recent upgrade to the latest TTRSS version and as well a switch from PHP5 to PHP7 I’m experiencing this error on about 10 out of 2000 or so feeds. I’m fairly sure they all worked before the update and the error is not telling me too much. My open_basedir is set to “nothing” and I found this on the old forum ht tps://tt-rss.org/oldforum/viewtopic.php?f=1&t=3775&p=22406&hilit=unable+to+fetch%3A+0#p22406 that is similar but I believe all feeds failed in that acse and not just a small percent as I’m seeing.
[13:53:36/30384] start [13:53:36/30384] local cache will not be used for this feed [13:53:36/30384] last unconditional update request: 2018-01-29 12:31:59 [13:53:36/30384] stored last modified for conditional request: Mon, 29 Jan 2018 12:07:44 GMT [13:53:36/30384] fetching [ht tps://www.geek4you.it/feed/] (force_refetch: )... [13:53:37/30384] fetch done. [13:53:37/30384] source last modified: Mon, 29 Jan 2018 12:07:44 GMT [13:53:37/30384] unable to fetch: 0 
I tested this feed on feedcake and works fine, so my first thought was that it was linked to my servers PHP version, though reverting back to the previous PHP5 version gives me the same error. Note that access the feed a browser and tiny proxy running the same box.
A CURL test for reference:
curl -IL ht tps://www.geek4you.it/feed/ HTTP/1.1 200 OK Date: Mon, 29 Jan 2018 14:29:33 GMT Content-Type: application/rss+xml; charset=UTF-8 Connection: keep-alive Set-Cookie: __cfduid=dbbab9ce100fae4c42fe80c5020de26fd1517236173; expires=Tue, 29-Jan-19 14:29:33 GMT; path=/; domain=.geek4you.it; HttpOnly Accept-Ranges: bytes Alt-Svc: quic=":443"; ma=2592000; v="35,37,38,39" Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Cf-Railgun: direct (starting new WAN connection) Etag: "1cc66b65e50ff9e3c3f58a52e93e80d8" Expires: Thu, 19 Nov 1981 08:52:00 GMT Last-Modified: Mon, 29 Jan 2018 12:07:44 GMT Link: <ht tps://www.geek4you.it/wp-json/>; rel="ht tps://api.w.org/" Pragma: no-cache Set-Cookie: PHPSESSID=mk2r1fhg015cc9gnku4mpcieb3; path=/ Set-Cookie: vchideactivationmsg=1; expires=Fri, 29-Jan-2021 14:29:32 GMT; Max-Age=94694400; path=/ Set-Cookie: vchideactivationmsg_vc11=5.4.5; expires=Fri, 29-Jan-2021 14:29:32 GMT; Max-Age=94694400; path=/ Strict-Transport-Security: max-age=0; preload X-Litespeed-Cache-Control: no-cache X-Robots-Tag: noindex, follow X-Turbo-Charged-By: LiteSpeed X-Content-Type-Options: nosniff Expect-CT: max-age=604800, report-uri="ht tps://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" Server: cloudflare CF-RAY: 3e4ce26158179c65-AMS
Ignore the space between “ht tp” as a hotfix for not beeing allow allowed to post more than two “links”
Any thoughts on my best next steps, not sure if TINY related or not at this point?