I have recently installed a ESM core and console server. I have added a URL re-write rule to allow my traffic to be proxied through this server. The issus is that the web based traffic is rewriting no problem. Its the communication on port 2125 that is being hindered through the reverse proxy. So I tried to specify a different port on the server installation like 443 so all comunications head through port 443 however the installer just yelled at me.
Is anyone else attempting to have TRAPS traffic go through a reverse proxy?
The reason I am trying to do URL re-write is because I am limited in the amount of external IP addresses I have left.
Is this a feasible method? How are we supposed to deploy the agent externally if I don't have any external IP's left?
Could you not use destination NAT to allow your clients to check in/upload externally? Or preferably you could use an always-on VPN back to your internal network that your clients establish? I'm not sure on the requirement to have the server accessible from outside the network? (maybe I don't have enough traps knowledge) I understand that the traps clients would still function and be protected if they are not connected to the server.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!