Detailed explanation of the pitfalls of Apache domain name configuration

I have never used apache. After I started working, I have always used nginx (not operation and maintenance). Recently, a small project of a friend of mine had some problems. I came into contact with apache.

First, configure the domain name and listen to port 889

Step 2: Restart Apache

/www/server/apache/bin/apachectl restart

The third step is to access it with an external browser.

Step 4. Identify the cause

1. Access the server locally using curl localhost:889, and the connection is refused

2. Check the port usage lsof -i:889

3. Query the monitoring netstat -tnl.

Monitoring is normal

4. I thought that the server port might not be open, so I used firewall-cmd --list-ports to check the open ports.

No port 889

5. Take centos7 opening port 889 as an example:

Adding Ports

firewall-cmd --zone=public --add-port=889/tcp --permanent (--permanent takes effect permanently, and will become invalid after restart without this parameter)

Refresh Rules

firewall-cmd --reload

View the specified port

firewall-cmd --zone=public --query-port=8080/tcp

Delete the specified port

firewall-cmd --zone=public --remove-port=8080/tcp --permanent

View all open ports

firewall-cmd --list-ports

6. In the end, it still doesn't work, because on Alibaba Cloud, the dedicated network limits the port, so you have to set it up

If you have a friend like me who is new to this problem, you can deal with it like this

This is the end of this article about the pitfalls of Apache domain name configuration. For more relevant content about Apache domain name configuration, please search for previous articles on 123WORDPRESS.COM or continue to browse the related articles below. I hope you will support 123WORDPRESS.COM in the future!