Hello, first of all, I would like to say thank you to rasa team, what a great job you guys have done! Here I got a problem when I am using rasa and rasa X on docker, I have trained a rasa model on docker and it runs properly on my shell, at the same time I already deployed rasa X on docker (exactly the same as the rasa x docs) and I can open the UI by visiting http://127.0.0.1 , the directory of rasa x is default to etc/rasa The problem is: how to connect rasa and rasa x? We can simple input rasa x command in shell under the same directory as rasa, but not possible to do the same thing on docker, I am having this error，rasa-worker_1 | 2019-06-26 03:24:34 DEBUG rasa.core.agent - Requesting model from server http://rasa-x:5002/api/projects/default/models/tags/production … rasa-worker_1 | 2019-06-26 03:24:34 DEBUG rasa.core.agent - Model server returned 204 status code, indicating that no new model is available. Current fingerprint: 74179b6124701653511dac217a08582a rasa-worker_1 | 2019-06-26 03:24:34 DEBUG rasa.core.agent - No new model found at URL http://rasa-x:5002/api/projects/default/models/tags/production rasa-production_1 | 2019-06-26 03:24:35 DEBUG rasa.core.agent - Requesting model from server http://rasa-x:5002/api/projects/default/models/tags/production … rasa-production_1 | 2019-06-26 03:24:35 DEBUG rasa.core.agent - Model server returned 204 status code, indicating that no new model is available. Current fingerprint: 74179b6124701653511dac217a08582a rasa-production_1 | 2019-06-26 03:24:35 DEBUG rasa.core.agent - No new model found at URL http://rasa-x:5002/api/projects/default/models/tags/production How do I fix this problem？ Thank you！

if you upload a trained model, it also automatically pulls training data from the model!

The Rasa X setup already includes a Rasa instance. No need, to connect them to a separate instance. If you want to use your existing model with Rasa X (on docker), you can simply upload them through the UI.

Thank you for your reply, I have already uploaded a trained model to the UI (by using curl) and also set it as the production, Rasa X should run this model but it didn’t, there’s no model running and I can’t talk with my chatbot. The error remained the same as before, even if I tried to use curl to upload the model to http://rasa-x:5002/api/projects/default/models/tags/production , still have no idea which step was wrong.

And the model shows up in your model view and you can tag it as in production I can’t talk with my chatbot. Mhm, that could also be another error. Can you run rasa and rasa-x with --debug and post the logs here?

Hi，thanks for the help, here are the logs, rabbit_1 | Welcome to the Bitnami rabbitmq container db_1 | rasa-x_1 | INFO:apscheduler.scheduler:Scheduler started rabbit_1 | Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-rabbitmq rasa-x_1 | ERROR:pika.adapters.utils.io_services_utils:Socket failed to connect: <socket.socket fd=9, family=AddressFamily.AF_INET, type=2049, proto=6, laddr=('192.168.16.5', 53590)>; error=111 (Connection refused) duckling_1 | no port specified, defaulting to port 8000 rabbit_1 | Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-rabbitmq/issues rasa-worker_1 | 2019-06-29 05:14:38 DEBUG rasa.cli.utils - Parameter 'endpoints' not set. Using default location 'endpoints.yml' instead. db_1 | Welcome to the Bitnami postgresql container rasa-production_1 | 2019-06-29 05:14:39 DEBUG rasa.cli.utils - Parameter 'endpoints' not set. Using default location 'endpoints.yml' instead. rasa-worker_1 | 2019-06-29 05:14:39 DEBUG rasa.cli.utils - Parameter 'credentials' not set. Using default location 'credentials.yml' instead. db_1 | Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-postgresql rasa-x_1 | ERROR:pika.adapters.utils.connection_workflow:TCP Connection attempt failed: ConnectionRefusedError(111, 'Connection refused'); dest=(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('192.168.16.2', 5672)) rabbit_1 | rasa-production_1 | 2019-06-29 05:14:41 DEBUG rasa.cli.utils - Parameter 'credentials' not set. Using default location 'credentials.yml' instead. rasa-x_1 | ERROR:pika.adapters.utils.connection_workflow:AMQPConnector - reporting failure: AMQPConnectorSocketConnectError: ConnectionRefusedError(111, 'Connection refused') rabbit_1 | INFO ==> Starting rabbitmq... db_1 | Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-postgresql/issues rasa-production_1 | 2019-06-29 05:14:41 DEBUG sanic_jwt.configuration - validating provided secret rasa-worker_1 | 2019-06-29 05:14:39 DEBUG sanic_jwt.configuration - validating provided secret app_1 | INFO:rasa_sdk.endpoint:Starting action endpoint server... rasa-worker_1 | 2019-06-29 05:14:39 DEBUG sanic_jwt.configuration - validating keys (if needed) rasa-production_1 | 2019-06-29 05:14:41 DEBUG sanic_jwt.configuration - validating keys (if needed) db_1 | Send us your feedback at containers@bitnami.com nginx_1 | SSL encryption is not used since no certificates were provided. duckling_1 | Listening on http://0.0.0.0:8000 app_1 | INFO:rasa_sdk.endpoint:Action endpoint is up and running. on ('0.0.0.0', 5055) nginx_1 | >> exec docker CMD rasa-production_1 | 2019-06-29 05:14:41 DE…

mhm, but the model is found and loaded. When the bot does not respond, what exactly is the behavior? Do see any failing network requests when you open up the developer tools when you send messages to the bot?

Hi, thank you, I think I know the reason, I am now having another problem with upload my stories file, that’s another topic, thank you very much for your help

What was the reason? :slight_smile:

I didn’t quiet understand how the rasa works in docker, I wrongly thought that there should be all the config, domain, nlu, stories files in the etc/rasa folder, in fact, rasa on docker only need models and custom actions to run the production, the bot didn’t react because the pika is not working, I deleted all the images and pull again then everything works, I am now trying to train model by using rasa x, it seems I need to upload all these files by using API

Oh, that’s awesome! I am going to try it, thank you!

Hi, again, I am now having another problem when tried to connect rasa docker service with slack channel, I followed the rasa doc, started the rasa x, and config the API in slack as well as credentials.yml, my question is: what is the Request URL? I noticed there are rasa production and rasa worker use the same port, 5005, I filled with this port and it verified successfully, but there’s no reply from my server when I talk to the bot (the server didn’t receive any message), do you have any idea?

Connection between Rasa and Rasa X on docker

[Deprecated] Rasa X Community Edition

yiouyou (Zack Song) February 24, 2020, 3:05pm 19

@rookiebird I’m a Chinese, what’s your wechat?

Topic		Replies	Views
Rasa X does not connect to Production/Worker hosts [Deprecated] Rasa X Community Edition	24	5292	November 25, 2020
Not able to run rasa x [Deprecated] Rasa X Community Edition	9	1656	July 13, 2020
Error launching chatbot on docker compose [Deprecated] Rasa X Community Edition	25	2301	February 9, 2022
The inconsistant behaviors of Rasa X interactive model [Deprecated] Rasa X Community Edition	6	1114	March 10, 2020
Identical model behaving differently on Rasa VS Rasa X [Deprecated] Rasa X Community Edition	8	863	August 24, 2021

Connection between Rasa and Rasa X on docker

Related topics