<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Apache web server SSL problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684796#M53877</link>
    <description>Apache 1.3.19.23 on HP-UX 11.0 or 11.11 -&lt;BR /&gt;I have two separate instances (separate config files, etc.) of apache web server on HP-UX 11.0 (and the same setup for testing on an 11.11 system). Each web server instance uses a unique IP address and each has SSL enabled by means of a Verisign secure server certificate. I have a separate /opt/apache/bin/apachectl for startup/shutdown of each one.&lt;BR /&gt;-----------------&lt;BR /&gt;Apache web server "A":&lt;BR /&gt;Is started with "-DSSL" and the config file is in the default location. The ports are specified in httpd.conf as:&lt;BR /&gt;Listen X.Y.Z.156:80 &lt;BR /&gt;Listen X.Y.Z.156:443&lt;BR /&gt;The port 443 is also speciied in the lines:&lt;BR /&gt;&lt;IFDEFINE ssl=""&gt;&lt;BR /&gt;Listen 443&lt;BR /&gt;&lt;/IFDEFINE&gt;&lt;BR /&gt;AND&lt;BR /&gt;&lt;VIRTUALHOST 443=""&gt;&lt;BR /&gt;-----------------------&lt;BR /&gt;Apache web server "B" configuration is identical to "A" except that the IP address is X.Y.Z.163 and the "-f" option is used in the startup to specify a separate httpd.conf file. It is also started with "-DSSL" option.&lt;BR /&gt;----------------------&lt;BR /&gt;If I start either A or B first, and in SSL mode, it is OK. The problem is in trying to start the second one in SSL mode.&lt;BR /&gt;For example, I first start A in SSL mode. It is OK. I check to make sure no process is using IP address X.Y.Z.163 (which will be used by B). Both "netstat -an|grep 163" and &lt;BR /&gt;"lsof -i -n -P|grep 163" display NO output. I try to start B in SSL mode. It fails with the following message in the error_log:&lt;BR /&gt;"Address already in use: make_sock: could not bind to port 443"&lt;BR /&gt;I can, however, start B in normal mode (no SSL) and it will be listening on both port 80 and 443. No matter which one I start second, the problem occurs, and it only occurs if I'm trying to start the second one in SSL mode. I'm stumped?&lt;BR /&gt;&lt;BR /&gt;Leon.Howorth@acs-inc.com&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/VIRTUALHOST&gt;</description>
    <pubDate>Sun, 17 Mar 2002 15:21:34 GMT</pubDate>
    <dc:creator>Leon A. Howorth</dc:creator>
    <dc:date>2002-03-17T15:21:34Z</dc:date>
    <item>
      <title>Apache web server SSL problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684796#M53877</link>
      <description>Apache 1.3.19.23 on HP-UX 11.0 or 11.11 -&lt;BR /&gt;I have two separate instances (separate config files, etc.) of apache web server on HP-UX 11.0 (and the same setup for testing on an 11.11 system). Each web server instance uses a unique IP address and each has SSL enabled by means of a Verisign secure server certificate. I have a separate /opt/apache/bin/apachectl for startup/shutdown of each one.&lt;BR /&gt;-----------------&lt;BR /&gt;Apache web server "A":&lt;BR /&gt;Is started with "-DSSL" and the config file is in the default location. The ports are specified in httpd.conf as:&lt;BR /&gt;Listen X.Y.Z.156:80 &lt;BR /&gt;Listen X.Y.Z.156:443&lt;BR /&gt;The port 443 is also speciied in the lines:&lt;BR /&gt;&lt;IFDEFINE ssl=""&gt;&lt;BR /&gt;Listen 443&lt;BR /&gt;&lt;/IFDEFINE&gt;&lt;BR /&gt;AND&lt;BR /&gt;&lt;VIRTUALHOST 443=""&gt;&lt;BR /&gt;-----------------------&lt;BR /&gt;Apache web server "B" configuration is identical to "A" except that the IP address is X.Y.Z.163 and the "-f" option is used in the startup to specify a separate httpd.conf file. It is also started with "-DSSL" option.&lt;BR /&gt;----------------------&lt;BR /&gt;If I start either A or B first, and in SSL mode, it is OK. The problem is in trying to start the second one in SSL mode.&lt;BR /&gt;For example, I first start A in SSL mode. It is OK. I check to make sure no process is using IP address X.Y.Z.163 (which will be used by B). Both "netstat -an|grep 163" and &lt;BR /&gt;"lsof -i -n -P|grep 163" display NO output. I try to start B in SSL mode. It fails with the following message in the error_log:&lt;BR /&gt;"Address already in use: make_sock: could not bind to port 443"&lt;BR /&gt;I can, however, start B in normal mode (no SSL) and it will be listening on both port 80 and 443. No matter which one I start second, the problem occurs, and it only occurs if I'm trying to start the second one in SSL mode. I'm stumped?&lt;BR /&gt;&lt;BR /&gt;Leon.Howorth@acs-inc.com&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/VIRTUALHOST&gt;</description>
      <pubDate>Sun, 17 Mar 2002 15:21:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684796#M53877</guid>
      <dc:creator>Leon A. Howorth</dc:creator>
      <dc:date>2002-03-17T15:21:34Z</dc:date>
    </item>
    <item>
      <title>Re: Apache web server SSL problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684797#M53878</link>
      <description>Leon&lt;BR /&gt;&lt;BR /&gt;Are they both trying to listen on 443?&lt;BR /&gt;&lt;BR /&gt;If one has the port then the other can't.&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Sun, 17 Mar 2002 19:47:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684797#M53878</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2002-03-17T19:47:23Z</dc:date>
    </item>
    <item>
      <title>Re: Apache web server SSL problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684798#M53879</link>
      <description>Hi I re-read your question.&lt;BR /&gt;&lt;BR /&gt;Is ssl locking out 443 on the first instance so that the second cannot attach?&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Sun, 17 Mar 2002 19:49:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684798#M53879</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2002-03-17T19:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Apache web server SSL problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684799#M53880</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;if both of them were listening on port 443 and blocking each other, why wouldn??t one use one apache with one httpd.conf in  which 2 virtual hosts are specified ?&lt;BR /&gt;&lt;BR /&gt;Greetings,&lt;BR /&gt;&lt;BR /&gt;Christoph</description>
      <pubDate>Mon, 18 Mar 2002 10:18:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684799#M53880</guid>
      <dc:creator>Christoph Rothe_3</dc:creator>
      <dc:date>2002-03-18T10:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Apache web server SSL problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684800#M53881</link>
      <description>The problem is here:&lt;BR /&gt;&lt;BR /&gt;&lt;IFDEFINE ssl=""&gt; &lt;BR /&gt;Listen 443 &lt;BR /&gt;&lt;/IFDEFINE&gt; &lt;BR /&gt;&lt;BR /&gt;which tells Apache to bind to port 443 on *ALL* interfaces. This means that the first instance gets it and the second can not. The quick fix is remove this config block from each conf file.&lt;BR /&gt;&lt;BR /&gt;The prefered solution, however, is to configure all of these virtual hosts in one Apache server. The key is to give each SSL virtual host a unique key and crt.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Mar 2002 00:30:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684800#M53881</guid>
      <dc:creator>Jordan Bean</dc:creator>
      <dc:date>2002-03-19T00:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Apache web server SSL problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684801#M53882</link>
      <description>Thank you Jordan Bean.&lt;BR /&gt;I should have noticed something so&lt;BR /&gt;obvious.</description>
      <pubDate>Wed, 20 Mar 2002 19:38:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/apache-web-server-ssl-problem/m-p/2684801#M53882</guid>
      <dc:creator>Leon A. Howorth</dc:creator>
      <dc:date>2002-03-20T19:38:18Z</dc:date>
    </item>
  </channel>
</rss>

