Hi, I am facing an issue when connecting my rasa action server to my rasa server deployment on EKS. I have deployed both the rasa server and the rasa action server and both appear to be running. When I try to access the action server from the rasa server pod, I can connect via a POST request. When I test my assistant, the assistant predicts a custom action but it does not return a response - logs show no connection. What am I missing? I have followed the instructions HERE . Helm chart configuration: rasa-action-server: external: enabled: true url: "http://rasa-action-server/webhook" accessing rasa action server from rasa server pod: $ kubectl exec -it rasa-server-588d78666-nmlsd -n dev -- curl -X POST http://rasa-action-server/webhook Defaulted container "nginx" out of: nginx, rasa-oss, download-data (init), train-initial-model (init) {"error":"Invalid body request"} Please help

Connect Rasa Action Server to a Rasa deployment - AWS EKS

stephens (Greg Stephens) March 1, 2024, 2:54am 2

You need to use the EKS service name for the action server. Did you use a helm release name of rasa-action-server and can you confirm that with kubectl?

Topic		Replies	Views
Not able to connect to action server in Kubernetes cluster Rasa Open Source	3	792	February 2, 2023
Rasa X quick installation model upload failed [Deprecated] Rasa X Community Edition	5	702	November 23, 2020
RASA deployment with Kubernets Rasa Open Source	1	478	November 17, 2020
Setting up rasa action server with helm and kubectl [Deprecated] Rasa X Community Edition	0	370	May 28, 2022
Remote Custom Action Server never responds Rasa Open Source	6	414	October 10, 2021

Connect Rasa Action Server to a Rasa deployment - AWS EKS

Related topics