Metabase URL IP

Questions
#1

I’m trying to use the metabase number, but I can’t connect, it’s just running. My doubt is if in the URL field it accepts the Public IP of my instance of the metabase.

image
image898×497 16.9 KB

#2

Hey @John_Kennedy,

The node should accept the IP and I can’t see anything to suggest it wouldn’t in the nodes code. When you try to connect is there an error?

#3

error print:

image
image885×598 26.6 KB

error message when trying to connect:

NodeApiError: UNKNOWN ERROR - check the detailed error for more information
    at RoutingNode.runNode (/usr/lib/node_modules/n8n/node_modules/n8n-workflow/src/RoutingNode.ts:220:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Workflow.runNode (/usr/lib/node_modules/n8n/node_modules/n8n-workflow/src/Workflow.ts:1341:11)
    at /usr/lib/node_modules/n8n/node_modules/n8n-core/src/WorkflowExecute.ts:949:29
#4

Hey @John_Kennedy,

So that is a fairly standard timeout message, At a guess I would say the n8n instance doesn’t have access to the host with Metabase running on it.

#5

So I have 1 instance with the n8n and another instance with the metabase, but when trying to connect with the node of the n8n using the Public IP of the metabase instance, it shows me this timeout message. I would like to know what can cause this timeout message

#6

Hey @John_Kennedy,

A timeout message can be caused if there is no reply from the other end so it could be that for some reason the n8n instance is not able to reach the IP. If it was the port we would see a connection refused message so at the moment I am thinking there might not be a route between the 2.

If you use the HTTP Request node and ask it to Get the same IP what do you see?

#7

monitoring through the chrome browser I can see these errors, but I don’t know how to solve them.

image
image955×732 37.8 KB

#8

Hey @John_Kennedy,

The connection to Metabase would be server side but that does suggest there is potentially a configuration issue.

Are you using a reverse proxy with your n8n instance?

#9

yes, I’m using it with a reverse proxy on the n8n instance, however, I’ve already looked at the entire configuration and I can’t find the possible error, I’m thinking of doing an installation via docker to see if the error remains.

#10

Hey @John_Kennedy,

Which proxy are you using? The reverse proxy will only be an issue for you connecting to the instance and not the instance talking to Metabase.

#11

I’m using reverse proxy of the n8n instance to connect to a metabase instance with a public ip, I’ve now switched to docker and the same problem continues, I don’t know what else to do.

error with docker:

NodeApiError: UNKNOWN ERROR - check the detailed error for more information
    at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:112:23)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:694:23)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:590:53
#12

Hey @John_Kennedy,

That sounds like an unusual setup but as you have the reverse proxy that you are going through to get to Metabase can you check the logs on it to see if the connection is getting that far? Did you try the HTTP Request node as well that would help confirm if this is an issue with the node or if this is what it looks like.

1 Like
#13

After many attempts to get the metabase number to work, the metabase instance had an IP geolocation block, as soon as I released the location it didn’t work. Thanks a lot for the help.

1 Like
#14

Now that is something I am going to remember for the future.

1 Like
#15

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