So, it took me a bit to get this working -- turns out I was using http://
<servername>/tt-rss/fever/ instead of http://
/fever/ -- but I finally got it working. This is great, thanks so much!
However, part of my problem was that I was also trying to get this Fever plugin to work over https:// instead of http://
, which simply did not work. I could not even see records of the attempt to connect in either /var/log/syslog, or the various /var/log/apache2/* files, or in the "ttrss_error_log" table (which has no rows in it).
So, my question is this:Has anyone had any luck getting this Fever plugin to work over https:// (SSL)? I've been using tt-rss with https:// and prefer not to be sending usernames / passwords unencrypted over the wire.
I'm an experienced developer and would be happy to help get https:// working with this plugin. But I do not know where to start, as I have no information as to why it's not
working. When I specify https://
, Reeder does seem to try to connect and login because there's a couple of seconds delay between pressing "Done" and getting Reeder's error message ("Login Failed: Please try again.", which itself is not very diagnostic). This, and the fact that I see no record of activity whatsoever on the server side when trying to setup the Reeder Fever account using https://
, leaves me unsure where to turn. Obviously, using the tt-rss web interface over https:// is working just fine for me. So, any suggestions and pointers are most welcome!
You can also email me directly at dm at-sign dougmorse period org.