missing x-forwarded-for header on health checks #19

Closed
opened 2026-04-05 17:00:32 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @svandive on 4/2/2026

Describe the Bug

x-forwarded-for header does not appear to be being sent as part of the HTTP/HTTPS connections being made as part of the Test connections for Health validation testing of a HTTP/HTTPS Public Resource.

Environment

  • OS Type & Version: (e.g., Ubuntu 22.04)
    Pangolin/Gerbil: On AWS EC2 VPS - Docker 29.2.1 running top of Ubuntu 24.04 Server
    Newt: On home Lab Server - Docker 29.3.1 running on top of Ubuntu 25.10

  • Pangolin Version: 1.16.2

  • Gerbil Version: (not sure if this is correct, 1.16.2, I wasn't able to locate a specific version for Gerbil)

  • Traefik Version: 3.6.11

  • Newt Version: 1.10.4

  • Olm Version: (if applicable)

To Reproduce

I have Stalwart Mail Server setup as a Public HTTPS Resource, normal connections to the mail server for JMAP (JSON over HTTPS) are seeing and using the x-forwarder-for header, however connections for the Health Check are being reported as missing the x-forwarded-for header.

Configure Health Check to a backend resource.

Expected Behavior

I would expect all http/https connections made to backend resources will include the x-forwarded-for headers

*Originally created by @svandive on 4/2/2026* ### Describe the Bug x-forwarded-for header does not appear to be being sent as part of the HTTP/HTTPS connections being made as part of the Test connections for Health validation testing of a HTTP/HTTPS Public Resource. ### Environment - OS Type & Version: (e.g., Ubuntu 22.04) Pangolin/Gerbil: On AWS EC2 VPS - Docker 29.2.1 running top of Ubuntu 24.04 Server Newt: On home Lab Server - Docker 29.3.1 running on top of Ubuntu 25.10 - Pangolin Version: 1.16.2 - Gerbil Version: (not sure if this is correct, 1.16.2, I wasn't able to locate a specific version for Gerbil) - Traefik Version: 3.6.11 - Newt Version: 1.10.4 - Olm Version: (if applicable) ### To Reproduce I have Stalwart Mail Server setup as a Public HTTPS Resource, normal connections to the mail server for JMAP (JSON over HTTPS) are seeing and using the x-forwarder-for header, however connections for the Health Check are being reported as missing the x-forwarded-for header. Configure Health Check to a backend resource. ### Expected Behavior I would expect all http/https connections made to backend resources will include the x-forwarded-for headers
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#19