Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to setup my web server (Apache) for a secure site.
I have established the SSL setting in virtual server.
I have created my certs.
I can start httpd at this state.
I can also start https: // localhost.
but I can't log into https: // .... from another machine (through the internet).
When I add the port 443 as a listening port in Apache server settings, I can't start httpd anymore. I get the following error:
Starting httpd: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
That is when it is set to listen to all address at port 443. When I put my own IP, it does the same.
I could not figure out how to open port 443 in the firewall (it is not showing as open) so I turned off the firewall. I still could not start htppd.
The problem is definately not firewall related. Everything your firewall does is restricting access to that port which doesn't affect the port binding.
The problem with "Address already in use" is that a program is already using that port. To check which program it is use netstat -A inet -lnp.
1. Without port 443 added as a listening port but with SSL checked under virtual
Response showed that port 443 was taken by httpd along with port 80.
2. With port 443 added as a listening port and SSL checked
Response showed that both port 80 and 443 were open but this is only because httpd could not start because it registered that port 443 was already in use during startup.
Conclusion
With SSL checked, it automatically opens 443 for listening and the addition of adding a port for listening is not required.
If this is the case, I am back to why I can't I get through to the server when both ports are open for listening? The only thing I can think of is that the firewall is blocking port 443. Any ideas?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.