Rashesh Padia

@ivanmatmati so I installed everything but for some reason request doesn't reach to demoapp pod ``` 10.244.0.1:32219 [29/Feb/2024:08:23:34.883] http haproxy-controller_default-local-service_http/SRV_1 0/0/0/0/0 404 135 - - ---- 1/1/0/0/0 0/0 "GET test.demoapp:30080/serverId...

> python3 ./script.py http://podip:podport @ivanmatmati Do I need to pass pod ip and pod port of haproxy ingress ? Sorry but I don't understand your steps I usually use minikube....

@ivanmatmati one more thing to consider when reproducing the problem. Make sure to scale HAproxy to 2 pods

same here. I can't open documents it just redirects me back to "Files" page if I try to open the document. Any solutions ?

> /lgtm cancel > > May I ask you to fix the CI? https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_security-profiles-operator/2845/pull-security-profiles-operator-verify/1921814827282468864 Sure. Let me check

> @Rash419 Please could you fix the build failure? Thanks I will check it, this weekend. sorry for the delay.

Hello everyone, I will take a look. Thank you for the reports.

Reading the issue, I think there are 2 different issues: 1. Running richdocument with dedicated coolwsd server where coolwsd is behind a endpoint for example "/coolwsd" and it can't open...

@snetAT Lets focus on fixing the richdocumentscode. I can't reproduce the problem. Can you share discovery.xml file https:///apps-writable/richdocumentscode/proxy.php?req=/hosting/discovery ? For me adminIntegratorSettings.html returns 200 with `richdocumentscode`:

Hey everyone, it looks like https://github.com/nextcloud/richdocuments/pull/4521 the patch never got backported to stable branches. I was checking on main branch so I couldn't reproduce the problem :) cc: @codewithvk