Folo Instance has been deployed by myself and I set the key, but `502 Bad Gateway`

Instance has been deployed by myself and I set the key, but `502 Bad Gateway`

Open tsinglinrain opened this issue 7 months ago • 1 comments

Platform

Desktop - Windows, Desktop - Web

Describe the bug

This is deployed by myself in the form of docker compsoe on the VM. After a while, I authenticated two subscription links (Lianhe Zaobao and Bing Wallpaper).

But then I checked Debug Info and found that many subscription routes did not belong to me, and the traffic consumption was large. So I added a key.

After a while, perhaps after a version update, my subscription links in Follow (now folo) all became invalid. That is, it showed 502 Bad Gateway, as shown in the figure.

I tried to restart the docker image, unsubscribe from Follow and then subscribe, but it didn't help.

I also tried to add my new Instance on Follow, , as shown in the figure, but it was still 502.

I can guarantee that the content can be viewed normally when the link is opened directly on the web page, and it can be viewed normally on other RSS readers such as inoreader.

Relevant Information

user id: 56198714880339968 feed id: 91729817851470848 feed url: https://rss.soyet.icu/zaobao/realtime/world?code=35c8746093a996ba586d680077bbd509

Only take Lianhe Zaobao as an example, but I can provide the key if needed.

Reproduction Video

None

Environment

App Version: 0.3.13 OS: Windows User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Folo/0.3.13 Chrome/132.0.6834.196 Electron/34.2.0 Safari/537.36 Env: electron Browser: Chrome Session Trace Id: C6o5teZji8gB5ZiHYK5kw

Validations

[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[x] This issue is valid