WordPress credentials not working

Describe the problem/error/question

When trying to connect a new WordPress node to my WordPress website, credentials aren’t saved. It seems that the test n8n does after inserting credential is not going through.

What is the error message (if any)?

No error, just the Save button wheel is spinning since minutes and nothing happens. Tryied multiple times.

I followed the steps in this page: WordPress credentials | n8n Docs

I created multiple Applications credentials trying to solve this problem.

Please share your workflow

Information on your n8n setup

  • n8n version: 1.38.1
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu

I made another test:

I successfully connect through curl, then copy/paste the curl command into the “Import cURL command” field of a HTTP node.
Sadly, also this was a failure. The request didn’t get through using an HTTP node. The request got timed out.

Here’s the curl command copied:
curl --user “g.lanzi:***” https://volevotutto.it/wp-json/wp/v2/users

Hey @giacomolanzi,

I have just had a quick look and I don’t get any issues when connecting from n8n to a test Wordpress 6.5.2 install using an app password.

It sounds like maybe your n8n instance can’t reach your Wordpress install at all, What happens if you use an http request node and try to get https://volevotutto.it/wp-json/wp/v2/posts without any authentication? For me I get a list of your posts back so it would be interesting to see if you get the same result.

1 Like

Hi Jon,

you’re right, it seems n8n isn’t able to reach my website at all.

How could it be possibile?
N8n is installed in a Droplet on Digital Ocean using Docker, alongside with Caddy.
I followed this guide to do this setup: Digital Ocean | n8n Docs

N8n is hosted in a third level domain of my main domain (planbproject.it). I have to notice that:

  • trying to reach volevotutto.it (different host, different domain) I got timed out
  • trying to reach planbproject.it (different host, same domain) I got an authentication error, as the n8n’s ip isn’t safe

Any idea on what I should look into to solve this situation? (mainly the one with volevotutto.it)

Also: I checked and the Droplet itself isn’t able to execute a get request with curl, so the problem should be serverside and not from n8n.

So, I fixed the problem :sunglasses: (Thanks Jon, your insight pointed me in the right direction)

It was the DigitalOcean IP that was blacklisted globally. (Veru disappointing :disappointed:)
If anyone interested, I will explain below how I did it.

Starting point

I had setup the following:

  • Droplet with Caddy + N8N containerized in docker (Following this guide: Digital Ocean | n8n Docs)
  • third level domain directed to the droplet (very important for me to use webhooks and ssl)

Create new droplet

  • Make a snapshot of the droplet
  • From the snapshot, select “create new droplet”. This will create a droplet from the snapshot you just created. everything will be the same (N8N, workflows, users, and so on).
  • From DigitalOcean, delete the domain I created
  • Create a new (third level) domain and connect it to the new droplet
  • From where you’re hosting the domain, go and change the dns record accordingly with what DO suggest to do to connect your domain.
  • Wait for the DNS to be propelry propagated
  • Enjoy the droplet with clean IP.

In the unfortunate event that the new droplet has a blasklisted IP too, try again, I guess. :sweat_smile:

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.