mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[PR #2400] Add CERT_BEHIND_PROXY setting to disable SSL certificate expiration warnings #3886
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#3886
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?
📋 Pull Request Information
Original PR: https://github.com/amidaware/tacticalrmm/pull/2400
Author: @jafolkerts
Created: 1/30/2026
Status: 🔄 Open
Base:
develop← Head:feature/cert-behind-proxy-setting📝 Commits (2)
9b3bf9dadd CERT_BEHIND_PROXY setting to disable SSL certificate expiration warningsdb894f4Add CLAUDE.local.md to .gitignore📊 Changes
2 files changed (+6 additions, -1 deletions)
View changed files
📝
.gitignore(+2 -1)📝
api/tacticalrmm/tacticalrmm/helpers.py(+4 -0)📄 Description
Summary
This PR adds support for a
CERT_BEHIND_PROXYsetting inlocal_settings.pyto disable SSL certificate expiration warnings when SSL termination is handled by an external reverse proxy.Changes
days_until_cert_expires()function inhelpers.pyto check for theCERT_BEHIND_PROXYsettingTrue, the function returns 999 days instead of calculating actual certificate expirationUse Case
This is useful for deployments where SSL termination occurs at a load balancer or reverse proxy layer (e.g., nginx, HAProxy, cloud load balancers), making the backend certificate expiration warnings irrelevant and potentially confusing.
Usage
Add to
local_settings.py:Testing
Tested on a production deployment with SSL termination at an external reverse proxy. The warning banner no longer appears in the UI after setting
CERT_BEHIND_PROXY = Trueand restarting services.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.