511 access not allowed after apache upgrade

AlaskanWolf

Well-Known Member
Aug 11, 2001
535
0
316
Fremont CA
Not sure where this goes, but theres a bug after upgrading apache, i recompiled and just cant figure it out

when you go to http://sandy.thehideout.net/~wwwhost/ or even the ip/~whatever url.....

you get

511 Access Not Allowed

http://sandy.thehideout.net/~wwwhost/

Access Not Allowed from this Domain
You are attempting to access a user dir from a domain that is not owned by the user. Please correct the domain that you are attempting to use to access this url.
--------------------------------------------------------------------------------

Apache/1.3.26 Server at www.www-hosting.net Port 80
 

SHSaeed

Well-Known Member
May 9, 2002
243
0
316
Actually, I kind of like that. It prevents users to access sites on the server from the wrong domains. For example, if your server's host name is &server3.webhost.com&, people can't access other sites by going to http://www.any-users-site.com/~account/, they have to load http://server3.webhost.com/~account/.
 

myros

Active Member
Dec 16, 2001
42
0
306
Glad I found this post :)
Any new IP-less accounts could no longer be viewed until the domain name went through. Was just giving the 511 error. Had me puzzling through the log files for hours lol.

Thanks for the tip on accessing them.

Gonna leave that mod in I think, seems like a good service.

Cheers,
Myros
 

rbmatt

Well-Known Member
Oct 21, 2002
211
0
166
I had this problem, and I did have some bandwidth modules on, but no more than a different, working server. So, I went through httpd.conf line by line to see what was different. Finally, them main server's virtualhost servername on the &bad& box was set to localhost.localdomain. I changed it to its actual name, restarted apache, and it works now.
Maybe this will help someone...
 

twhiting9275

Well-Known Member
Sep 26, 2002
560
28
178
cPanel Access Level
Root Administrator
Twitter
Actually, BW protection is a good thing (tm). I realize that you can't get the clients setup until their domain filters through, however, this, well, it protects from users using ~/username/blah in order to lay the bw cost on you instead of them. I know, it's a cheap tactic, but people still do it.
 

Radio_Head

Well-Known Member
Verifed Vendor
Feb 15, 2002
2,048
1
343
Originally posted by AlaskanWolf
Not sure where this goes, but theres a bug after upgrading apache, i recompiled and just cant figure it out

when you go to http://sandy.thehideout.net/~wwwhost/ or even the ip/~whatever url.....

you get

511 Access Not Allowed

http://sandy.thehideout.net/~wwwhost/

Access Not Allowed from this Domain
You are attempting to access a user dir from a domain that is not owned by the user. Please correct the domain that you are attempting to use to access this url.
--------------------------------------------------------------------------------

Apache/1.3.26 Server at www.www-hosting.net Port 80



comment this lines on your httpd.conf

# LoadModule bwprotect_module libexec/mod_bwprotect.so
# AddModule mod_bwprotect.c

Hope this helps