[Archivesspace_Users_Group] Setting up SSL - binding port 443 to Apache

Zachary L Pelli zachary.pelli at shu.edu
Thu Feb 16 11:03:27 EST 2017

I am following these directions to set up our AS for SSL:


Now I have run in to an issue. I set up the firewall, configure the Apache httpd.conf, but when I restart httpd, I get an error. The error comes from the "Listen 443" in the ssl.conf file. According to the Apache error log:

[Wed Feb 15 16:45:50.101298 2017] [core:crit] [pid 16935] (22)Invalid argument: AH00069: make_sock: for address [::]:443, apr_socket_opt_set: (IPV6_V6ONLY)
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
(98)Address already in use: AH00072: make_sock: could not bind to address
[Wed Feb 15 16:45:50.101339 2017] [mpm_prefork:alert] [pid 16935] no listening sockets available, shutting down
[Wed Feb 15 16:45:50.101341 2017] [:emerg] [pid 16935] AH00019: Unable to open logs, exiting

I nmap the server and I see:

80/tcp   open   http           Apache httpd 2.4.6 ((Red Hat Enterprise Linux)
443/tcp  open   ssl/http       Jetty 8.1.5.v20120716

So it seems Apache cannot bind to the port because ArchivesSpace's Jetty sets up shop on the port. Since I have to go through IT to open any new ports, I would much rather stick to 443 than bind Apache to something else. How could I configure Jetty to NOT listen on 443? Any other possible solutions? Thanks in advance.

Zach Pelli
Digital Collections Developer
Walsh Library, Seton Hall University

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170216/65e408a0/attachment.html>

More information about the Archivesspace_Users_Group mailing list