Getting local server HTTPS issues

Hello Everyone, I was using deployed RASA-X locally using guide. And I successfully installed the software, but the issue arise during HTTPS configuration. When I run the helm upgrade command, it return timed out message, and I think its checking port 8080.

As per my research, the main rasa-x interface is at port 80, and the port for HTTPs is 443. As it is installed in our local system, only port 443 is open externally with the external IP and domain. Other ports are only used for internal purpose.

Kindly guide me whether I need to open few other ports, if yes, then which ones.

And what if I would like to use my own paid certificates for ssl. What would be the procedure then? Kindy help me out Thanks in Advance Regards: Diksha

Hi @Zainalee

I can point you towards this part of the documentation.

And for the port there are two flags, --rasa-x-port for Rasa X and --port for the rasa server that is also deployed.

To resolve the HTTPS configuration issue with Rasa X, ensure that port 443 is open externally, as that’s the default for HTTPS. However, Rasa X might also use other internal ports, such as 5005 for the Rasa server, so verify which ports need to be open in your setup.

If you’re encountering a timeout with the helm upgrade command, check that your Kubernetes cluster is running properly, the correct ports are configured, and there’s no network issue or firewall blocking the connection.

For using your own paid SSL certificates, you’ll need to create a Kubernetes secret with the certificate and key files:

kubectl create secret tls rasa-x-tls --cert=/path/to/your/certificate.crt --key=/path/to/your/private.key

Then, update your Helm chart to reference the secret for the ingress configuration:

ingress:
  enabled: true
  hosts:
    - host: yourdomain.com
      paths:
        - /
  tls:
    - secretName: rasa-x-tls
      hosts:
        - yourdomain.com

Finally, upgrade the Helm release to apply the changes:

helm upgrade rasa-x rasa-x/rasa-x --namespace rasa

Afterward, check your domain to ensure the SSL certificate is properly applied via HTTPS.