401 : Sorry, you are not allowed to create posts as this user

[jangirsuresh95]

I have tried the same thing mentioned in it and I am getting below error message.

the account I am using is the Administrator and I have WP BASIC Auth (https://github.com/wokamoto/wp-basic-auth) plugin installed.

{
    "data": {
        "code": "rest_cannot_create",
        "message": "Sorry, you are not allowed to create posts as this user.",
        "data": {
            "status": 401
        }
    },
    "headers": {
        "Allow": "GET"
    },
    "status": 401
}

[jangirsuresh95]

I am able to solve this problem. it was some misconfiguration in .htaccess file. I have installed "Application Passwords" plugin which indicated the problem in htaccess file.

[richplastow]

For anyone else who encounters this problem, you need to install and activate the ‘Application Passwords’ plugin and then follow the instructions given here:
https://github.com/georgestephanis/application-passwords/wiki/Basic-Authorization-Header----Missing
But you don’t need to actually set up any Application Passwords for your users.

[samdoj]

No amount of hacking the .htaccess file nor installing this plugin has the correct effect. Whenever I try to upload media with credentials that I know to be correct, I get "Sorry, you are not allowed to create posts as this user". This makes absolutely no sense as the user is me and I'm an admin.

[ManishMuttreja1]

I am getting the same problem, followed all the steps and its still failing to upload media with credentials that are correct. The error is same as @samdoj and it happens even with admin users.

[emmieandrew]

{
"code": "rest_cannot_create",
"message": "Sorry, you are not allowed to create posts as this user.",
"data": {
"status": 401
}
}

i am unable to solve this issue please help

[emmieandrew]

I am getting the same problem, followed all the steps and its still failing to upload media with credentials that are correct. The error is same as @samdoj and it happens even with admin users.

did you solve this ?

[mattcullenmeyer]

I spent hours facing the same problem and finally got it to work. The only plugin I installed was Application Passwords. I also edited the .htaccess file per the comments above. The issue I ran into was what username to use for the authorization header. I was trying to use the name assigned to the password generated through Application Passwords. In reality, you should use your actual username, which in my case is just "admin" (along with the password from Application Passwords).

[gotofritz]

I have the same issue and I cannot solve it with the free plan on wordpress.com as I cannot install plugins

This is a bug, it should just work and I shouldn't need to install plugins. Thanks

[smartm0use]

For anyone else who encounters this problem, you need to install and activate the ‘Application Passwords’ plugin and then follow the instructions given here:
https://github.com/georgestephanis/application-passwords/wiki/Basic-Authorization-Header----Missing
But you don’t need to actually set up any Application Passwords for your users.

This does the trick! Thank you.

[arunbasillal]

The original suggestion didn't work for me (On Local by Flywheel)
This worked: https://wordpress.stackexchange.com/a/310898/90061

[geniecoder]

I was facing the same issue and the problem is, I forgot to add these lines in htaccess file.

RewriteCond %{HTTP:Authorization} ^(.)
RewriteRule ^(.) - [E=HTTP_AUTHORIZATION:%1]
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

You can also check below link to know how and where to add these lines.

https://github.com/imranhsayed/react-with-wordpress/

[iDanielBH]

I had a similar problem, and my problem was that it used the "Application Passwords Name" as the username. And the normal username has to be used.

He also doubted whether to use the password with spaces or without spaces, finally it was with spaces.

[LukeV111]

I spent hours facing the same problem and finally got it to work. The only plugin I installed was Application Passwords. I also edited the .htaccess file per the comments above. The issue I ran into was what username to use for the authorization header. I was trying to use the name assigned to the password generated through Application Passwords. In reality, you should use your actual username, which in my case is just "admin" (along with the password from Application Passwords).

This is the actual answer here.

Same username, but generated Application Password.