moved to new server - can't log in

aartech · **moved to new server - can't log in -** 29-04-2008, 01:33 AM

Hi all,

I'm moving to a new server so I copied all my files over, and my database over to the new server. I can get to the log-in screen but when I enter my user name and password, it just goes back to the log-in screen again. same for admin or staff screen.

I thought it was a key issue so I had kayako generate a new temporariy key. But the new key is actually giving a domain error even though it was supposed to be for the new temporary IP address I'm using.

Anyone have any ideas while I'm waiting for another key in the morning, why my existing install that was copied over, is just going back to the log in screen over and over with no errors?

Thanks!

jaigupta · 29-04-2008, 01:49 AM

If you have pointed your domain to the new server and you are using your domain (not IP) to access kayako then this shouldn't be key error.

Can you give us link to your kayako and phpinfo?

aartech · 29-04-2008, 01:59 AM

[quote=jaigupta;77609]If you have pointed your domain to the new server and you are using your domain (not IP) to access kayako then this shouldn't be key error.

I am using the IP address. I got the new temporary key working fine now and I'm not getting any errors. But it just takes me back to the log-in page again and again.

jaigupta · 29-04-2008, 03:39 AM

If you are using IP address then have you replaced your domain name with your IP in config file and in settings?

aartech · 29-04-2008, 03:57 PM

Quote:

Originally Posted by jaigupta

If you are using IP address then have you replaced your domain name with your IP in config file and in settings?

Yes, I have. I do get to the log-in screen, and then it goes for a second and comes back again.

I think it's a cookie issue personally but not sure what I need to change. I've even tried amending some of the settings and have also done a fresh install to the new software, done the database upgrade, but still have the same login problem...

aartech · 30-04-2008, 02:37 AM

Well, spoke with support today and the answer was that I needed to actually clear the cookiedomain in the database manually... I had tried setting it to the new IP but apparently I needed to blank it out. Just in case someone else has this issue in the future.

**Jamie Edwards** · 30-04-2008, 07:44 AM

Thank you for sharing the resolution, and I am glad to hear it is resolved.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Moved server	]SK[	Installation & Upgrading	4	17-03-2008 05:03 PM
LiveResponse disconnects continuously.	rohmelec	SupportSuite, eSupport and LiveResponse	21	26-09-2007 08:14 AM
Syncworks installation problems	jenglish	SyncWorks	10	29-03-2007 05:01 PM
URL to connect to my server during trial	ozzee	LiveResponse Desktop Application	10	22-01-2007 03:20 PM
connection problem	inteltechs	InstaAlert	5	27-04-2006 12:23 AM

jaigupta Offline Member Posts: 75 Join Date: Apr 2008	29-04-2008, 01:49 AM If you have pointed your domain to the new server and you are using your domain (not IP) to access kayako then this shouldn't be key error. Can you give us link to your kayako and phpinfo? Jai Gupta

aartech Offline New Member Posts: 18 Join Date: Jun 2007	29-04-2008, 01:59 AM [quote=jaigupta;77609]If you have pointed your domain to the new server and you are using your domain (not IP) to access kayako then this shouldn't be key error. I am using the IP address. I got the new temporary key working fine now and I'm not getting any errors. But it just takes me back to the log-in page again and again.

jaigupta Offline Member Posts: 75 Join Date: Apr 2008	29-04-2008, 03:39 AM If you are using IP address then have you replaced your domain name with your IP in config file and in settings? Jai Gupta

aartech Offline New Member Posts: 18 Join Date: Jun 2007	30-04-2008, 02:37 AM Well, spoke with support today and the answer was that I needed to actually clear the cookiedomain in the database manually... I had tried setting it to the new IP but apparently I needed to blank it out. Just in case someone else has this issue in the future.