ceffylau Posted December 24, 2016 Share Posted December 24, 2016 Every time I try to log into the back office it accepts my password and says it is redirecting to the dashboard, but it just shows the log in page again. Only way I can get in is by turning debug mode on. I have done everything I can think of (clearing all cache and cookies etc) Any Ideas Link to comment Share on other sites More sharing options...
LieBM Posted January 9, 2017 Share Posted January 9, 2017 Try one thing: 1. put in your browser URL to your front office and push INTRO. Wait until load fully 2. Put in your browser URL to your BO puch INTRO and introduce your credentials. Try to enter. I hope you solve your issue with this steps. Best regards! Link to comment Share on other sites More sharing options...
Smart-Web Posted January 11, 2017 Share Posted January 11, 2017 (edited) I have the exact same issue, fresh install ( through Softaculous). I can only access BO when I enable debug. Otherwise the login page just refreshes. LieBM's solution does work for us. Update: This problem only seems to happen on installations done through Softaculous as it renames the admin folder. Will report this to the Softacuolus team... Edited January 11, 2017 by Smart-Web (see edit history) Link to comment Share on other sites More sharing options...
ceffylau Posted February 2, 2017 Author Share Posted February 2, 2017 Sorry for the delayed response, but I ended up doing that site on a manual install. However, I'm doing another one and seeing the same issue. I'm not sure if I fully understood your instructions, but I went to the front office and waited for it to fully load, then I typed in the backoffice and it still didn't work, Link to comment Share on other sites More sharing options...
ceffylau Posted February 2, 2017 Author Share Posted February 2, 2017 This did not work for my, not sure why. But yes this a Softacuolus error, just not sure how to fix it. Link to comment Share on other sites More sharing options...
fabbea Posted April 22, 2017 Share Posted April 22, 2017 (edited) Hi, I've the same problem. My version is prestashop 1.7.1 updated from 1.7.0. At the beginning I did'nt have this problem, it came suddenly... without any modifications in the core, the scripts or this sort of things... A big problem, can someone of the Prestashop team help us ? Thanks Regards Edited April 22, 2017 by fabbea (see edit history) 1 Link to comment Share on other sites More sharing options...
richo Posted April 26, 2017 Share Posted April 26, 2017 Hi, I have also the same problem since the update to Prestashop 1.7.1.1 1 Link to comment Share on other sites More sharing options...
ValentinSV Posted April 27, 2017 Share Posted April 27, 2017 Same problem, i can only log when the debug is on... somes issues ? Link to comment Share on other sites More sharing options...
Rekal007 Posted May 10, 2017 Share Posted May 10, 2017 (edited) same here, i can only log in to the backoffice if i go into Debug mode. i tried to change from HTTP tp HTTPS, then this happend. Edited May 10, 2017 by Rekal007 (see edit history) 1 Link to comment Share on other sites More sharing options...
wooowmk Posted May 17, 2017 Share Posted May 17, 2017 +1 Me after change HTTP to HTTPS in backend, only in the backend ERROR 500, but if i active Debug mode the backend works finde Link to comment Share on other sites More sharing options...
ValentinSV Posted May 17, 2017 Share Posted May 17, 2017 (edited) i updated 1.7 to 1.7.1 and this fix problem Edited May 17, 2017 by ValentinSV (see edit history) Link to comment Share on other sites More sharing options...
nomealternativo Posted May 19, 2017 Share Posted May 19, 2017 Same here, if debug mode is off, I get an error 500 when I load the backend. My PS version is already 1.7.1, it's on HTTPS and has custom backend url (www.mydomain.com/custom-name) Any idea? Link to comment Share on other sites More sharing options...
kornwaikas Posted May 29, 2017 Share Posted May 29, 2017 Same problem. Only can enter to backoffice width debug mode. Its happened me after updating custome theme. But i try to back to classic theme and the error still happened Link to comment Share on other sites More sharing options...
Trafiquant Posted June 2, 2017 Share Posted June 2, 2017 (edited) Same issue here. Edit: Seems that you need to delete the /app/cache folder. It was the solution for me. Edited June 2, 2017 by Trafiquant (see edit history) 3 Link to comment Share on other sites More sharing options...
Antoine F Posted June 2, 2017 Share Posted June 2, 2017 Hello everyone,Could you please make a new ticket on the forge to report the issue to the Product Team? Here is the dedicated link (note that you'll need to make an account on the forge to get access to this link).Thank you! Link to comment Share on other sites More sharing options...
francescR Posted July 26, 2017 Share Posted July 26, 2017 (edited) I have the same problem. i am not sure i understood LieBM UPDATE: i updated prestashop to last version and now it works ok Edited September 6, 2017 by francescR (see edit history) Link to comment Share on other sites More sharing options...
chomik Posted September 4, 2017 Share Posted September 4, 2017 Thanks Trafiquant it worked. Altough it's not the best solution I think... Link to comment Share on other sites More sharing options...
Sickboards Posted January 19, 2019 Share Posted January 19, 2019 For me the car/cache/prod folder (with contents) was missing, after copying it from another site it worked like a charm 1 Link to comment Share on other sites More sharing options...
Sharak Posted January 21, 2019 Share Posted January 21, 2019 I've installed 1.7.5.0 and the same thing still happens. In normal mode it doesn't even try to open admin site. Just goes straight to blank page and console shows error 500. And yet it shows absolutely no error when debug mode is enabled. WTF prestashop? :/ Link to comment Share on other sites More sharing options...
LieBM Posted January 21, 2019 Share Posted January 21, 2019 17 minutes ago, Sharak said: I've installed 1.7.5.0 and the same thing still happens. In normal mode it doesn't even try to open admin site. Just goes straight to blank page and console shows error 500. And yet it shows absolutely no error when debug mode is enabled. WTF prestashop? :/ Disable debug mode. Try to go into BO and when error 500 is launched, contact with your server provider telling them the time (hour and minute) when this error was launched. Ask for a log errors. They will show you the error message with details about this error 500. Then write this message here and I can help you. Best regards Link to comment Share on other sites More sharing options...
Sharak Posted January 21, 2019 Share Posted January 21, 2019 (edited) Is this normal that /var/cache/prod directory has rights 0755 (the same inside) and /var/cache/dev has 0771 and most folders inside have 0777 (except /doctrine which has 0775) and most files have 0666 (except FrontContainer.php which has 0644)? Edited January 21, 2019 by Sharak (see edit history) 1 Link to comment Share on other sites More sharing options...
Dixin Posted January 21, 2019 Share Posted January 21, 2019 5 hours ago, Sharak said: I've installed 1.7.5.0 and the same thing still happens. In normal mode it doesn't even try to open admin site. Just goes straight to blank page and console shows error 500. And yet it shows absolutely no error when debug mode is enabled. WTF prestashop? :/ Be sure that the user and user groups used to upload and to execute the website are the same (you can use ftpzilla and a little PHP script to generate a test file to check user/group). Check the logs to be sure that the paths are correct. I experienced a similar behaviour and the problem was due to rights errors on user/group and to the fact that it seems prestashop try to use cache (if files exist) even if caches have been disabled. Link to comment Share on other sites More sharing options...
Sharak Posted January 22, 2019 Share Posted January 22, 2019 I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime Link to comment Share on other sites More sharing options...
Sharak Posted January 22, 2019 Share Posted January 22, 2019 I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime. Logs don't show anything. Just that it runs normally with http code 200, then I can turn off debug mode through admin advanced settings which results in blank page and http code 500 in the log or by updating values in defines.inc.php with the same result when trying to open admin page again. Link to comment Share on other sites More sharing options...
LieBM Posted January 22, 2019 Share Posted January 22, 2019 2 hours ago, Sharak said: I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime. Logs don't show anything. Just that it runs normally with http code 200, then I can turn off debug mode through admin advanced settings which results in blank page and http code 500 in the log or by updating values in defines.inc.php with the same result when trying to open admin page again. There is some files with logs. You should check the file named error_logs Link to comment Share on other sites More sharing options...
Dixin Posted January 24, 2019 Share Posted January 24, 2019 (edited) On 1/22/2019 at 2:33 AM, Sharak said: I installed my shop localy on my computer and then uploaded to the server. Locally everything was fine. On the server I can't access admin panel unless I'm in debug mode. FO seems to work fine everytime Be aware if you tried locally with Wamp and then you are using Linux for production. The path separator (\ on windows, / on Linux) changes and the cache accesses will be all wrong. Edited January 24, 2019 by Dixin (see edit history) Link to comment Share on other sites More sharing options...
shon Posted March 23, 2019 Share Posted March 23, 2019 Same problem, has anyone found a solution? Link to comment Share on other sites More sharing options...
Sharak Posted March 25, 2019 Share Posted March 25, 2019 (edited) The problem is with permissions. 1.7.5.0 repeats old bugs (typical for presta 😣 ). It works on localhost because you have full access there, but on the server it all dependes on folders' and files' permissions and it's simply wrong. Set 755 on all folders and 644 on all files. Then delete /var/cache/ content (/dev and /prod) Edited June 6, 2019 by Sharak (see edit history) 1 4 Link to comment Share on other sites More sharing options...
AlexFL Posted March 29, 2019 Share Posted March 29, 2019 I delete /dev and /prod in /var/cache/ and it worked. 1 Link to comment Share on other sites More sharing options...
shon Posted March 29, 2019 Share Posted March 29, 2019 On 3/25/2019 at 11:48 PM, Sharak said: The problem is with permissions. 1.7.5.0 repeats old bugs (typical for presta 😣 ). It works on localhost because you have full access there, but on the server it all dependes on folders' and files' permissions and it's simply wrong. Set 755 on all folders and 644 on all files. Thene delete /var/cache/ content (/dev and /prod) Thanks for the reply. I had already solved deleting / var / cache / content (/ dev and / prod). I had read this in another discussion and it was enough to solve. As for file and folder permissions, I had also read about these but when I tried to change those in the files something stopped working, so I put them back as they were by default. It is not clear to me what they refer to. Link to comment Share on other sites More sharing options...
tikrashobis Posted June 6, 2019 Share Posted June 6, 2019 On 3/26/2019 at 12:48 AM, Sharak said: Thanks, now work, only need delete /var/cache/ content (/dev and /prod) Link to comment Share on other sites More sharing options...
Ionut Chiriac Posted September 20, 2019 Share Posted September 20, 2019 On 6/7/2019 at 1:05 AM, tikrashobis said: Thanks! Deleting /var/cache/ worked for me too Link to comment Share on other sites More sharing options...
PrestaUserr Posted January 24, 2020 Share Posted January 24, 2020 Hello, I deleted contents of var/cache/prod folder and it worked. It generates them again, but this time correctly. 1 Link to comment Share on other sites More sharing options...
LieBM Posted January 24, 2020 Share Posted January 24, 2020 Hi, we talk about this issue in the following post:https://www.liewebs.com/en/prestashop-en/prestashop-error-500-or-blank-page-when-accessing-the-back-office/ Also we have develop a little script free to download to clean deeply Prestashop cache and fix this issue. Best regards! Link to comment Share on other sites More sharing options...
Pierre Belin Posted January 28, 2020 Share Posted January 28, 2020 On 1/21/2019 at 6:19 PM, Sharak said: Is this normal that /var/cache/prod directory has rights 0755 (the same inside) and /var/cache/dev has 0771 and most folders inside have 0777 (except /doctrine which has 0775) and most files have 0666 (except FrontContainer.php which has 0644)? This one works perfectly well for me. Thanks ! Link to comment Share on other sites More sharing options...
neron Posted April 21, 2021 Share Posted April 21, 2021 On 3/29/2019 at 3:37 PM, AlexFL said: I delete /dev and /prod in /var/cache/ and it worked. Works for me! thanks. 1 Link to comment Share on other sites More sharing options...
MrKairo Posted April 25, 2022 Share Posted April 25, 2022 On 3/25/2019 at 7:48 PM, Sharak said: The problem is with permissions. 1.7.5.0 repeats old bugs (typical for presta 😣 ). It works on localhost because you have full access there, but on the server it all dependes on folders' and files' permissions and it's simply wrong. Set 755 on all folders and 644 on all files. Then delete /var/cache/ content (/dev and /prod) I confirm the recipe cited here..., facing the fkg problem of "only accessing in debug mode" by deleting the "\dev" and "\prod" folders from the \var\cache path this issue is solved. Many thanks to the contributor of the solution! Link to comment Share on other sites More sharing options...
malcek Posted June 13, 2022 Share Posted June 13, 2022 On 1/24/2020 at 3:51 PM, PrestaUserr said: Hello, I deleted contents of var/cache/prod folder and it worked. It generates them again, but this time correctly. It works for me also. Somehow when you hit clear cache it doesn't clean all the cache, you have to delete it manually in file manager Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now