Client pages viewable w URL resellerdomain.com/~username ?

Technical support for webhosting Resellers, and questions which directly relate to their services.

Moderator: Admins

Post Reply
Rayg
newbie
Posts: 9
Joined: Tue Nov 04, 2003 6:02 am
Location: Brooklyn, N.Y.

Client pages viewable w URL resellerdomain.com/~username ?

Post by Rayg » Mon Nov 17, 2003 9:57 am

Can client pages be viewed using the URL resellerdomain.com/~username, where "resellerdomain.com" is my reseller main domain and "username" is the client site's user name? This works using the IP or the PColo server name, but when I tried it using my main domain name, I got:

"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."

This feature works if you use the SECOND of the two sequential IPs assigned to a reseller (123.123.123.124). If you use the first (123.123.123.123), you get the above error message. So it's as if the main domain name is only associated with the first IP in this process. Yet it is this first IP that is listed for the client sites in a WHM accounts listing.

So, I need to know if this feature can be made to work using the main reseller domain name. I also think it would be good to give a bit of info on how the two IPs work.

:?:

porcupine
Site Admin
Posts: 669
Joined: Wed Jun 12, 2002 5:57 pm
Location: Toronto, Ontario
Contact:

Re: Client pages viewable w URL resellerdomain.com/~username

Post by porcupine » Mon Nov 24, 2003 12:58 am

Rayg wrote:Can client pages be viewed using the URL resellerdomain.com/~username, where "resellerdomain.com" is my reseller main domain and "username" is the client site's user name? This works using the IP or the PColo server name, but when I tried it using my main domain name, I got:

"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."

This feature works if you use the SECOND of the two sequential IPs assigned to a reseller (123.123.123.124). If you use the first (123.123.123.123), you get the above error message. So it's as if the main domain name is only associated with the first IP in this process. Yet it is this first IP that is listed for the client sites in a WHM accounts listing.

So, I need to know if this feature can be made to work using the main reseller domain name. I also think it would be good to give a bit of info on how the two IPs work.

:?:
thats how the private shared IP addresses worked. There is no way we have in place to avoid this, you simply have to point them to the next IP address up, typically your ns2 ip address.
Myles Loosley-Millman
Priority Colo Inc.
myles@prioritycolo.com
http://www.prioritycolo.com

Rayg
newbie
Posts: 9
Joined: Tue Nov 04, 2003 6:02 am
Location: Brooklyn, N.Y.

Post by Rayg » Mon Nov 24, 2003 2:20 am

I hope I understand correctly. So, if I switch the 2 nameserver IP designations, that will do it? That is, if I take what is currently the second (NS2) nameserver's IP and assign it to the first listed nameserver (NS1), and vice versa, then the nameserver set will firstly point to the 123.123.123.124 (client-associated) IP, and resellerdomain.com/~username will then work to reach client sites?

porcupine
Site Admin
Posts: 669
Joined: Wed Jun 12, 2002 5:57 pm
Location: Toronto, Ontario
Contact:

Post by porcupine » Mon Nov 24, 2003 5:59 pm

Rayg wrote:I hope I understand correctly. So, if I switch the 2 nameserver IP designations, that will do it? That is, if I take what is currently the second (NS2) nameserver's IP and assign it to the first listed nameserver (NS1), and vice versa, then the nameserver set will firstly point to the 123.123.123.124 (client-associated) IP, and resellerdomain.com/~username will then work to reach client sites?
Nope, the sites will appear on the IP we normally provide for your NS2 IP address, it doesen't make it point to *any* hostname.
Myles Loosley-Millman
Priority Colo Inc.
myles@prioritycolo.com
http://www.prioritycolo.com

DavidLaneSystems
newbie
Posts: 8
Joined: Thu Jan 15, 2004 6:44 pm

Post by DavidLaneSystems » Sat Mar 27, 2004 1:53 pm

Dear Myles:

Same difficulty here, but still cannot access via second IP address because it is taken by another domain with SSL.

Help???

Regards,
RS

porcupine
Site Admin
Posts: 669
Joined: Wed Jun 12, 2002 5:57 pm
Location: Toronto, Ontario
Contact:

Post by porcupine » Sat Mar 27, 2004 2:04 pm

DavidLaneSystems wrote:Dear Myles:

Same difficulty here, but still cannot access via second IP address because it is taken by another domain with SSL.

Help???

Regards,
RS
Simply use the server hostname for it then :)
Myles Loosley-Millman
Priority Colo Inc.
myles@prioritycolo.com
http://www.prioritycolo.com

lipak
newbie
Posts: 10
Joined: Sat Jun 12, 2004 12:31 pm

Post by lipak » Thu Dec 22, 2005 4:28 pm

For people like me, that's:

http://wwwX.pcdc.net/~username/

instead of

123.123.123.123(+1)/~username/

Where X is the server number you are on.

Post Reply