


What should I do if I cannot access the web page after apache is started?
Foreword:
Apache cannot be accessed after it is started. After investigation, we found that the port was not occupied, so we considered a firewall issue.
(Learning video sharing: Introduction to Programming)
Solution:
First we need to ensure that the remote Linux system has been installed, we use xshell Remote SSH login to the Linux system, we also need to ensure that apache has been installed using yum and other commands, and then we start troubleshooting and analysis
In order to be able to access the server remotely For web pages, we first need to ensure that the apache service httpd is running. We use the command to check the status of the corresponding service:
service httpd status
If it is running as shown in the figure, it means that the service has been started, otherwise we need to use the command Pull up the httpd service:
service httpd start
Then we need to determine the status of SELinux. SELinux is a security policy service under the Linux system, but due to the complicated settings and the need for system services and The access operation has a great impact. If it is not closed, it may cause some abnormal conditions. Therefore, we need to use the command to determine whether SELinux has been closed:
sestatus
If it is disabled as shown in the figure, it means it has been closed. , otherwise we need to use the command to temporarily close the policy service:
setenforce 0
Then we need to determine whether port 80 is occupied by other programs, use the following command to check:
netstat -lnp | grep 80
If port 80 is used by httpd as shown in the picture, it is OK, otherwise we need to make corrections, which will not be detailed here
Then we can first check whether the system firewall is turned on. When other services are normal, the inability to access the web page is most likely caused by the incorrect configuration of the firewall. Therefore, we first use the following command to determine the status of the firewall
service iptables status
If it is as shown in the figure below, it means that the system's firewall is running. In order to do a simple troubleshooting check, we can try to turn off the firewall first, and then turn it on and reconfigure it after confirming that it is a firewall problem.
service iptables stop
After I turned off the firewall, I found that I could access it normally. After confirming the root cause, we need to reopen the firewall for system security. Then we need to access the system. The tcp network of port 80 requests firewall configuration. We need to restart the firewall first
service iptables start
Then enter the command to configure the firewall and view the configured firewall policy
iptables -I INPUT -p TCP --dport 80 -j ACCEPT service iptables status
After completion, as shown in the figure, The configuration is complete and remote access to the web page on the server is OK
Related recommendations: apache tutorial
The above is the detailed content of What should I do if I cannot access the web page after apache is started?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

The steps to start Apache are as follows: Install Apache (command: sudo apt-get install apache2 or download it from the official website) Start Apache (Linux: sudo systemctl start apache2; Windows: Right-click the "Apache2.4" service and select "Start") Check whether it has been started (Linux: sudo systemctl status apache2; Windows: Check the status of the "Apache2.4" service in the service manager) Enable boot automatically (optional, Linux: sudo systemctl

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.

How to view the Apache version? Start the Apache server: Use sudo service apache2 start to start the server. View version number: Use one of the following methods to view version: Command line: Run the apache2 -v command. Server Status Page: Access the default port of the Apache server (usually 80) in a web browser, and the version information is displayed at the bottom of the page.

Apache cannot start because the following reasons may be: Configuration file syntax error. Conflict with other application ports. Permissions issue. Out of memory. Process deadlock. Daemon failure. SELinux permissions issues. Firewall problem. Software conflict.
