Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection refused during Nexus Operation for Internal Frontend HTTP Port (7246) #7386

Open
dran-dev opened this issue Feb 25, 2025 · 0 comments

Comments

@dran-dev
Copy link

dran-dev commented Feb 25, 2025

Expected Behavior

When attempting to use Temporal Nexus endpoints for cross-namespace communication, requests fail because the internal frontend service is not listening on the expected HTTP port (7246). This occurs despite having Nexus enabled in the configuration.

Actual Behavior

{"message":"Post \"http://10.1.251.74:7246/nexus/endpoints/4ffdb2f8-5829-47fb-9242-8c353a730b64/services/testnexusservice/test-operation?callback=http%3A%2F%2Flocalhost:%3A7243%2Fnamespaces%2Ftest-namespace%2Fnexus%2Fcallback\": dial tcp 10.1.251.74:7246: connect: connection refused","applicationFailureInfo":{"type":"CallError"}}

Steps to Reproduce the Problem

  1. created a temporal nexus endpoint for cross namespace call.
$ temporal operator nexus endpoint list
  ID                       4ffdb2f8-5829-47fb-9242-8c353a730b64
  Name                     testnexus-endpoint
  CreatedTime              <nil>
  LastModifiedTime         "2025-02-25T19:45:20.784Z"
  Target.External.URL
  Target.Worker.Namespace  test-worker-namespace
  Target.Worker.TaskQueue  test-task-queue
  Description
  1. The internal frontend pod only listens on these ports:
$ netstat -plant | grep LISTEN
tcp        0      0 127.0.0.1:7936          0.0.0.0:*               LISTEN      1/temporal-server
tcp        0      0 :::9090                 :::*                    LISTEN      1/temporal-server
tcp        0      0 :::6936                 :::*                    LISTEN      1/temporal-server
tcp        0      0 :::7236                 :::*                    LISTEN      1/temporal-server
  1. relevant config
services:
  frontend:
    rpc:
      grpcPort: 7233
      httpPort: 7243
      membershipPort: 6933
      bindOnIP: "0.0.0.0"
  internal-frontend:
    rpc:
      grpcPort: 7236
      httpPort: 7246
      membershipPort: 6936
      bindOnIP: "0.0.0.0"
  1. dynamicConfig
dynamicConfig:
  system.enableNexus: true
  component.nexusoperations.callback.endpoint.template: "http://localhost:7243/namespaces/{{.NamespaceName}}/nexus/callback"

Specifications

  • Version:
    • temporal-server - 1.26.2, 1.27.0
    • helm chart - v0.55.0, v0.56.0
  • Platform: Kubernetes

Is there additional configuration needed to enable the HTTP port (7246) on the internal frontend?
Is this a known issue with the current version?
Are there any workarounds available?

Let me know if you need any additional information to help investigate this issue.

@dran-dev dran-dev changed the title Connect refused during Nexus Operation for Internal Frontend HTTP Port (7246) Connection refused during Nexus Operation for Internal Frontend HTTP Port (7246) Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant