Apache is functioning normally - website not shown

L

Lucas.

Verified User
Joined
Oct 9, 2021
Messages
12
Hi,
I migrated a DirectAdmin backup from a shared host to a VPS.
Unfortunately when trying to set up the first domain, I get the apache page.

Apache is functioning normally

What could be wrong and how do I check this?
Thanks for helping me out.

www.supervisual.be

Lucas.
 
looks like your domain pointed to IP where is no virtualhost for this domain.
 
Richard G said:
Glue records are only used for nameservers.
Check if the domain is set to use the versio nameservers and check at Versio if A records are set correctly.

Next you can check this.
Click to expand...
Hi Richard!
Thanks for your reply. In Directadmin (under admin -> nameservers) it is set to the Versio name servers. However I'm not sure this is correct.
I did not get any name server details from Versio. I just contacted them to ask what they are.
Schermafbeelding 2021-10-10 om 12.26.47.png

A Records are also pointing to my VPS:
Schermafbeelding 2021-10-10 om 12.30.51.png

It seems the domain name points to the right server, but the server does not point to the right html folder.
 
I'm sorry, I didn't use external nameservers for so long that I'm not 100% sure anymore.

As far as I remember (if I remember correctly) in the admin configuration section itself, it should still read ns1.hostingcompany.com and ns2.hostingcompany.com.

If you are logged in as admin and choose reseller level, then you can use the "set the name servers that will be assigned to new users" there and point to the acx.nl nameservers. I think you did that so that seems correct.

And then in the customer domain section in DNS it should read in Directadmin:
ns1.hostingcompany.com 3600 NS nszero1.axc.nl.
ns2.hostingcompany.com 3600 NS nszero2.axc.nl.
(mind the trailing dot).

If I'm not mistaken... it's a long time ago I worked with external nameservers so I'm doing this out of my head.

I've just checked the changes you made with the axc nameservers and it seems it's correct now.

Check the ip in DNS of the customer which is used. This should all be your vps ip's.
Also check /etc/virtual/domains if the domain is present in that file.
Same for /etc/virtual/domainowners if the domain and the accountname is in there.

Also check the help file.
 
For anyone after me having the same problem.
Eventually all hosting settings where okay. The ip address in the httpd file was not correctly set because I migrated from another server. (still had the old servers ip)

/usr/local/directadmin/data/users/USERNAME/httpd.conf
 
Lucas. said:
The ip address in the httpd file was not correctly set
Click to expand...
In exactly which httpd file? Because now you're pointing to a users httpd.conf file which will be rebuild by a ./build rewrite_confs command.
People should normally not have to edit every user's httpd.conf file. Suppose you would have a couple of hundred accounts...

So I presume you mean the ip's should be correct in:
/usr/local/directadmin/data/admin/ip.list
and
/usr/local/directadmin/data/admin/ips/
and the
/etc/httpd/conf/ips.conf file?
 
Hi Richard,

Yes you are right. When I rebuilt this file afterwards, the HTTPD settings were wrong again.
I went searching and I have noticed that the server ip settings in Directadmin were not correct.
After changing this server settings, rebooting and regenerating the Httpd file, everything worked as it should.
 
You must log in or register to reply here.
Back
Top