Hello,
I want to to pass all traffic to UI on "external clients" via comm_server in DMZ.
For https traffic it's no problem - I have Apache working as reverse proxy and it works.
For mxProxy I think I should run mxProxy process also on the same comm_server in DMZ, and in DNS for external clients point name of WinCC server to address of comm_server in DMZ.
But I have already mxProxy running on WinCC OA servers. This proxy is used by "internal clients".
1. Is possible to run mxProxy directly on WinCC server and another mxProxy on another machine?
2. How to configure mxProxy on comm_server? Should I use separate config file or simply copy original one from WinCC server?
3. How to point for different clients which mxProxy should them use? Can it be done via different entries in e.g. config.linux and config.nt files?
4. Can I use different mxProxy entries for different UI ( [ui_xx] section)?
Best Regards
mxProxy and Apache
- gschijndel
- Posts:376
- Joined: Tue Jan 15, 2019 3:12 pm
Re: mxProxy and Apache
1. Yes, it is possible to run multiple mxProxies.
2. Never configured it before, but I the remote mxProxy connection must be allowed by adding this to the WinCC OA server configs:
[data] & [event]
mxProxy = "none" OR localAddress = ""
This will make the data and event managers accessible from remote hosts, so you might additional settings to limit this access (with a firewall and/or ip_allow/ip_deny).
3. Yes, it could be done via different config files.
4. Yes, general config keywords could be used in different sections.
2. Never configured it before, but I the remote mxProxy connection must be allowed by adding this to the WinCC OA server configs:
[data] & [event]
mxProxy = "none" OR localAddress = ""
This will make the data and event managers accessible from remote hosts, so you might additional settings to limit this access (with a firewall and/or ip_allow/ip_deny).
3. Yes, it could be done via different config files.
4. Yes, general config keywords could be used in different sections.