HighLevel OAuth2 Credentials does not appear on Docker version of n8n

Questions
, ,
1

Describe the problem/error/question

I am trying to use the new OAuth2 credentials for HighLevel, released on 1.45.0, but it does not appear on my self-hosted n8n Docker setup on a Debian machine.

I’ve tried downgrading it from 1.46.0 to 1.45.1, and it still didn’t appear.

Strangely, when I installed 1.45.1 from npm, on my Windows machine, the new HighLevel OAuth2 Credentials option appeared in there.

I haven’t tried installing the docker version on my Windows machine.

My Debian n8n installed with Docker already had some workflows using the old v1 HighLevel API, before I upgraded to the new version with this new nodes/credentials. Maybe this has something to do with it?

Here’s the available credentials for HighLevel on 1.46.0 and 1.45.1 with Docker:
image

Here’s the available credentials for HighLevel on 1.45.1 with npm:
image

If I try to copy a node using OAuth2 from the npm version to the docker version, I get this warning:

image
image842×719 19.3 KB

Information on your n8n setup

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

For some reason, when I change the subdomain of n8n from “n8n” to anything the new Credentials option appears, if I change back to “n8n” it disappears again.
I have no idea what is going on with that.

3

I found out what was happening, there seems to be a cache of some sort preventing to load the new version of the node.

Opening the website with an anonymous tab displays the new node/credentials.

I tried deleting the cache of the website and it still gives me an error for the new node/credentials on my main browser window for some reason.

1 Like
4

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