Kryptronic Software Support Forum

Do you have root access to your account? - If so, you could try redirecting kryptronic.com server lookups to localhost (127.0.0.1).  That should work, but it depends on whether the code has been written to allow access on failed lookup and whether the code is expecting something specific in the way of an acknowledgement from the other server.

If you want to modify the code you will find that  calls on  which, in turn, calls on the various GBU/CCP requirements through GBU or .

Otherwise, maybe simpler, temporarily stop MySQL, Bind, and Apache (or their equivalents, and with the database server first) on your existing server at some time in the small hours of the morning and test it then (with the above three stopped you should not have a lock-out problem, because a check for existing setup will return false).

Last edited by Design_Wholesale (01-15-2011 00:13:21)

No problem.  The Kryptronic server should not be a problem, either.  What is more likely to be a problem is DNS propagation. - You really need to make sure that the IP addresses for your new setup have propagated, if nothing else; otherwise you will have a time when your domain name won't be resolving because the nameservers have not yet had chance to match the new underlying IP address(es) for your domain to the domain name.

What might be a good idea, on the DNS side of things, is to add in the IP addresses for your new site to the DNS zone file for your domain on both servers and to then let the changes propagate before changing your site over, but I would speak to your new host first because getting that right can be a pain at the best of times. - Done properly, though, it will work, and you will also need to remove the old server IP address(es) once it is done.

Also, don't forget to get your new webhost to set up rDNS for your domain name (it is highly recommended if you don't want other people's mailservers regarding email from your server as junk email or spam or simply refusing to accept email from your domain) and you will require at least two IP addresses. - Multiple IP addresses are not usually required, but are essential if you are using SSL, as SSL encrypted sessions cannot share an IP address with unencrypted traffic.

Last edited by Design_Wholesale (01-18-2011 13:48:52)

I was told that when trying to work out our requirements for our current hosting. - They told us that I did not need a second IP address unless I was using SSL.  I know, too, from configuring HTTP servers (Apache and Lightpd) that you won't get HTTPS working with only the one IP address (unless that is just some issue with the software, perhaps?).

Well I will have to pass that onto our webhost. - I accepted what they said because I had already hit major problems trying to get both working on a single IP with the HTTP servers, as I said, so I had 'proof' that there was a problem with a single IP for encrypted and non-encrypted.  I will also have to investigate things further with servers, too; although I did want multiple IPs anyway (private nameservers) and room for expansion, so it is not all bad. - Thanks for making me aware of this.