Jump to content

this request was aborted because it appears to be forged

joshuag

By joshuag,
in General Support

 Share

Recommended Posts

joshuag Sr. Member

joshuag

Posted
Posted

Hi,

I just moved PW to a new server and now I can't login because I am getting the error:

"this request was aborted because it appears to be forged" when submitting the login form.

I tried changing the password and username with the API... thinking this is session related?

Any suggestions?

Thanks in advance,

Link to comment
Share on other sites
  • 3 weeks later...
ryan Hero Member

ryan

Posted
Posted
Just managed to get in by changing permissions on the assets folder to 777. Not sure how much I fancy leaving it like that but for now will have to do as putting it back down to 755 for example, I get the error message again.

Most likely Apache is running as the same user for everybody on the server, probably with a name like "nobody". So it's not going to be able to write to a directory that is only writable to you (755)... it'll only be able to read from it. If the accounts a truly jailed from one another, and one account can't manipulate the files of another (by way of Apache) then 777 should be no problem. Likewise if it's a dedicated or VPS without untrusted accounts on it, then it should be fine. It sounds like that's the only way it'll run right now, so I would set it to that and then check with the web host what they recommend for Apache-writable directory permissions, and do what they suggest. You might also inquire if you can get an suPHP environment, where Apache/PHP would run as your account--in that case, you would only need rwx to yourself (700) or writable to you and rx to others (755).

  • Like 3
Link to comment
Share on other sites
  • 1 month later...
alan Hero Member

alan

Posted
Posted

Same here: I moved a site to a safe live hosting env' and had this error.

The fix proved to be making /site/assets/ 777 and recursively applying that to all inside /site/assets/, that fixed it :) thanks posters.

  • Like 1
Link to comment
Share on other sites
Pete Hero Member

Pete

Posted
Posted

I've had two lots of hosting where I asked the host to switch it to suPHP - there are only a few minutes of downtime during the process, if that, and the permissions side of things suddenly makes infinitely more sense, so +1 to ryan.

Link to comment
Share on other sites
evanmcd Sr. Member

evanmcd

Posted
Posted

I just got this error too, but found that it persisted even after I double-checked my assets and config.php permissions.

I had installed the site using the ProcessWire Blank Profile, so figured I'd try it without that. Not sure why, but it did the trick. Removing the current install and reinsalling while sticking with the default site cleared up the issue.

  • Like 1
Link to comment
Share on other sites
  • 2 weeks later...
  • 4 weeks later...
cstevensjr Hero Member

cstevensjr

Posted
Posted

I just got this error too, but found that it persisted even after I double-checked my assets and config.php permissions.

I had installed the site using the ProcessWire Blank Profile, so figured I'd try it without that. Not sure why, but it did the trick. Removing the current install and reinsalling while sticking with the default site cleared up the issue.

I just ran into the exact same problem trying to use the Blank Profile.

Link to comment
Share on other sites
  • 4 weeks later...
Soma Hero Member

Soma

Posted
Posted

Blank profile is done using pw 2.2.0 I think so there could be the problem. However it would take u only little time creating a new one. Or just start with the default install, which is actually very nice start.

Link to comment
Share on other sites
ryan Hero Member

ryan

Posted
Posted
Is it OK to just use the default install and just delete the fields, pages and templates? Anything else that should be done?

This is perfectly fine. I think that's what most people do. Though those fields, pages and templates are the bare minimum foundation for nearly any site I build, so it's rare that they get deleted here. I guess you could say that the default profile is the blank profile for some of us. :)

  • Like 1
Link to comment
Share on other sites
  • 3 months later...
typ9 Full Member

typ9

Posted
Posted

Just managed to get in by changing permissions on the assets folder to 777. Not sure how much I fancy leaving it like that but for now will have to do as putting it back down to 755 for example, I get the error message again.

Same for me here... I don't know why that happened. Seemes to me like it has got something to do with the rights of my ftp-account - because this error popped up after I created a single ftp-account for the new pw-directory - rather than using one global ftp-account for all directories.

Anyone got a solution here? Cause I feel quite uncomfortable having site/assets/ on 777... 

Link to comment
Share on other sites
ryan Hero Member

ryan

Posted
Posted
Anyone got a solution here? Cause I feel quite uncomfortable having site/assets/ on 777... 

Is it a shared hosting account, or a dedicated/vps? If it's some kind of dedicated platform where you don't have other accounts under someone else's control, then it's not as much of a concern. But I think this is a question for your hosting provider. What's probably happening is that PHP can't write to /site/assets/. Who is listed as the directory owner? It's most likely you, which would mean that Apache is running under an account other than yours that does not have write access. I would check with your hosting provider to see what permissions they recommend for CMSs that need to have a writable directory. This can very from host to host, so it's tough for us to narrow in on it here short of trying different options (that are more secure than 777) till it works. 

  • Like 1
Link to comment
Share on other sites
  • 7 months later...
jan Jr. Member

jan

Posted
Posted

I've built a processwire website for a friend and had lots of problems with "this request was aborted because it appears to be forged" after putting it on the production server.

Now, after some weeks of searching for the problem (also at the provider...) solution was very simple and I like to share:

The Webspace on the server was full. And cause every visit creates a session (inside assets/sessions/ folder) no new session could be created (new sessions files were created, but size was zero). The result was the "forged" message. 

So perhaps this could be one more solution, if anyone else has this problem...

  • Like 5
Link to comment
Share on other sites
alan Hero Member

alan

Posted
Posted

At the risk of 'pimping about' another thread where I've touched on /sessions/, I wonder if /sessions/ can safely be excluded in migrations and if so, then seeing no sessions created in /sessions/ would have made it easier, perhaps, in this case to spot the problem. Just a thought (here's the thread where I'm seeking to find the definitive list of stuff not to copy when migrating sites, in case it's of help anytime).

Link to comment
Share on other sites
  • 8 months later...
gebeer Hero Member

gebeer

Posted
Posted

I'm experiencing this problem on a vagrant box with nfs mapped www folder.

Changing permissions of site/assets recursively and config.php to 777 doesn't help.

I checked sessions folder. a 0 byte session file gets created. But the vagrant box has plenty of space available.

I checked out brandnew dev branch, installed it and get the error on login to admin.

All other PW sites on that vagrant box have the same problem. They used to work until recently. I'm not aware of any changes to the box that could have led to this behaviour.

Any pointers to a solution would be much appreciated.

Link to comment
Share on other sites
  • 3 weeks later...

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...