Domain pointers not working correctly.

D

defamai

Verified User
Joined
Apr 15, 2006
Messages
7
Hello,

I'm having several problems which I believe are related at the moment, those being listed below:
1. When I attempt to use the admin level "Custom HTTPD Configurations" feature, I recieve the message "error reading httpd.conf". I've checked /usr/local/directadmin/data/users/[user]/httpd.conf,
and the permissions are as follows:
-rw-r--r-- 1 diradmin diradmin 2352 Apr 15 15:51 httpd.conf
In addition, My domain pointers are returning Error 404 - "The requested URL / was not found on this server.", when they are accessed. I have checked the domain they should be pointing to, and do not recieve a 404.
I've checked /etc/virtual, and I see the pointer to the other domain.

I've checked the DNS records, and everything appears to be valid as well.

In addition, I've checked /usr/local/directadmin/data/users/httpd.conf, and the domain is listed under ServerAlias in the virtual host.

The operating system is FreeBSD 6, and we're running the latest version of directadmin.

Any help would be much appreciated.
 
Last edited:
Hello,

You're trying to customize the httpd.conf for the domain pointers? That won't work because domain poitners don't have any of their own virtualhosts. They're just inserted into the virtualhost of it's main domain as a ServerAlias.

Try clicking on the domain name that the domain pointer is created under.

Not as sure about the 404 errors. That would generally mean that a file is being access directly that isn't there. If you're accessing just "domainpointer.com" ... then you'd either see the index file, a forbidden message if there is no index, or the directory contents. A 404 for just "domainpointer.com" might indicate that there is an .htaccess file in the public_html redirecting or something like that.

John
 
My apologies, I suppose I must have been unclear before.

When attempting to customize the httpd.conf for any domain (Including TLD domains), I recieve the previously stated error.

I've verified that apache is actually using the configuration file, by inserting errors into one of these custom files, then running the httpd configtest command. And yes, I recieve the 404 when accessing domainpointer.com, which should be pointing to domainpointer.net
I've also verified that there is no .htaccess file baring access to this directory.

EDIT:
Upon examining /var/log/httpd/domains/[domain name].error.log, I'm seeing this:
"[Sat Apr 15 21:59:58 2006] [error] [client 70.136.41.49] File does not exist: /home/admin/domains/[domain_pointer_name]/public_html/404.shtml
"
why is it looking under the administrator account for these, if the alias was not created from it?
 
Last edited:
Well, fixed one of the two problems.
The domain pointer now works, however, I'm unable to edit the users httpd.conf file from directadmins interface. Not really that big of a deal, since I can just do it through bash, but rather puzzling all the same. I've checked all of the parent folders to the users httpd.conf file as well, and all the permissions are set correctly.
Thank you for your help in resolving the first problem, and all help is appreciated in resolving the second
 
Regarding "error reading httpd.conf" .. is the domain you're click the domain pointer or the main domain itself?

The way it works, is the domain/username is taken from the /etc/virtual/domainowners file. The username is taken from there.. as assembled as "/usr/local/directadmin/data/users/username/httpd.conf"... so.. really, my only guess is that the domain pointer isn't in the /etc/virtual/domainowners file.

Also, make sure the httpd.conf is chmod 644. Looks like DA is running as "nobody" when it reads in the httpd.conf file so it has to be world readable.

John
 
You must log in or register to reply here.
Back
Top