WPIntell

Source evidence

Status Code Error: 401 when creating a connection

Make Connector · support · 2025-09-24T09:42:00+00:00

complaintsentiment
highseverity
0.8relevance
6replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 33 rows with source links

12.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
bunitas unresolved
After updating to the new version, I can’t connect WordPress to Make. I tried on two installations. I get the following error: Status Code Error: 401. I enable the plugin by default. Previously, all I had to do was enable it, copy the API, and it worked. Could you confirm what version of the connector you’re using. as well as any relevant screenshots? Same issue here. Running the latest version of the plugin. Is this related to this issue: https://wordpress.org/support/topic/bad-practice-5/ ? It states that This plugin uses it’s own alternative authentication method for the WP-JSON API instead of the native application passwords provided by core WP […] After examining the code a bit further to find out why the authentication always returned a 401 in our setup, we’ve discovered it tries to login and run it’s code as the first (random) administrator account it can find in the database. I find this quite preoccupying. I would love clarification on this, @davidgurr . I don’t believe so. We’re continuing to investigate. Apologies for the delay – it took a while to find a way to reproduce the issue. We’ve just pushed a fix live in the WordPress app. This doesn’t require a new version of the Make plugin for WordPress – it should just work. Could those of you with the problem please try again and report back here? CORRECTION – I jumped the gun a little. The fix isn’t yet live – please watch this thread for news. This reply was modified 7 months, 1 week ago by davidgurr . Reason: Not yet live The fix should now be live. If you can, please try again and let me know your results. Contrary to the previous message, you WILL need to install the a new version of the plugin, v1.6.5 This reply was modified 7 months, 1 week ago by davidgurr . Reason: Need to install new plugin version

Comments

6 shown
davidgurr 2025-09-25T07:35:00+00:00

Could you confirm what version of the connector you’re using. as well as any relevant screenshots?

juaniglive 2025-10-01T18:36:00+00:00

Same issue here. Running the latest version of the plugin.

cargonico 2025-10-13T13:06:00+00:00

Is this related to this issue: https://wordpress.org/support/topic/bad-practice-5/ ? It states that This plugin uses it’s own alternative authentication method for the WP-JSON API instead of the native application passwords provided by core WP […] After examining the code a bit further to find out why the authentication always returned a 401 in our setup, we’ve discovered it tries to login and run it’s code as the first (random) administrator account it can find in the database. I find this quite preoccupying. I would love clarification on this, @davidgurr .

davidgurr 2025-10-14T15:28:00+00:00

I don’t believe so. We’re continuing to investigate.

davidgurr 2025-10-21T14:06:00+00:00

Apologies for the delay – it took a while to find a way to reproduce the issue. We’ve just pushed a fix live in the WordPress app. This doesn’t require a new version of the Make plugin for WordPress – it should just work. Could those of you with the problem please try again and report back here? CORRECTION – I jumped the gun a little. The fix isn’t yet live – please watch this thread for news. This reply was modified 7 months, 1 week ago by davidgurr . Reason: Not yet live

davidgurr 2025-10-23T14:03:00+00:00

The fix should now be live. If you can, please try again and let me know your results. Contrary to the previous message, you WILL need to install the a new version of the plugin, v1.6.5 This reply was modified 7 months, 1 week ago by davidgurr . Reason: Need to install new plugin version