[Bug] Compliance Status fails https when behind reverse proxy

[hugobugomugo]

Describe the bug

when having pegaprox configured behind an reverse proxy, compliance says that https isnt enabled

Steps to Reproduce

1. setup pegaprox behind e.g. nginx
2. check compliance status in settings

Expected behavior

either pegaprox needs to detect that im accessing via https (which im not sure how to do if pegaprox itself is running on https, because technically its correct)

OR

Disable "https enabled" compliance status when reverse proxy is enabled
maybe there is a better way to handle it, im not sure

Environment

• PegaProx Version: 0.9.5
• Installation Method: docker
• OS: Debian 13
• Browser: Chromium: 146.0.7680.178
• Behind Reverse Proxy? nginx
• UI? corporate

Logs

Screenshots

Checklist

• I have searched existing issues to make sure this is not a duplicate
• I am using the latest version of PegaProx

[MrMasterbay]

Hi @hugobugomugo ,

thank you! This should be now fixed in the latest as we don't have a verifier anymore when reverse proxy is activated

[DjDhHome]

i want to know how to turn it off, all of them, i can not for the life if me build a lxc or Vm, i tried everything, none of the mirror site and pull, i think its after i was in compliance this started happening

let me restate this, i cant use promenux to build, i can build a Debian container