Fail2ban with docker bridge ip #3958

New Issue

Closed

opened 2026-03-07 19:21:16 -06:00 by GiteaMirror · 3 comments

GiteaMirror commented 2026-03-07 19:21:16 -06:00

Owner

Copy Link

Originally created by @snevas on GitHub (Jun 13, 2019).

I have my docker behind a apache proxy that does 80 > 81 per wiki instructions. When I try to setup fail2ban, I see it tries to ban the docker bridge ip based on this log:
[2019-06-13 09:26:51][bitwarden_rs::error][ERROR] Username or password is incorrect. Try again. IP: 172.17.0.1. Username:test@test.com.

Originally created by @snevas on GitHub (Jun 13, 2019). I have my docker behind a apache proxy that does 80 > 81 per wiki instructions. When I try to setup fail2ban, I see it tries to ban the docker bridge ip based on this log: `[2019-06-13 09:26:51][bitwarden_rs::error][ERROR] Username or password is incorrect. Try again. IP: 172.17.0.1. Username:test@test.com.`

GiteaMirror closed this issue 2026-03-07 19:21:17 -06:00

GiteaMirror commented 2026-03-07 19:21:17 -06:00

Author

Owner

Copy Link

@snevas commented on GitHub (Jun 13, 2019):

bitwarder_rs should use the X-Forwarded-For header to log the original ip.

@snevas commented on GitHub (Jun 13, 2019): bitwarder_rs should use the [X-Forwarded-For](http://en.wikipedia.org/wiki/X-Forwarded-For) header to log the original ip.

GiteaMirror commented 2026-03-07 19:21:18 -06:00

Author

Owner

Copy Link

@dani-garcia commented on GitHub (Jun 13, 2019):

Rocket uses the X-Real-IP header when determining the origin IP address, you should configure the proxy to set that one instead of X-Forwarded-For.

@dani-garcia commented on GitHub (Jun 13, 2019): Rocket uses the `X-Real-IP` header when determining the origin IP address, you should configure the proxy to set that one instead of `X-Forwarded-For`.

GiteaMirror commented 2026-03-07 19:21:18 -06:00

Author

Owner

Copy Link

@snevas commented on GitHub (Jun 13, 2019):

Hi Dani, thanks for all your work on the project. You rock!
I've tested setting the correct header and it works. I've changed the proxy example in the wiki @
https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples

@snevas commented on GitHub (Jun 13, 2019): Hi Dani, thanks for all your work on the project. You rock! I've tested setting the correct header and it works. I've changed the proxy example in the wiki @ https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples

GiteaMirror referenced this issue 2026-03-07 21:09:19 -06:00

[PR #3958] [MERGED] Container building changes #6998

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#3958