ip's for accounts not working

[666]

i jus got a new server in the past few hours... i set it up for my own dns servers which should take a few days to propagate... Anyway, I added a few accounts and when I click on the ip for them in the account listings,

69.69.69.696/~accountname

it hangs for a few seconds and then goes to a dead page.


what could this be from?

[welo]

Try adding a slash to the end (ip.ad.dre.ss/~username/). That should work. Am uncertain why though.

[666]

that does not help.

BTW the ip is the virtual shared IP for accounts, not one of the servers main ip's.

[666]

i dont know if this could be the problem, but while setting up my own dns i accidentaly inputted the servers main ip (which serves as ns1) in the 'master primary server' option in the basic server setup. is that a bad thing?

[666]

well poking around i noticed in my resolver setting the local ip 127.0.0.1 and the info saying that if the main ip of the serv is gonna be the dns then thats the ip i should have there... so i changed it and im rebooting now.

this should at least correct what i did with the master primary server' incident... i think

[666]

well i rebooted the serv, and it had no effect on my problem regarding the site ip's not working. I went back to the resolver config part and noticed the same 127.0.0.1 was still there, yet in my (/etc/resolv.conf file it shows the correct ips for my name servers


i still dont get why i cant access the sites with the ip

[bamasbest]

This is what I found works for me.

1. To access an account with a dedicated ip, just enter the IP address assigned to the account:
http://111.111.111.111

2. To access any account (shared or dedicated), use the boxes primary IP address (or domainname if propogated) and append the backslash tilde backslash:

http://pri.mar.yip.add/~user/

[6x3]

Originally posted by bamasbest
This is what I found works for me.

1. To access an account with a dedicated ip, just enter the IP address assigned to the account:
http://111.111.111.111

2. To access any account (shared or dedicated), use the boxes primary IP address (or domainname if propogated) and append the backslash tilde backslash:

http://pri.mar.yip.add/~user/

i had to reregister on the fourms cuz these forums wouldnt let me see anything while i was correctly logged in.

I wanna thank you, this allowed me to reach the accounts, but only as if i was browsing the sites.. it did not prompt me to login to the cpanel for that account.

But i ask, why in the account listings does it show the virtual shared ip instead of the primary ip that works? ALso, I had setup my own dns yesterday and I guess its half working if i can access the hostname (my.site.com) as a site, cuz when I put the primary ip and the user account name after it, the url changed to my hostname with the account name after it. But if I do just the root site (site.com) it doesnt work, even tho i setup an account for it.






Also I did a dns report for the domain name i have setup for nameservers, which i also created a hosting account for....and it showed that:

FAIL All WWW IPs public Error: At least one of your WWW IPs is not a public IP. The problem IP(s) are:

WWW: FAILED

111.11.11.11 (the virtual ip, not my primary) is not a public IP
That means that some or all people trying to get to your web site will not be able to get there.

MX: FAILED

All MX IPs public Error: At least one of your MX records points to an IP address that is not a public IP. The problem IP(s) are:

111.11.111 (virtual ip) is not a public IP
Note that these IPs are not reachable, which can cause extra resource usage, slight mail delays, and possibly bounced mail.

MX: FAILED

Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site. The problem MX records are:
162.220.16.172.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0)]

Mail: FAILED

Connect to mail servers ERROR: I could not complete a connection to any of your mailservers!

mydomain.com: Timed out [Last data sent: None]

If this is a timeout problem, note that the DNS report only waits about 30 seconds for responses, so your mail may work fine in this case but you will need to use testing tools specifically designed for such situations.

[bamasbest]

[i]
I wanna thank you, this allowed me to reach the accounts, but only as if i was browsing the sites.. it did not prompt me to login to the cpanel for that account.

But i ask, why in the account listings does it show the virtual shared ip instead of the primary ip that works? ALso, I had setup my own dns yesterday and I guess its half working if i can access the hostname (my.site.com) as a site, cuz when I put the primary ip and the user account name after it, the url changed to my hostname with the account name after it. But if I do just the root site (site.com) it doesnt work, even tho i setup an account for it.


Also I did a dns report for the domain name i have setup for nameservers, which i also created a hosting account for....and it showed that: [/B]

OK. You can access a cPanel account , even with shared IP's by going to:

http://shared.orassigned.IP.address:2082

use the login/pass assigned to the user and you're cookin with gas.

As for your nameservers...

while you may have some errors as far as your entries, dnsreports.com/dnstuff.com has been kinda buggy for the past few days.

I received the same (private IP) errors, waited 20 minutes and then received an AOK report.

[6x3]

well i need to figure out why the virtual ip does not work for any account. When I do a traceroute or check at dnsreports it says there is nothing at all at the IP.

What settings / files should I look into?

[6x3]

no solution huh

[bamasbest]

Hmmm....

If your box is working, and the IP's aren't resolving to your box, you may want to check with your DC (Data Center) as they may have configured them improperly.