Facebook
Twitter
J
jeremy.brown
Guest
Hi,
OS: Windows 2003
PLESK: 6.5.2
I've tried without any success to move the apache admin interface onto a second exclusive ip (not managed by plesk) with no luck.
It seems that something is globbing to port 443 on all bound ips.
Actions:
- modified server configs to Listen x.x.x.x:443 (x.x.x.x) is the dedicated IP
- modified ssl config for mod_ssl to 443 as well
All daemons come up except the admin (apache complains about binding to 443). IIS reports that the only webserver is bound explicitly to the primary IP which is managed by PLESK (this is also the ip used for shared, physical configs).
Anyone?
J.B.
OS: Windows 2003
PLESK: 6.5.2
I've tried without any success to move the apache admin interface onto a second exclusive ip (not managed by plesk) with no luck.
It seems that something is globbing to port 443 on all bound ips.
Actions:
- modified server configs to Listen x.x.x.x:443 (x.x.x.x) is the dedicated IP
- modified ssl config for mod_ssl to 443 as well
All daemons come up except the admin (apache complains about binding to 443). IIS reports that the only webserver is bound explicitly to the primary IP which is managed by PLESK (this is also the ip used for shared, physical configs).
Anyone?
J.B.
