Cannot bind a spcific IP to Apache
Posted: 30. March 2021 08:58Good day,
I am trying really hard to set up XAMPP but not having much luck. I installed the latest version on Server 2008 R2. My issue is as follows:
1: I have a mail server already using port 443, so need to bind Apache to a different IP/port combination, still using port 443.
2: If I leave the Apache configuration files (httpd.conf and httpd-ssl.conf) unaltered then obviously Apache will not start due to the mail server already using port 443. Acceptable and understandable.
3: If, however, I change the "listen" directive in both the above files, then Apache will STILL not start, throwing out a very generic "service-specific Incorrect function" error in Windows event viewer. Nothing shown in Apache error log.
I have tried to follow numerous instructions dealing with binding Apache to a specific IP/port combination, and they all sat essentially the same thing: simply change the "listen" directive and it will work. But it does not. Where am I going wrong or is this a issue specifically with XAMPP/Apache?
I am trying really hard to set up XAMPP but not having much luck. I installed the latest version on Server 2008 R2. My issue is as follows:
1: I have a mail server already using port 443, so need to bind Apache to a different IP/port combination, still using port 443.
2: If I leave the Apache configuration files (httpd.conf and httpd-ssl.conf) unaltered then obviously Apache will not start due to the mail server already using port 443. Acceptable and understandable.
3: If, however, I change the "listen" directive in both the above files, then Apache will STILL not start, throwing out a very generic "service-specific Incorrect function" error in Windows event viewer. Nothing shown in Apache error log.
I have tried to follow numerous instructions dealing with binding Apache to a specific IP/port combination, and they all sat essentially the same thing: simply change the "listen" directive and it will work. But it does not. Where am I going wrong or is this a issue specifically with XAMPP/Apache?