View Full Version : moved server
Markos
09-02-2009, 05:13 PM
i moved server last night and i would say 95% of my users go to the new server through the url and the other 5% go to the old server through the same url how can this bee ???
Lynne
09-02-2009, 05:25 PM
The DNS probably hasn't propagated yet for some users. You should turn off the old server. Or point to the new server using the IP from the old server.
Markos
09-02-2009, 05:28 PM
thanks lynne some users get there but not showing online and cant see the chatbox and things just the main forum
--------------- Added 1251923676 at 1251923676 ---------------
im now getting this error anyone know what it is ??
https://vborg.vbsupport.ru/external/2009/09/78.jpg
Dismounted
09-03-2009, 05:53 AM
Your forum is showing fine for me. You may still be experiencing some DNS issues (incidentally, accessing it frequently makes the DNS refresh period longer).
Markos
09-03-2009, 05:59 PM
i found out why it is giving this error the amount off user access was exceeded so now i have to get a bigger server lol
snakes1100
09-03-2009, 06:09 PM
Is the server even setup/optimized right, i would travel this route before making that assumption or relying on your host for that info.
Markos
09-03-2009, 07:42 PM
it was my host who told me it was going over the max connections and im not to good with servers so i don't know if it was set up proper
snakes1100
09-04-2009, 01:40 PM
Is this a dedicated/vps server that you moved to?
If it is, then you need to optimize the server or at least set your max_connections in my.cnf to a higher number.
But the picture you posted dont indicate a db error anyways, thats a custom error page, it would be better to check your server logs and find the real issue.
Angel-Wings
09-06-2009, 02:00 PM
It's not a custom error page - your new host is running Squid as reverse caching proxy at the server sv13.bytehost.org and this reverse Proxy can't forward incoming requests to your Website.
If this problem persists and your hoster really is bytehost, would contact them about this issue. Looks like they crippled their internal access configuration
vBulletin® v3.8.12 by vBS, Copyright ©2000-2025, vBulletin Solutions Inc.