Replies: 1 comment
-
ran across something just after posting this. I seem to have a network issue in docker that I need to address before I mess with this. So I'm closing the discussion for now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on moving over from a standalone nginx install to the NPM docker setup. I'm having trouble with a couple of hosts that need some specific headers to work. The examples below are from a LibreNMS install, but I'm seeing it on a few hosts with specific headers needed. Here is the working config from my original nginx server:
That works just fine. I added the host to NPM and I get a 502 when I try to access it. So I set a custom location of / and tried to apply my settings there:
But I still get 502. When looking at the generated config file, I see some of the headers I set in the custom location are overwritten by some default values:
I see a couple of the headers I set are being set just below my custom settings with the default values. But even after manually deleting those and restarting, I get the 502 errors.
Any suggestions on getting it working through NPM given the original nginx config works?
Beta Was this translation helpful? Give feedback.
All reactions