Repository navigation
Replies: 3 comments 1 reply
|
There is already a separate URL for exactly this case: It only applies to the agent connection, that is the install line, reinstall, re-emit and auto-reinstall. Everything else keeps using The agent then downloads the installer over the LAN address and the Pangolin login never enters that flow. Both values accept http or https, so if the LAN listener is plain HTTP that is fine as long as the LAN path is allowed. One caveat: the address has to be reachable from the routers themselves, and it is what gets written into the agent config, so a later change of LAN IP means re-emitting or reinstalling. |
|
the server reads it's config from for the netpulse-agent, it is |
|
Closing the loop with what @crowedavid pointed at, since "where do I put it" was the missing half. The two URLs are server settings and live with the rest of the config, in NETPULSE_PUBLIC_URL=https://netpulse.example.com
NETPULSE_AGENT_URL=http://192.168.1.50:8080Two details that cost time if you find them the hard way. The scheme is required: a bare From then on the install line, reinstall, re-emit and auto-reinstall all use the LAN address, which is the path that broke for you after a router upgrade. Nothing else changes: the panel keeps answering on the public URL, so Pangolin keeps guarding it. The agent side is separate, If it works on your setup, say so and I will mark this solved. If the LAN listener is plain HTTP and something along the way refuses it, paste what the server logs and we look at it. |
Uh oh!
There was an error while loading. Please reload this page.
I currently run NetPulse behind a reverse proxy which is gated by Pangolin's login. This presents issues when I have to reinstall the agent after a router upgrade. Becuase it's gated, when the script is called, it fails with an auth error.
We should have an option to add a separate internal IP for cases like this so it can effectively pull the Agent installer.
All reactions