Facing issues while running the inbound connector for NATS Jetstream

While running my Inbound connector code I am facing the issue while running the application
1. My Application properties file
server.port=9899
#outbound
camunda.client.zeebe.grpc-address=http://localhost:26500
camunda.client.zeebe.rest-address=http://localhost:8088
camunda.client.auth.type=none
#camunda.client.mode=self-managed
spring.autoconfigure.exclude=io.camunda.zeebe.spring.client.configuration.ZeebeClientStarterAutoConfiguration

#inbound properties
zeebe.client.broker.gateway-address=localhost:26500
zeebe.client.security.plaintext=true

operate.client.url=http://localhost:8080/operate
operate.client.username=demo
operate.client.password=demo
operate.client.profile=simple

#enable inbound runtime
camunda.connector.inbound.enabled= true
camunda.connector.inbound.refresh-interval=5s
#Optional logging to debug trigger registration
logging.level.io.camunda.connector=DEBUG
logging.level.io.camunda.connector.runtime.inbound=DEBUG

2 . Error that I am getting logs

scheduling-1] .c.c.r.i.e.InboundExecutableRegistryImpl : Inbound connector status report - 0 executables active
2025-08-15T17:54:01.000+05:30 ERROR 23664 — [ scheduling-1] i.c.c.r.i.i.ProcessDefinitionImporter : Failed to import process elements

java.lang.RuntimeException: Unable to authenticate

Caused by: org.apache.hc.client5.http.HttpHostConnectException: Connect to http://localhost:8081 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: getsockopt

3. POM file that I am using

Hi there! :waving_hand:

I can see you’re facing authentication and connection issues with your NATS Jetstream inbound connector. The error indicates that the connector runtime is trying to connect to localhost:8081 but getting a connection refused error.

Looking at your configuration, I notice a potential issue:

Problem Analysis

  1. Port Mismatch: Your configuration shows:

    operate.client.url=http://localhost:8080/operate
    

    But the error shows it’s trying to connect to localhost:8081.

  2. Configuration Property: For inbound connectors, you should use base-url instead of url for the Operate client configuration.

Solution

Please update your application properties file with the correct configuration:

# Replace this line:
# operate.client.url=http://localhost:8080/operate

# With these lines:
operate.client.base-url=http://localhost:8081
operate.client.username=demo
operate.client.password=demo
operate.client.profile=simple

Why This Happens

  • Port 8080: Default internal port for Operate inside the container
  • Port 8081: Commonly mapped external port for Operate in Docker/Kubernetes setups
  • base-url vs url: Inbound connectors specifically require the base-url property, not url

The ProcessDefinitionImporter needs to authenticate with Operate to import process definitions for the inbound connector to work properly.

Additional Checks

  1. Verify Operate is running: Make sure Operate is accessible at http://localhost:8081
  2. Check your Docker/Kubernetes port mappings: Confirm which port Operate is exposed on
  3. Test the connection: Try accessing http://localhost:8081 in your browser

If you’re still having issues after making these changes, please share:

  • Your complete POM file (it seems to be cut off)
  • Your Docker Compose or Kubernetes configuration
  • Which version of Camunda 8 you’re using

References:

Let me know if this resolves your issue! :rocket:

Hello @bharat3

Was @zee-bot helpful ? Let us know if you have any other issues

Mathias

Yeah the issue is resolved now