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
Right now I have this solution deployed in kubernetes (minikube with ingress activated and configured):
Backend service springboot (spring-boot-starter-websocket 3) implementing stomp over websockets deployed in minikube under a nginx ingress activated and configured
Frontend in Angular 16 deployed outside kubernetes to debug
These are my end-to-end tests and results
If I start the two services native everything works OK
If I deployed the backend service under minikube and expose the service under a proxy port-forward and the frontend native everithing works OK
If I deployed the backend service under minikube and expose the service under a nginx ingress and open a websocker connection using postman everithing works OK
If I deployed the backend service under minikube and expose the service under a nginx ingress and open the frontend native the client NOT connect with a WebSocketError like this:
client.js:285 WebSocket connection to 'ws://minikube.io/poc-backend/ws' failed:
_createWebSocket @ client.js:285
(anonymous) @ client.js:218
asyncGeneratorStep @ asyncToGenerator.js:3
_next @ asyncToGenerator.js:22
invoke @ zone.js:368
onInvoke @ core.mjs:11061
invoke @ zone.js:367
run @ zone.js:129
(anonymous) @ zone.js:1257
invokeTask @ zone.js:402
(anonymous) @ core.mjs:10735
onInvokeTask @ core.mjs:10735
invokeTask @ zone.js:401
onInvokeTask @ core.mjs:11048
invokeTask @ zone.js:401
runTask @ zone.js:173
drainMicroTaskQueue @ zone.js:581
invokeTask @ zone.js:487
ZoneTask.invoke @ zone.js:472
data.args.<computed> @ zone.js:2347
Show 20 more frames
rx-stomp.config.ts:33 Mon Oct 30 2023 12:36:51 GMT+0100 (hora estándar de Europa central) 'Connection closed to ws://minikube.io/poc-backend/ws'
rx-stomp.config.ts:33 Mon Oct 30 2023 12:36:51 GMT+0100 (hora estándar de Europa central) 'STOMP: scheduling reconnection in 500ms'
rx-stomp.config.ts:33 Mon Oct 30 2023 12:37:42 GMT+0100 (hora estándar de Europa central) 'Opening Web Socket...'
As you see only when the ingress is in the middle the back and front the connection is not established, but however using postman it works. Also I don't have any detail error to discover the origin of the error, so my question is:
This is my log from ingress controller when I can't connect to backend throw ingress
Right now I have this solution deployed in kubernetes (minikube with ingress activated and configured):
These are my end-to-end tests and results
As you see only when the ingress is in the middle the back and front the connection is not established, but however using postman it works. Also I don't have any detail error to discover the origin of the error, so my question is:
This is my log from ingress controller when I can't connect to backend throw ingress
172.23.0.1 - - [30/Oct/2023:13:06:36 +0000] "GET /poc-backend/ws HTTP/1.1" 308 164 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36" 554 0.000 [default-poc-uniovi-avib-data-projection-backend-8080] [] - - - - e48ee5984470f7686e8aabf47b3e5877
And this log is when connect from Postman correctly:
172.23.0.1 - - [30/Oct/2023:13:35:19 +0000] "GET /poc-backend/ws HTTP/1.1" 101 4 "-" "-" 234 26.471 [default-poc-uniovi-avib-data-projection-backend-8080] [] 172.17.0.4:8080 0 26.468 101 9f7600aae958e6e940767f3159a74bff
Also logs from my Springboot backend service:
How Can I obtain more errors details (follow your sample) to know exactly what happend using the kubernetes ingress controller?.
The text was updated successfully, but these errors were encountered: