Hi community! I have forgotten my old Kong settings, and I cant get my WS to work thru Kong. #14767
-
|
So I had WS work thru Kong before, but I dont remember the Kong settings. I use Kong Konnect. Now we have some problems, and the only change i have done is that my WS server is now running on localhost instead of public 0.0.0.0 so localhost is now 127.0.0.1 port 5004. Under is my xcode settings for gateway and for router. I have also added my first page for the Go ws that worked before but the only change is the local 127.0.0.1 instead of nothing so it was public 0.0.0.0. Here is the settings: And the gateway } and here is also my ws server "first page" with the connection part eg. //websocket server in Go for eventdriven system. Here is my nginx settings |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hi @Jensileus, |
Beta Was this translation helpful? Give feedback.
Hi @Jensileus,
When you use 0.0.0.0 as the listening address, all packets sent to port 5004 on any network interface will be delivered to your service. However, if you listen on 127.0.0.1, only packets whose destination address is 127.0.0.1:5004 will be forwarded to your service, and 127.0.0.1 is reserved for local communication within the same host. Therefore, please ensure—based on the above explanation—that Kong and your upstream service are able to communicate with each other over the network.