Before I had my 2nd server "optimized" by my management company I used to be able to access my CPANEL accounts via my ip address and then the ~username like:

http://67.xx.xxx.xxx/~rwood

This is the link that WHM provides when you list accounts and click on the IP, this used to work and does work on my other server.

It will work if I go to http://67.xx.xxx.xxx/~rwood/

But as this is not the link WHM provides I would like http://67.xx.xxx.xxx/~rwood (without the ending slash) to work again.

Management company says its a cpanel bug, but I REALLY dont think so.

Could anyone point me in the right direction on how to fix this?

tia
gp

contact cpanel and ask them..???

What? Im sure they keep very busy, and im thinking this is something messed up by ******* so if anyone has any suggestions on how i could fix this, that would be very much appreciated.

thanks again,
gp

It is either a Cpanel or Apache bug but it has been plaguing the combination from as far as I could remember.

When you don't put the trailing slash, you get re-directed to http://hostname/~account/ so is your hostname set, valid and resolving correctly?

I did have some trouble with the host name at the beginning and cpanel emailed errors about it on bootup. I believe I have since fixed it, and no longer receive the errors about host name resolving.

Is there a way that I can check if this is the problem?

thanks for the help

gp

try going to http://your.hostname.tld/ and see if you get anything, if you do, try http://your.hostname.tld/~username/ and see if you see the account.

http://page.gpnameserver.com/ works

http://page.gpnameserver.com/~rwood does not work

but

http://page.gpnameserver.com/~rwood/ does work

so its not a hostname problem?

thanks again,

gp

Nope, not a hostname problem since that seems to be working fine.
Must be a problem with your apache config or a cpanel bug.

And as it worked perfectly before my management company touched my setup, I assume its something in apache config?

Anyone else having this problem?

thx

gp

It looks like an Apache configuration problem.

These two should work by default like you would expect them to work. There are two potential sources for your problem: The mod_alias and the mod_rewrite settings in your httpd.conf and .htaccess.

Look at your httpd.conf and check for anything related to them. What do they look like? Also, what does your .htaccess file (in the user's public_html directory) contain?

Did you get this problem sorted out yet?

Its a bug so im told...never did find a fix to it. kinda sucks, i have the same problem.

Sorry tekpro, I had to dash off the other day.. I havent fixed it, im a little reluctant to put sany more time or effort into it.

gp

That is understandable. Nevetheless, I find that it is very suprising and odd as well, since I do not have that problem with Apache. Surely it is just a misconfiguration. It is not a serious problem really, but if you are interested in getting rid of it, I could help you out. PM me.