Self Host n8n with API Login failed in the “Credentials”
Using the PlayGround is totally fine
(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)
Do you have user management enabled, or do you use basic auth?
I also had problems with my basic auth deployment
yeah , just “basic” auth to fool around to taste the drag and drop and love it
So we need user managerment to get it work?
You can probably debug it and work out what it requires… but I threw in the towel and just enabled user mgmt 
In saying that, it definitely did work a few versions ago with basic auth because that’s what both my backup workflows relied on.
Another option is to disable user management algogether and run n8n behind an auth proxy. For instance you can proxy it behind github or Azure at least until they add native Oauth support.
To get around the issue of accessing it I’m pretty sure you can expose the API using Path Prefix - though I don’t recommend doing that unless you lock down access to the API using some other method, or only use it inside your network.
Interesting Idea, may I write an other proxy api for the round trip?
Havent figure out how to debug this thing yet.
Check on Chrome Console?
That, or an intercepting reverse proxy.
It may be that some case where it’s adding a JWT Bearer as the authorization header, but ALSO trying to add/overwrite the basic auth Authorization header. So have a look at the headers sent in a normal request, then compare to a request to the API. Probably easiest to check the API explorer directly at /api/v1/docs/.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.