DediPlace
08-31-2003, 11:24 AM
Hi,
I just want to know why it is not possible for my new host for me to use http://www.myresellerdomain.com/~username as temporary link for my clients. I can use this to all of my previous host. But why not on this new host? Is it because this new host gave me a dedicated IP and the others did not? I think this is a good function for a more professional look.
THanks
marcustr
08-31-2003, 11:34 AM
Pwh,
The only reason I can think of is your provider has had people steal bandwidth. When you use your domain like http://www.myresellerdomain.com/~username. It doesn't count against your account but your providers account. There has been times that I have to do this also on some of our servers. I will agree it does look professional but bandwidth does cost money and if someone takes it with out paying you have to draw the line. That is my thought I am sure someone else will have something to say.
efarmer
08-31-2003, 12:58 PM
Now I know how not to pay for my Large Bandwidth Usage.
Have you tried theservername.com/~username or perhaps IP/~username
If that doesn't work you could always assign a subdomain to the account untill their domain has resolved.
DediPlace
08-31-2003, 01:39 PM
XeroMedia,
Yes, the theservername.com and ip works fine. I don't like the name of the servername, not identifiable thru me and the ip is changing to the servername when the page is loaded....
Thanks
efarmer
08-31-2003, 01:45 PM
I am sure your host would be most willing to help you out on this.
RossMAN
08-31-2003, 03:00 PM
Originally posted by efarmer
I am sure your host would be most willing to help you out on this.
Yep this is what support is for and assuming they're with a good web host who has adequate support.
I just tested this out with my dathorn resellers account and it works just fine.
thedavid
08-31-2003, 03:54 PM
The reason why this is happening is because of bandwidth leech protection being turned on for your account. This is something that is likely a 'default' with your hosting provider. To fix this, all they need to do is remove a section of the virtualhost for your domain name inside of the apache server config, and restart apache.
-David