I’m setting up SSL in my apache server. After activating SSL in sysconfig and restart apache, I get this error
aldebaran:/etc/apache2 # apachectl start
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
AH00015: Unable to open logs
aldebaran:/etc/apache2 #
I have found that if I edit /etc/apache2/listen.conf
and comment the Listen 443 line, the error is gone and apache starts ok (no SSL).
So i thought that there must be some Listen 443 line in any other place and they were entering in conflict, but
aldebaran:/etc/apache2 # cat *conf |grep Listen
# Listen: Allows you to bind Apache to specific IP addresses and/or
# Change this to Listen on specific IP addresses as shown below to
# Listen directives: "Listen ::]:443" and "Listen 0.0.0.0:443"
#Listen 12.34.56.78:80
#Listen 80
#Listen 443
Listen 80
# Listen 443
aldebaran:/etc/apache2 # cat vhosts.d/*conf |grep Listen
aldebaran:/etc/apache2 #
So, that’s not the issue. I usually setup vhosts in /etc/apache/vhosts.d ( as YaST’s http module does ). You need vhosts if you want both port 80 and 443 to work, If you want I can show you the ones for my nextcloud instance, which has 2 vhosts entries, one for port 80 ( which does nothing but redirect to https ) and one for 443.
aldebaran:/etc/apache2 # apachectl start
(98)Address already in use: AH00072: make_sock: could not bind to address 192.168.2.5:443
no listening sockets available, shutting down
AH00015: Unable to open logs
aldebaran:/etc/apache2 #
First,
Because you’re deployed on vmware, you should have posted in the Virtualization forums
And now it sounds like you are executing functions that are specific to the virtualization and not typical of an application running on any kind of install (even on bare metal).
You’ll need to describe what VMware setup you have… ESX? Maybe you’re executing your vmware command within the context of some other kind of virtualization manager?
If you’re deployed in a VPS,
Then it’s conceivable that certain Management commands might invoke configurations within the virtual machine, but otherwise in this Applications forum, we hope to stick to commands that execute only on the local system.
No, it is not deployed on vmware it’s only that there were a vmware workstaton running on this machine (in fact i’m not using it , I installed it some time ago to test how shared vms worked, and it seems I forgot to remove it) and the https of the vmware (for the ws server, for sharing vms) was eneting in conflict with apache.
Your Workstation is likely configured with remote management enabled, the default port is port 443 (sharing the default SSL port).
If you are not using VMware Workstation for anything, and don’t intend to use it in the future it’d likely be good practice to uninstall and remove it…
If uninstalling isn’t sufficient to remove the app,
I outlined some steps for purging all remnants of an app from a system in the following post which needed to purge the system of PostgreSQL, you can modify for VMware Workstation. Since VMware Workstation likely was originally installed running the VMware Installer, you should run the installer again which should detect you installation and offer to uninstall for you. https://forums.opensuse.org/showthread.php/533714-Postgresql?p=2885264#post2885264
Then,
You you test your machine again for any processes using port 443, your Apache should work without the conflict Workstation was causing for you.