[GH-ISSUE #5384] Reverse Proxy with NB_PROXY_ACME_CERTIFICATES false not indicated correctly by dashboard #11142

Open
opened 2026-08-05 01:28:38 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @konstfish on GitHub (Feb 18, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5384

Describe the problem

When setting up the Reverse Proxy with NB_PROXY_ACME_CERTIFICATES set to false the management (or dashboard) will incorrectly display an "Issuing certificate..." spinner. This does not hinder the proxies functionality.

To Reproduce

Steps to reproduce the behavior:

  1. Set up a proxy instance with NB_PROXY_ACME_CERTIFICATES false & in my case a wildcard certificate generated by cert-manager. (Subject Alt Names proxy.example.com & *.proxy.example.com)
  2. Create a Service
    Image

I wrote blog post on the exact setup steps covering how to run the proxy on Kubernetes https://konst.fish/blog/NetBird-Reverse-Proxy-on-Kubernetes (If this counts as self promotion I'm happy to remove it from the issue)

Expected behavior

The dashboard should indicate the self-managed certificate status of the proxy.

Are you using NetBird Cloud?

Self-hosted using the Helm Chart from netbirdio/helms

NetBird version

v0.65.2 (proxy & mgmt), v2.32.3 (dashboard)

Is any other VPN software installed?

No

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings

Loving the proxy so far! I have a question kind of related to this issue, I'm assuming this isn't the case, but will the proxy support serving http in the future without any required certificate setup? This would make the deployment for infrastructures with existing ingress controllers a bit easier.

Originally created by @konstfish on GitHub (Feb 18, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5384 **Describe the problem** When setting up the Reverse Proxy with `NB_PROXY_ACME_CERTIFICATES` set to `false` the management (or dashboard) will incorrectly display an "Issuing certificate..." spinner. This does not hinder the proxies functionality. **To Reproduce** Steps to reproduce the behavior: 1. Set up a proxy instance with `NB_PROXY_ACME_CERTIFICATES` false & in my case a wildcard certificate generated by cert-manager. (Subject Alt Names proxy.example.com & *.proxy.example.com) 2. Create a Service <img height="296" alt="Image" src="https://github.com/user-attachments/assets/c070b1e5-7984-43f3-813a-72bbcc173a8a" /> I wrote blog post on the exact setup steps covering how to run the proxy on Kubernetes https://konst.fish/blog/NetBird-Reverse-Proxy-on-Kubernetes (If this counts as self promotion I'm happy to remove it from the issue) **Expected behavior** The dashboard should indicate the self-managed certificate status of the proxy. **Are you using NetBird Cloud?** Self-hosted using the Helm Chart from netbirdio/helms **NetBird version** `v0.65.2` (proxy & mgmt), `v2.32.3` (dashboard) **Is any other VPN software installed?** No **Have you tried these troubleshooting steps?** - [ ] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [ ] Searched for similar issues on GitHub (including closed ones) - [ ] Restarted the NetBird client - [ ] Disabled other VPN software - [ ] Checked firewall settings Loving the proxy so far! I have a question kind of related to this issue, I'm assuming this isn't the case, but will the proxy support serving http in the future without any required certificate setup? This would make the deployment for infrastructures with existing ingress controllers a bit easier.
saavagebueno added the triage-needed label 2026-08-05 01:28:38 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11142