RSS Troubleshooting Notes

title: RSS Troubleshooting Notes
date: 2023-03-08 15:59:18
tags:

Records
Troubleshooting
excerpt: Documenting the process of setting up ttrss and related RSS content
categories:
Learning

RSS Troubleshooting Notes#

On March 7th, with no classes in the afternoon, I had a lot of free time. After getting bored of playing Vampire Survivor, I decided to try setting up a server that I had previously failed to do.

First, I tried using AZURE, but the student verification didn't pass, so I gave up. Then I tried Alibaba Cloud. They have a program called "FeiTian Acceleration 3.0 - University Plan" where you can get seven months of ECS. It went quite smoothly.

After receiving it, the first thing I wanted to do was set up my own RSS service. I basically followed the instructions in 找不到满意的 RSS 服务？你可以自己搭建一个 to complete it. However, there were still some twists and turns along the way, and I encountered some challenges.

The first issue was with the network. The addresses provided in the article were all on GitHub, but the download speed was really slow. It took over half an hour to download a 16MB file. There are two ways to solve this. The first thing I tried was using a mirror site, but the mirror site I tried had some issues. Additionally, I wanted to set up a Telegram bot on the server later on. So, I decided to use a proxy. I referred to 如何让国内的阿里云服务器可以高速下载 Github 代码 and the tutorial from the VPN service I used. However, I'm still not clear on how to change the nodes. I have learned it now and documented it in 网络.
The second issue was with the docker-compose configuration file for ttrss provided in the article. Even after modifying it myself, the downloaded files were still incorrect. Then I thought of simply copying it over. However, I'm not familiar with vim operations, and the yml format has strict requirements for indentation. So, I spent quite a while struggling with it.
(I realized that I was being foolish. GitHub provides a corresponding download method: click "raw", and it will redirect to the desired URL. For example, the code I needed for this step was curl -fLo a.yml https://raw.githubusercontent.com/HenryQW/Awesome-TTRSS/main/docker-compose.yml)
After starting the containers, according to the description, I should be able to directly see the Tiny Tiny RSS web frontend by accessing {server IP}:181. However, I encountered a 502 error. Later, I realized that the default 181 port is not open, so I added it in the security group settings, and it worked.
Choosing a reader also took me a lot of time. First, I tried using "Fluent Reader" which I had been using for some time, but the address provided in the documentation didn't work. Then I tried "TTRSS-Reader", which went smoothly, but the interface was a bit outdated and it lacked some features, or maybe I just hadn't discovered them yet. So, I switched to "FeedMe". Initially, I used the TTRSS API, but I encountered an issue where the subscription address could be imported, but the content couldn't be fetched. I found out that this was a bug that appeared several months ago and hasn't been fixed yet. The solution was to switch to the Fever API. But this was also a challenge. First, the address provided on the website was http:/[your address]/plugins.local/fever/, while the documentation provided https://[your address]/plugins/fever. However, it's possible that different readers have different filtering methods. The address that "FeedMe" could use was http://[your address]/, while "Fluent Reader" used http://[your address]//plugins/fever/.

These were the issues I encountered during the entire setup process. Currently, I have found that "FeedMe" has significantly more features, and I also want to start using RSSHub and expand the subscription sources beyond personal blogs.