Self Host n8n “Credentials” Couldn’t connect

Describe the problem/error/question

Could’t connect n8n API in n8n

Information on your n8n setup

  • **n8n version: 1.6.1
  • **Database (default: SQLite): Sorry, i am not tecincal persion, I follow a youtube video to install n8n on Digital Ocean,
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • **Running n8n via : Docker
  • **Operating system: window

I have search the solution here, I have tried to added this 2 lines into something call nano docker-compose.yml. Restarted but still not working.
- N8N_BASIC_AUTH_ACTIVE=false
- N8N_AUTH_MODE=oauth2

I ask ChatGPT teach me how to add it, not sure is this correct.

Here is the setting :

version: “3.7”

services:
caddy:
image: caddy:latest
restart: unless-stopped
ports:
- “80:80”
- “443:443”
volumes:
- ${DATA_FOLDER}/caddy_data:/data
- ${DATA_FOLDER}/caddy_config:/config
- ${DATA_FOLDER}/caddy_config/Caddyfile:/etc/caddy/Caddyfile

n8n:
image: n8nio/n8n
restart: always
ports:
- 5678:5678
environment:
- N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
- N8N_PORT=5678
- N8N_PROTOCOL=https
- NODE_ENV=production
- WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/
- N8N_BASIC_AUTH_ACTIVE=false
- N8N_AUTH_MODE=oauth2
- GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
volumes:
- ${DATA_FOLDER}/local_files:/files
- ${DATA_FOLDER}/.n8n:/home/node/.n8n
volumes:
caddy_data:
external: true
caddy_config:

1 Like

Hi @shek, welcome to the community! I am sorry you’re having trouble. Which error are you seeing when clicking “More details” here?

Could it be something like “Unauthorized” suggesting you might simply be using the wrong API Key or is it something else for you?

1 Like

It take a very long time to load. Then when if click “more” , it said :

Couldn’t connect with these settings
ETIMEDOUT

thats all, there is no other error message.

Thanks

Hello @shek

Maybe a stupid question: Is it the same n8n host you want to connect to? If so for what reason? What do you want to achieve?

This sounds like it could be a problem with your networking setup (perhaps a firewall somewhere eating traffic). Perhaps you want to try using http://localhost:5678/api/v1 as your base domain so traffic from the n8n node hits your n8n instance directly?

1 Like

Thanks for responses.

I want to backup my n8n workflow into github.

Thanks it works using localhost one! thanks

1 Like

Amazing, thanks so much for confirming!

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