[SOLVED] redirect=AdminDashboard can't reach BackOffice at all !

[clpadmin]

Hey !

 

I'be made a post in french topics, but not a single answer nor advice so I'll post it here in english...

I've got a weird trouble as I can not login with any version of Safari I v'e got

Prestashop versions tested : 1.4.4.1 updated to 1.5.6 / fresh 1.5.6 / fresh 1.6 ß / fresh 1.6.04 RC

 Mac OS X : 10.6.8 - Safari 5.1.7

 Mac Os X : 10.8.5 - Safari 6.1.1

As soon as I login with (Correct credentials) I'm always redirect to the login page with &redirect=AdminDashboard at the end of the url.

all the shops are on a Debain VM.

I've wipe out all my settings in Safari (cache, history, cookies, saved stuff, everything...) but for nothing.

I just can't login from any Mac with a Safri.

Firefox does log in, Iceweasel too. I'm stuck.

odly the online "production version" 1.4.4.1 has no problem.

I've had no problems at all some weeks ago. I've just suspended the VM, the waken it.
NO System Updates, no changes on the VM system, nor the shops.

I've tried to edit a cookie.php (see some tips on this very forum) on the 1.4.4.1 updated to 1.5.6 and as a result I now have a blank page... in front office and in back office. 

 

I've of course reverted the changes but no go. shop is out.
 

So I just don't understand what the trouble is...

Any advice would be greatly apreciated.

 

I'll try to install a New VM (again) and new fresh 1.6[RC] just to see.
this could be a VM trouble but I don't see what it could be as I did not changes anything on it at all.

Desesparate "developper" I am

Edited March 17, 2014 by clpadmin (see edit history)

[clpadmin]

just installed epiphany on a fresh Debian.. no GO still have the redirect AdminDashboard.

[musicmaster]

That's a famous one. It happens quite a lot as you will see when you look around in the forum. Unfortunately there is no standard solution.

 

What I understand is that until now you try to repair it on the client side. You might try on the server side instead: for example removing .htaccess or deleting the content in the cache subdirectory.

 

Some other ideas:

 - use htpps instead of http

 - hand type some specific module in the backoffice like http://www.myshop.com/myadmin/index.php?controller=AdminPreferences&token=abcdefghijklmnopqrstuvwxyz

One you are in: delete the Smarty cache.

 

Your Front Office blank page suggest that switching error debugging on might help too.

[clpadmin]

Hey MusicMaster thank a lot for those suggestions

I'll give  atry to each of them did'nt think of cheating like "calling a module" directly

I've tried to clean the cache but I'll take a second look at it.

I turn to just have finished to create a totaly fresh new VM with a Fresh 1.6.0.4 RC and I can go to the backoffice.

I blieve the culprit is on the server side, but as all the 4 tests shops are concerned this may be system wide and not prestashop side...

Anyway as they are for "dev" and I've got most of it in a git repo, I'll try to transfer my changes to the New VM,

I have to go on and I'm afraid searching culprit and cause will take me more time than start again from scratch.

As I'm stubborn and hate not understand, I'll dig on it anyway, by following your advises. and give feddabck here if I succeed or fail..

thx

[clpadmin]

ok so I tried wiping out the smarty, changing every options.

but no go.

 

As I 

- could login in production server BackOffice via Safari/webkit

- could not login in any VM shopS BackOffice on any versions either from Safari on SnowLeopard, MountainLion nor Debian

 

Suspect could only be "system wide" aka the debian itself.

 

So, once again I went to the logs and looked at apache logs and xauth.log etc...

 

Then all of a sudden it appeared  as plain as the nose on my face.

 

If you've read my 1st post then you may have noticed I said I did PAUSE the VM.

 

so as I was connecting from webkit to the BackOffice of One of the shops, I realized that the time, well  the date and time were just not godo at all on the VM - aka 21 of january 2014.

 

I did reboot the VM but stangely Time didn't update. so after setting up ntp on time/date pref on the VM, I did reboot the VM, went back to my Safari, to the login page and BAM logged in the BackOffice ...

 

SO morality is if you can't log back in a Back Office from webkit,

FIRST check date and time are correct both on server and on client or at least they are in sync!

 

Morality N°2 : it is just amazing that Gecko/firefox allowed me to log in when webkit would not. In a way that's good as I could see the shops weren't broken, but in another way I consider this as security hole, and webkit is way more ensible in cookies and such with time matching just like Kerberos can be.

 

I don't know what the max Time delay is (kerberos is 5 minutes max).

 

so Back again on my original VM and shops. 

 

So damn Happy it has been more than 2 weeks I'm getting mad with this !