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

wallabag lost port when redirecting requests from reverse proxy

Open
#449 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, nginx

Research direction

Start by reproducing the redirect with the supplied Docker environment, SYMFONY__ENV__DOMAIN_NAME value, and reverse-proxy headers. Trace how the application constructs the login redirect and verify that visiting https://wallabag.a.com:6666 redirects to a URL that preserves port 6666.

Written by the indexing model from the issue text.

Description

I am working on deploying a wallabag behind reverse proxy.

wallabag container adderss: http://127.0.0.1:5555,

reverse proxy domain: https://wallabag.a.com:6666,

Wallabag configure:
- SYMFONY__ENV__DOMAIN_NAME=https://wallabag.a.com:6666

When visiting “https://wallabag.a.com:6666”,the server redirected to "https://wallabag.a.com/login“,miss the port.

wallabag log:
::ffff:10.0.3.9 - - [03/Jul/2025:10:53:02 +0800] "GET / HTTP/1.1" 302 215 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Edg/138.0.0.0"

reverse proxy config:
proxy_set_header Host '$host'; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Port $server_port; proxy_set_header X-Forwarded-Host $host:$server_port;

Dominant language
Shell
Stars
771
Forks
168
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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.

More from wallabag/docker

All issues in wallabag/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.