Tiny Tiny RSS: Community

Feed not displaying on web version, but displaying on Android


#1

PLEASE READ THIS BEFORE POSTING: Read before posting / reporting bugs

Describe the problem you’re having:

  1. Feed https://opinionua.com/feed/ is not showing with error Could not update headlines (invalid object received - see error console for details)

In console log I can see that backend.php returned empty response

If possible include steps to reproduce the problem:

Subscribe to https://opinionua.com/feed/

tt-rss version (including git commit id):

git rev-parse HEAD
79c50359203afef9c04824376368040139fc3402

commit 79c50359203afef9c04824376368040139fc3402
Author: Andrew Dolgov [email protected]
Date: Mon Nov 26 12:44:36 2018 +0300

reset password: use updated mailer parameters properly

Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:

Linux 4.14.70 PostgreSQL 9.6 PHP 7.2.8 nginx 1.15.5

Please provide any additional information below:

Android client loads feed without any issues


#2

Feed works fine here…


#3

Worked fine for me as well till today.

Now empty response - but status is 200

No errors in logs, and I have no idea how to debug


#4

What have you changed since the issue started?

I don’t think the latest updates would affect this, but if you roll back a few commits (to before the mailer changed–just temporarily because of the security issues) does it work?


#5

op, i’m not seeing any error logs (preferences -> system)


#6

Empty


#7

Error in browser console


#8

I have installation updated after I have seen this issue


#9

Could you maybe rephrase that, I don’t understand.


#10
  1. I have noticed the issue today, before updating tt-rss installation with latest git updates
  2. Then I have updated tt-rss installation
  3. Issue still occurs

#11

The JSON response is basically empty so I’m guessing it’s failing before it can do much. Can you change the log destination in config.php to an empty string and try again. Then see if anything shows up in the log files on the actual server?


#12

zero length JSON response without any logged errors in tt-rss (and i assume neither in nginx/apache error.log) could indicate some kind of MITM being triggered by data, i.e. an antivirus on your PC or a filtering proxy.


#13

I dont think so

curl request on the box

curl -v “http://127.0.0.1/tt-rss/backend.php” -H “User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0” -H “Accept: text/javascript, text/html, application/xml, text/xml, /” --compressed -H “X-Requested-With: XMLHttpRequest” -H “Content-type: application/x-www-form-urlencoded; charset=UTF-8” -H “Connection: keep-alive” -H “Cookie: GUID_8888=exLLEd4yfChDOy*******; ttrss_sid=pko7ip9e*******7q4usu” --data “op=feeds&method=view&feed=132&view_mode=adaptive&order_by=default&cat=false&csrf_token=6ty9q********df”

  • Trying 127.0.0.1…
  • TCP_NODELAY set
  • Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)

POST /tt-rss/backend.php HTTP/1.1
Host: 127.0.0.1
Accept-Encoding: deflate, gzip
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0
Accept: text/javascript, text/html, application/xml, text/xml, /
X-Requested-With: XMLHttpRequest
Content-type: application/x-www-form-urlencoded; charset=UTF-8
Connection: keep-alive
Cookie: GUID_8888=exLLEd4yfChDOyHu7Txw; ttrss_sid=pko7ip9e3hsto4avgkbt7q4usu
Content-Length: 106

  • upload completely sent off: 106 out of 106 bytes
    < HTTP/1.1 200 OK
    < Server: nginx
    < Date: Thu, 29 Nov 2018 10:38:09 GMT
    < Content-Type: text/json; charset=utf-8
    < Transfer-Encoding: chunked
    < Connection: keep-alive
    < Expires: Thu, 19 Nov 1981 08:52:00 GMT
    < Cache-Control: no-store, no-cache, must-revalidate
    < Pragma: no-cache
    < Content-Language: auto
    < Content-Encoding: gzip
    < Vary: Accept-Encoding
    <
  • Curl_http_done: called premature == 0
  • Connection #0 to host 127.0.0.1 left intact