SQL Credential

I filled credential fields with my server (SSMS 19) information but it is returning a timeout error when i try to connect, is the filling incorrect?

Server: 123.456.7.8
Database: DatabaseName (name of the database in SQL that has the tablee)
user: sql login
password: sql password
port: 1433
domain: internet domain

That credential return me this error:
Failed to connect to in 30000ms

Please someone can help me? I cant think of anything else to do

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:

Hey @enzo_botoloto,

How are you running n8n and have you configured SQL to allow the connection? Are you also using a self hosted SQL instance (Express or Full) or is it a Cloud instance of SQL on something like Azure?

Hello Jon,

I configured in SQL Configuration Manager TCP/IP in SQL Express in on-premise server (enterprise), after that i created login account and connected to database with my personal endpoint (successful conection).

Now i need to create this workflow to save Pipefy Reports in SQL but i can’t connect with credentials (even filling it out correctly, i guess)

It is a docker installation for n8n? Is the SQL port opened for n8n? Please try to tcpdump the login traffic.

I’m using Web N8N, and using the same port 1433 (already opened) that uses in SQL TCP/IP. I never hear about tcpdump, it is in N8N credential configuration?

Hey @enzo_botoloto,

If you are using n8n cloud do you have your firewall open and is the traffic from n8n cloud allowed through it?

I guess that’s the problem. I’ve thought about this, but I can’t imagine how to allow n8n traffic to pass through the firewall for web access.

Hey @enzo_botoloto,

You would need to open the firewall for the SQL port which can in some cases be dangrous if you don’t know what you are doing. It could be that running your own instance of n8n is the best approach for you.

1 Like

Can we talk in chat?

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