Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Adding more than 213 feeds causes nginx issue - "502 Bad Gateway"

Closed
#75 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker, nginx

Research direction

Reproduce the failure with the LinuxServer FreshRSS Docker image by adding more than 213 feeds and opening the subscription management page. Start by checking the nginx proxy behavior and the container logs; done means the page remains accessible with at least 214 feeds, ideally at the reported thousands-of-feeds scale.

Written by the indexing model from the issue text.

Description

no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

If I add more than 213 feeds it breaks the Subscription Management page (?c=subscription). Trying to visit the subscription management pages results in "502 Bad Gateway". If I delete the 214th feed, the Subscription Management page starts working again.

Google AI suggests that it's an issue with nginx proxying and suggesting making changes to the size of several proxy buffer settings.

I opened an issue with FreshRSS and one of their maintainers said that their official Docker does not use nginx and they suspect that the issue is related to nginx proxying.

Expected Behavior

FreshRSS should be able to handle thousands of feeds without issue

Steps To Reproduce
  1. I am using this Docker from the official image in the Unraid package manager / store
  2. I have been using it without issue for several months. When I added the 214th feed the Subscription Management page stopped working and reports "502 Bad Gateway". If I delete the 214th feed the page starts working again.

I have tried many combinations of adding/removing feeds to different categories and the 214th feed triggers the issue no matter where or how I add it.

Environment
- OS: Unraid 7.2.4
- The Docker image was installed from the Unraid official package manager/store
CPU architecture

x86-64

Docker creation
docker run
  -d
  --name='freshrss'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Voyager"
  -e HOST_CONTAINERNAME="freshrss"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:80]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/freshrss-logo.png'
  -p '8180:80/tcp'
  -v '/mnt/disks/ssd1/appdata/freshrss':'/config':'rw,slave' 'lscr.io/linuxserver/freshrss'
c03578b1280f687ad490693e2cebe437d067d479a39eb5d83d314a3ed026804c
Container logs
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    99
User GID:    100
───────────────────────────────────────
Linuxserver.io version: 1.28.1-ls302
Build-date: 2026-04-19T13:50:37+00:00
───────────────────────────────────────
    
using keys found in /config/keys
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Dominant language
Dockerfile
Stars
233
Forks
27
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.