mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #5330] Flag OpenSSL module to use FIPS mode #3171
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#3171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DrkCorners on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5330
Is your feature request related to a problem? Please describe.
It would be really nice to set NPM in "FIPS Mode". This would help significantly with compliance issues and putting non-compliant services behind NPM to ensure that the communications were compliant.
It looks like OpenSSL has a flag that can be set to use the FIPS certified module (https://docs.openssl.org/master/man7/fips_module/#making-all-applications-use-the-fips-module-by-default).
Describe the solution you'd like
As I think NPM uses OpenSSL for its cryptographic functions, can the FIPS module be included and a switch (in GUI or in docker compose) be set to use only FIPS algorithms/libraries?
Describe alternatives you've considered
I have not found any fully open source reverse proxy that has a FIPS mode. All that have an option seems to be locked behind a paywall that includes a bunch of other features that are overly complex and painful.
Additional context