Let us take a closer look at the error, apache is functioning normally fix DirectAdmin. At Bobcares our Server management support services can give you a detailed overview of the error and its causes.

error: getting the apache page. Apache is functioning normally

The error might trigger based on one of the causes given below:

Cause 1

In this case, if apache is functioning normally fix DirectAdmin; the value the domain resolves to *at your computer* is not matching the value apache is using. Go to Admin Level -> Show All Users, look for the domain, and see what IP it’s configured to use.

The next step is to determine what IP address the domain resolves to. It is advisable to use an external server, such as dnsreport.com or other free lookup services, to find the IP address to which the name resolves. These two IP addresses must match.

Please note that if we have recently updated the IP of the domains, we may have to wait up to 4 hours for the new IP to propagate to us. So seeing the above pages is *normal* while changing IP addresses. Lower the TTL before making the IP change to reduce this time.

Cause 2

The virtualhost is not specified in the Apache configurations. There are a few things to look into. The user httpd.conf file is present in /usr/local/directadmin/data/users/username/httpd.conf and must Include into the main /etc/httpd/conf/httpd.conf in one of two ways, depending on the configuration.

For configurations on apache is functioning normally fix DirectAdmin:

1. If we have the custombuild (typically Apache 2.2), we should see the following line in /etc/httpd/conf/httpd.conf:

   Near the bottom, include the file conf/extra/directadmin-vhosts.conf. The Include line for the user httpd.conf should then appear in the /etc/httpd/conf/extra/directadmin-vhosts.conf file, as should /usr/local/directadmin/data/users/username/httpd.conf. If that is not the case, we can change all of the apache configuration files with:

   cd /usr/local/directadmin/custombuild
./build rewrite_confs

   For this configuration, make sure we observe the following for apache is functioning normally fix directadmin error management:

   apacheconf=/etc/httpd/conf/extra/directadmin-vhosts.conf
in the /usr/local/directadmin/conf/directadmin.conf.
2. It’s the same notion if we’re using customapache (typically apache 1.3), but the user httpd.conf is different. Included in /etc/httpd/conf/httpd.conf is /usr/local/directadmin/data/users/username/httpd.conf. Also, apacheconf=/etc/httpd/conf/httpd.con should be present in /usr/local/directadmin/conf/directadmin.conf.

Troubleshooting 1:

We can use multiple troubleshooting options for the error apache is functioning normally fix DirectAdmin some of them as shown below:

• Verify that the domain is addressed to an IP address that has a virtualhost for this domain.
• After migrating from another server, ensure that the IP address in the httpd file is appropriately set. (The old server’s IP address may still be present).

  /usr/local/directadmin/data/users/USERNAME/httpd.conf
• Please ensure that the IP address assigned to the domain matches the IP address it refers to. If https isn’t working, I’d guess the person has SSL deactivated.
• Force Apache/nginx to restart using the following code:

  killall -9 httpd
service httpd start and check if it resolves the problem.

• The other method for apache is functioning normally fix directadmin error is to Examine the virtualhost. If we see the “welcome to apache” page, it signifies that the virtualhost is not loaded in the httpd.conf files for that IP address. It’s possible that the user’s httpd.conf isn’t included at all in the main httpd.conf, or the IP address that the domain resolves to doesn’t match the IP address defined in the virtualhost.

  Using custombuild, we can easily repair it by entering the code below.

  cd /usr/local/directadmin/custombuild
./build rewrite_confs
• Make sure the IP in /etc/hosts matches the domain/user DirectAdmin to tackle the apache is functioning normally fix directadmin error.
• If we just want to host one website on a server with a single IP address and want the site to be visited by that IP, we can do so as follows:

  Firstly modify the file:/etc/httpd/conf/extra/httpd-vhosts.conf:

  DocumentRoot /var/www/html

  Change the code given above to the code as shown below:

  DocumentRoot /home/user1/domains/domain.com/public_html

  Rename user1 and domain.com with the real username and domain. Note to alter them only within sections:

  VirtualHost 11.22.33.44:80
...
...
...
VirtualHost
VirtualHost 11.22.33.44:443
...
...
...
VirtualHost

  Where 11.22.33.44 is the server IP address. After that run the code:

  chattr +i /etc/httpd/conf/extra/httpd-vhosts.conf

  Finally, restart the Apache.

Troubleshooting 2:

• In the case of using the “chattr +i” on any configuration files. Please do the following instead of it now to manage apache is functioning normally fix DirectAdmin:

  chattr -i /etc/httpd/conf/extra/httpd-vhosts.conf mkdir -p /usr/local/directadmin/custombuild/custom/ap2/conf/extra cp -p /etc/httpd/conf/extra/httpd-vhosts.conf /usr/local/directadmin/custombuild/custom/ap2/conf/extra/httpd-vhosts.conf

• Run the code given below:

  chattr -i /etc/httpd/conf/extra/httpd-vhosts.conf

  Make the necessary changes and run the command:

  chattr +i /etc/httpd/conf/extra/httpd-vhosts.conf

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have learned more about the error apache is functioning normally fix DirectAdmin, the factors causing it, and how to manage it with the troubleshooting options with the support of our Server management support team.