I have a server with IPs: 192.168.5.10 - .12. I have bound PRTG to .12 with SSL (443). I have disabled the port 80 redirect with the registry setting indicated in another thread.
When configured in this manner, my IIS sites bound with SSL will not run. I'm not sure if the problem is PRTG or IIS, but I suspect PRTG.
I have two sites in IIS 7 that both use SSL on port 443. They are bound to the .10 and .11 IPs only. Neither can be started once PRTG is running. Likewise, if IIS is started first, PRTG cannot start.
I have no idea what is causing this conflict as everything should be bound to its own distinct IP. My only guess is that internally PRTG is actually binding to all IPs on the machine on port 443.
In IIS, trying to start a site gives the error: "The process cannot access the file because it is being used by another process." This error generally indicates a binding error.
Running netstat -ano -p
tcp only seems to show the 443 port and 1801 being bound though:
TCP 192.168.5.12:443 0.0.0.0:0 LISTENING 3160
At this point I'm stumped. I've tried restarting both the IIS service and PRTG with no success. If PRTG is stopped, both SSL sites can be started and run without issue.
Add comment