I have several websites that have been running over a month now on a shared IP. Today, a client entered their web site address in their browser (IE 5.5, with latest service packs) and it pulled up another clients web site that was also on that shared IP. As soon as they hit reload, it went to their correct site. I have not seen this happen before. The server is RH 7.3 with apache 1.3.26 with CPANEL 5.0.0 Build 70. I have not been able to reproduce the error at my office. I am concerned about this, but I'm not sure if it's a one time fluke or what. Anyone have any thoughts on this, or have you experienced this before? Everything else seems to be running flawlessly (knock on wood).

Thanks for any input you may provide.

Originally posted by svdorr
I have several websites that have been running over a month now on a shared IP. Today, a client entered their web site address in their browser (IE 5.5, with latest service packs) and it pulled up another clients web site that was also on that shared IP. As soon as they hit reload, it went to their correct site. I have not seen this happen before. The server is RH 7.3 with apache 1.3.26 with CPANEL 5.0.0 Build 70. I have not been able to reproduce the error at my office. I am concerned about this, but I'm not sure if it's a one time fluke or what. Anyone have any thoughts on this, or have you experienced this before? Everything else seems to be running flawlessly (knock on wood).

Thanks for any input you may provide.

i've seen it happen on cpanel servers where the httpd.conf gets a little screwy....usually fixed right away (i think after the nameservers service gets restarted)

Typically the only cause for this is cache problems. Does the user have a cache running somewhere?

Netware's proxy server is known for not being compatible with RFC's (all of their software for that matter...) and often ignores "Host:" headers.

When you use shared IP's the only way the server knows which site to send you is through the host: header, which IE5.5 is sending (really old browsers don't send it) - but the proxy is too old to know about Host: headers.

The latest release of Netware's proxy server does not fix this. Warning: I am extremly biased against Novell and Netware. Extremely. Maybe its a different proxy server software package that is caching the pages and not interpreting host: headers.


At any rate - if they hit refresh and it STILL doesnt fix the problem, add "?asdf " to the end of your url:

webhostingtalk.com/?asdf

This makes the proxy think its a CGI page and it doesn't cache it because of the query-string's existance.

Akash:

Not to say your post is incorrect, but a nameserver restart has nothing to do with a caching problem on totally different systems, especially when the nameserver sends the same IP out for everyone anyway.

Perhaps there is a problem with Cpanel - I don't know - I only use cpanel software built in house as we can pack a lot more options and usability into the Control Panel than with stock control panels.

Originally posted by refcom
Akash:

Not to say your post is incorrect, but a nameserver restart has nothing to do with a caching problem on totally different systems, especially when the nameserver sends the same IP out for everyone anyway.

Perhaps there is a problem with Cpanel - I don't know - I only use cpanel software built in house as we can pack a lot more options and usability into the Control Panel than with stock control panels.

i am probably wrong...just saying that i've seen it before and the conditions i've seen it under..

There was a bug in the latest cpanel build. I believe it is fixed (or at least a patch is available) now.

Thank you everyone for your feedback. I have made sure that everything is patched to the latest version. I'm going to go forward with the idea that it was just a fluke, and keep a close eye on it. If anyone else has some thoughts on this problem, please let me know.

Thanks.

what refcom said it probably the reason..
i setup a virtual site the other day and it pointed to my main site for some reason, but after everything rehashed it was fine :)
- Ross

Upgrade to build 76

for those who've checked WHM in the past 24 hours it seems Nick's been pretty darn busy. No doubt if you had an issue it was due to the pretty large update that went through. As always however, if an issue arises, it's generally taken care of pretty quick :)

Greg Moorew

Yes :D, Every hour theirs an update. Good to see a new version of Phpmyadmin finally.