I have deployed Camunda 8 self managed version via docker-compose installation method. I am using the latest 8.6.6 deployment and the Camunda Desktop Modeler 5.30.0
I am able to open the modeler and design a BPMN, but when I try to deploy the model to the zeebe cluster endpoint, “http://localhost:26500”, the Deploy Button just fades out for sometime before returning to the original blue state again. Then, no matter what how many times I click the button, its not responding. This is also the case with Start Instance operation.
What I tried:
- Removing all the cache regarding camunda in the system, uninstalling and re-installing the desktop modeler.
- Removing all the unused docker-volumes
- Checking whether the elastic search exporter is set, as suggested in some other threads.
- Redeploying Camunda. I don’t think the issue is with the version of the modeler or Camunda, since I am facing this issue for quite sometime (from Modeler version 5.27.0, if I remember)
Any supports or insights regarding the issue will be very much helpful.
Thanks in Advance.
Hi @Hariharan_B - behind the scenes, Modeler is attempting to establish a connection to Zeebe, and that is why you’re seeing the button get disabled briefly. Are you using Windows, macOS, or Linux? I think the next steps are:
- confirm you can connect to the cluster using zbctl or Postman (or similar tool that supports gRPC). If you can’t, then the issue is with your connection and/or deployment, not with Modeler.
- start Modeler from the command line, which should then pipe additional debug output to the terminal and you can see if there are any relevant errors. If there are any, you can share them here and we can figure out what’s going on!
Hi @nathan.loding , Thanks for your response.
I am using Windows are here is the logs that I got when I launched the app via terminal.
And the below one is the status check that I did for the zeebe container via Postman.
Any inference from the above that will fix my issue will be helpful.
@Hariharan_B - the actuator endpoint is a different service in your Zeebe cluster. You would want to do something simple like fetching the topology via the gRPC endpoint to test this accurately. You can do that with a tool like Postman, or using the zbctl tool.
Hi @nathan.loding
PFA the response of the Topology gRPC request
@Hariharan_B - that’s interesting, from the Postman request it looks like it should work. Do you have Identity enabled in your Docker deployment? Did you need to set any Authorization headers in Postman?
Yes, I have got Identity enabled in my deployment. And, I used Basic Auth by giving the demo/demo default credentials in order to handle this request.
