Websocket TLS handshake error EOF

[game5413]

Hello, currently i'm trying to setup nats websocket with tls based example configuration on this reference on my local environment, tls that i'm use was self signing certificate from mkcert, then mounting them into docker container alongside with my nats server configuration.

nats-server.conf

# Client port of 4222 on all interfaces
port: 4222

# HTTP monitoring port
monitor_port: 8222

authorization {
	default_permissions: {
		publish: "SANDBOX.*"
		subscribe: ["PUBLIC.>", "_INBOX.>"]
	}
	ADMIN: {
		publish: ">"
		subscribe: ">"
	}
	WS_USER: {
		publish: ["cmd.req", "_INBOX.>"]
		subscribe: ["notifications.*", "_INBOX.>"]
	}
	users: [
		{ user: admin, password: "admin", permissions: $ADMIN, allowed_connection_types: ["STANDARD"] }
		{ user: user, pass: "user", permissions: $WS_USER, allowed_connection_types: ["WEBSOCKET"] }
	]
	timeout: 15.0
}

# This is for clustering multiple servers together.
cluster {
  name: "executive-nats-cluster"

  port: 6222

  authorization {
    user: "cUser"
    password: "cPassword"
    timeout: 2
  }

  routes = []
}

websocket {
    port: 6969

    tls {
          cert_file: "/etc/nats/mkcert-server-cert.pem"
          key_file: "/etc/nats/mkcert-server-key.pem"
    }

    authorization {
		timeout: 3.0
    }
}

With config above, i'm tried connecting to websocket using nats.ws as client, with example code like below, and got an error message unknown error

after that, i'm checking container logs on docker and see an error logs that say TLS handshake error EOF like on picture below

Is there something wrong with SSL Certificate or Nats server configuration ?

Environment:

• Windows 10 Pro 21H2
• WSL2
• Docker Desktop

[kozlovic]

I suggest that we close this discussion since I see that you have reported an issue in nats.ws repo, and mention that you can connect using the nats.go client, so looks more like a library issue?

[game5413]

Yeah, it seem issue from the library, thanks for your response.