Manol Posted July 1, 2013 Share Posted July 1, 2013 Does anybody know why I get this message when trying to access the admin area? Regards. Link to comment Share on other sites More sharing options...
kongondo Posted July 1, 2013 Share Posted July 1, 2013 Sorry, am rushing somewhere...the following will answer your question http://processwire.com/talk/topic/2786-request-seems-to-be-forged/ http://processwire.com/talk/topic/1563-this-request-was-aborted-because-it-appears-to-be-forged/ http://processwire.com/talk/topic/2102-using-previous-pw-installation-as-template-for-the-next-one/ http://processwire.com/talk/topic/2763-500-error-when-visiting-the-backend/ http://processwire.com/talk/topic/3668-internal-server-error-in-admin-page/ 6 Link to comment Share on other sites More sharing options...
Manol Posted July 2, 2013 Author Share Posted July 2, 2013 Solved by creating /site/assets/sessions/ 1 Link to comment Share on other sites More sharing options...
alan Posted March 27, 2014 Share Posted March 27, 2014 Solved with 777 on the sessions folder and all contents. I seem to hit this (it feels) every time I make a site live :/ 2 Link to comment Share on other sites More sharing options...
March Posted December 2, 2014 Share Posted December 2, 2014 Thanks alanfluff for your post: Solved with 777 on the sessions folder and all contents. Oh it feels good to get Apache off the war path. 1 Link to comment Share on other sites More sharing options...
alan Posted December 3, 2014 Share Posted December 3, 2014 Welcome @March and welcome to the forum 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