Creative Nexus, Connect, Create, Thrive All guides

“rest_not_logged_in” 401 on connect

A correct WordPress credential is rejected with 401, usually a stripped auth header.

10 min read Advanced

If connecting WordPress returns 401 rest_not_logged_in even though the username and Application Password are correct, your host is almost certainly stripping the Authorization header.

  1. 1Confirm the account is an Administrator or Editor (a Subscriber gives 403, not 401).
  2. 2Confirm the credential format is exactly username:application_password.
  3. 3If those are right, follow “Fix the WordPress REST API Authorization header” (CGIPassAuth / .htaccess / disable CDN).
  4. 4If the header is stripped at a CDN you can't disable, install the Nexus Apply secret endpoint.

Quick test: try a deliberately wrong password. If it returns the SAME rest_not_logged_in error, the header is being stripped (WordPress never sees either password).

Related guides

Fix the WordPress REST API Authorization header

The complete DIY fix when a correct credential still returns 401 “not logged in”.

Install the Nexus Apply plugin (secret endpoint)

A must-use plugin that lets fixes apply even when your host strips the auth header.

Still stuck?

We’ll get back within one business day.

Contact support