Coda n8n connection

Describe the problem/error/question

Hello, I’m trying to connect with Coda (using n8n’s pack) but it does not work)
We’re using the self hosted version on windows

What is the error message (if any)?

Couldn’t get updates from n8n for Coda as of 5 mins ago. Try again in a few minutes or check your settings.
Failed to fetch data from n8n for Coda

Reason: unable to verify the first certificate

We have a godaddy certificate and it’s valid (in fact, I can access the domain and use n8n from another laptop, also in the api playground I have no issues, i can retrieve data with 200 response)
We’re also using nginx as reverse proxy

I don’t know what I’m doing wrong

Information on your n8n setup

  • n8n version: Version 1.36.2
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):**npm
  • Operating system: windows 11

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Hi @o_morales
Thanks for posting here and welcome to the community :partying_face:

It would be really helpful if you could share your workflow here, so we can try to reproduce the error you are getting.

You can simply share workflows here by pasting their JSON content (after you download the workflow from you workspace) in between two block quotes (```).

Also if you have any screenshots of what you are seeing, that would be good!

Thanks :slight_smile:

1 Like

Thanks!

In n8n I’m just trying to execute the curl that the n8n Public API gave me (for testing)
Here is my code:

and I noticed that if I ignore SSL it works, otherwise it shows the following error:

When I’m using the API it works
image

And in Coda I put this

and get the same error
image

This is my nginx.conf

worker_processes auto;

error_log logs/error.log;

events {
worker_connections 1024;
}

http {
server {
listen 82;
server_name n1nl.gcien.com www.n1nl.gcien.com;
return 301 https://$host$request_uri;
}

server {
    listen 443 ssl;
    server_name n1nl.gcien.com www.n1nl.gcien.com;

    ssl_certificate /path/to/credentials/;
    ssl_certificate_key /path/to/credentials/;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers HIGH:!aNULL:!MD5;

    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 10m;

    ssl_stapling on;
    ssl_stapling_verify on;

    ssl_trusted_certificate /path/to/credentials/;

    location / {
        proxy_pass http://localhost:5678/;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;
        proxy_redirect off;

        error_page 500 502 503 504 /error.html;
        location = /error.html {
            root /path/to/your/error/pages;
            internal;
        }
    }

    access_log logs/access.log;
    error_log logs/error.log;
}

}

And the certificate

Thanks again for your time :smiley:

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