Is your feature request related to a problem? Please describe.
I am not able to customise the NetBird Reverse Proxy error pages (502, etc) to A) suit the branding of the web service, or B) obfuscate the stack being used (NetBird) for security reasons.
Describe the solution you’d like
I use NetBird for its VPN functionality, but I also find the reverse proxy feature extremely useful. And I use it currently to host a couple of web services (Yes. I know it’s in beta, but so far I found it to be fairly stable.)
I have noticed that when an error occurs with the origin server (e.g., the reverse proxy can’t reach the origin server, or the origin server returns some kind of an error code). The client gets presented with a NetBird error page. This is quite nicely styled. However, it seems to be more targeted towards the NetBird administrator, with a link to documentation, rather than a random user who has hit an issue.
Furthermore, in some cases, it’s a bit of an information leak because it reveals that you’re using NetBird in the stack. Therefore, I would really appreciate if there was a functionality to be able to override the default NetBird error page, ideally, on a per service basis in the reverse proxy.
So for some services, you could leave the default page enabled, whereas for others, you can set a custom page. For example, what I would probably do for some of my services is just set a very basic error page, almost like the Apache or NGINX defaults. But you could also do something like add on-brand error pages for your specific service if you wanted.
I am not sure, this might be something against Netbird’s terms, but that’s a bit more nuanced then I would know instead the Netbird legal team. The feature itself is nice though, however. I would suggest asking the devs directly on their slack, or waiting for a response on the forum.
Would you be able to elaborate a bit on the “terms”? I don’t really know anything about “terms” for Netbird (should probably research it), but why would custom error pages possibly be against these terms?
White-labling netbird more specificly, I’m just a community support agent. So I am only guessing here, but you could best ask on the Netbird slack. Or the Github Issues tab. As this is specific to editing the web source of netbird and it’s management ui. (Or proxy ui)
OK I see. I figured considering its an open-source tool this would not be an issue but I may be wrong.
Also, I am not looking to truly white-label the system (E.G remove “Netbird” from the management I/F etc). This is purely, to remove the evidence that a given exposed service (E.G webserver, exposed via NB Reverse Proxy) is using a Netbird stack (as is currently revealed in the HTTP error pages (E.G 5xx errors)).
Just the same principle to how NGINX by default returns a header like this: Server: nginx/1.27.0 and how it is commonly removed via a line in config: more_clear_headers 'Server';