You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the code(backend/services/mtp/ws-adapter/internal/config/config.go line 59) has prepared a port 8081 for WebSocket connections with TLS, but it seems not working in my case. I just want to make sure if oktopus supports WebSocket connections with TLS? If yes, do we need to change certain configurations to enable it?
wsTlsPort := flag.String("ws_tls_port", lookupEnvOrString("WS_TLS_PORT", ":8081"), "websocket tls server port")
Another question is that does oktopus support Notify message? When I connect a WebSocket obuspa to the controller and let the agent send Notify messages to oktopus with send_resp true, I can't see oktopus's NOTIFY_RESP to the agent, which leads to the agent continuously sending Notify messages to the controller. So I guess that oktopus doesn't support Notify yet?
Thank you very much for your precious time and your response!
The text was updated successfully, but these errors were encountered:
Hello again,
I noticed that the code(backend/services/mtp/ws-adapter/internal/config/config.go line 59) has prepared a port 8081 for WebSocket connections with TLS, but it seems not working in my case. I just want to make sure if oktopus supports WebSocket connections with TLS? If yes, do we need to change certain configurations to enable it?
wsTlsPort := flag.String("ws_tls_port", lookupEnvOrString("WS_TLS_PORT", ":8081"), "websocket tls server port")
Another question is that does oktopus support Notify message? When I connect a WebSocket obuspa to the controller and let the agent send Notify messages to oktopus with send_resp true, I can't see oktopus's NOTIFY_RESP to the agent, which leads to the agent continuously sending Notify messages to the controller. So I guess that oktopus doesn't support Notify yet?
Thank you very much for your precious time and your response!
The text was updated successfully, but these errors were encountered: