Scott O.

Great to hear, thanks Jean-Francois!

Hi Jean-Francois - I checked docs and SnapGPT and here is something to try: The error you're seeing is a DNS resolution failure — your client cannot resolve the hostname pa2s-sdjc-ifx0c6uynsd61asd4 to an IP address. Based on the search results, I can pinpoint the likely root cause. The URL generated for your MCP Server: pa2s-sdjc-ifx0c6uynsd61asd4/mcpserver/.../mcp ...looks like it's pointing directly to a raw Snaplex node hostname rather than a proper load balancer URL. This internal hostname is not publicly DNS-resolvable, which is why getaddrinfo ENOTFOUND is thrown. Additionally, port :8081 is atypical — production MCP Server URLs should resolve over standard HTTPS (port 443). Resolution Steps According to SnapLogic documentation, there are two prerequisites for a valid, connectable MCP Server URL:

💡 If either of these is missing, the generated URL will not be publicly accessible. Here's what you should check: Step 1 — Verify Load Balancer Configuration

Step 2 — Re-check the MCP Server URL

Not a raw node hostname with a port like :8081 Step 3 — Validate the URL Before connecting your client, test the endpoint using curl or Postman: curl -X POST https://{your-host}/mcpserver/{serverId}/mcp \ -H "Content-Type: application/json" \ -H "Authorization: Bearer your-token" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' Once the load balancer is properly configured, Manager should generate a correct public URL and the DNS resolution issue should be resolved.

Hi Satish - There are several ways to control which node or Snaplex a pipeline runs on: 1. Pipeline Configuration in Designer When you have a pipeline open in the Designer, you can select the target Snaplex directly from the Snaplex drop-down menu in the pipeline configuration. This determines where the pipeline will run. 2. Scheduled or Triggered Task Configuration When setting up a Scheduled or Triggered Task, you can specify the Snaplex on which the associated pipeline should run during task configuration. 3. Using the Pipeline Execute Snap (for Child Pipelines) When invoking a child pipeline via the Pipeline Execute Snap, you can control node execution using the "Execute On" field, which offers three options: LOCAL_NODE Runs the child pipeline on the same node as the parent pipeline. Best for performance — no network transfer. LOCAL_SNAPLEX Runs the child pipeline on any available node within the same Snaplex as the parent. SNAPLEX_WITH_PATH Runs the child pipeline on a user-specified Snaplex. A Snaplex Path field appears for you to enter the target Snaplex name. Tip: Using LOCAL_NODE is recommended for most child pipeline executions as it avoids network overhead and improves performance. 4. Using pipe.plexPath Expression You can use the pipe.plexPath expression in the Pipeline Execute Snap to dynamically ensure the child pipeline runs on the same node as the parent pipeline. Note: pipe.plexPath is not recommended for Ultra Pipelines, as sending execution to another node can be resource-intensive. 5. Dedicated Snaplex for a Project An Org/Environment admin can assign a dedicated Snaplex to a specific project by moving it from the Shared project to another project. Only pipelines within that project will have access to that Snaplex in Manager and Designer. Best Practices Summary