Rasa X 1.1.0: After connecting to Github, only domain.yml is seen

Rasa X Community Edition (Deprecated)
#1

Hi,

I am fairly new to Rasa and Rasa X, and am really impressed by the conversation driven developement potential of Rasa X.

However, I am facing many difficulties in getting Rasa X to work.

Currently, I am running Rasa X 1.1.0 in a Kubernetes cluster, and have successfully connected it to my remote Git repository, with the Project folders set up correctly.

However, Rasa X can only show my domain.yml file, and is unable to display the intents (nlu,.yml) or stories (stories.yml) - it’s as if it doesn’t even see the data folder!

Naturally, training fails.

Any help is appreciated.

#2

hi @Uma , this is a very common problem with Rasa X 1.1.0. For me it helped to downgrade the version tags in the different files from 3.1 to 3.0. Does this also work for you?

#3

Hi @soerenetler, thank you so much. :+1:t3:

Changing the version in the .yml files to 3.0 (down from 3.1) worked.

Now, I can see all the intents, stories and my domain.yml is consistent with the other files.

I have another problem now - my training has failed. Let me look into it, and see if I need to ask for help in the Forum again :sweat_smile:

#4

Hi @Uma,

How did you deploy Rasa X? Did you add the following line to you values.yml file?

rasa:
   versions:
     rasaProduction:
       enabled: true
     rasaWorker:
       enabled: true

This is needed to enable rasa open source. Otherwise you need to connect a separate rasa open source instance for training.

#5

Yes, I tried initially with this - it wasn’t working earlier because of the 3.1 version.

Currently, my setup includes external Rasa OSS, like below:

version: "3.1.0"
versions:
    # Disable the rasa-production deployment in order to use external Rasa OSS deployment 
    rasaProduction:
      enabled: false
        
      # Define if external Rasa OSS should be used.
      external:
        # enable external Rasa OSS
        enabled: true         
        # url of external Rasa OSS deployment
        url: "http://20.205.221.71:5005" 
      
    # Disable the rasa-worker deployment in order to use external Rasa OSS deployment 
    rasaWorker:
      enabled: false
        
      # Define if external Rasa OSS should be used.
      external:
        # enable external Rasa OSS
        enabled: true         
        # url of external Rasa OSS deployment
        url: "http://20.197.78.40:5005"

Does the version in the above also need to be changed to 3.0.x? If so, which x do you recommend?

#6

This is the error I see in Rasa X

ERROR:rasax.community.services.stack_service:401, message=‘Unauthorized’

#7

I am wondering if the tokens shouldn’t have any special characters?

#8

I tried removing the special characters from the tokens & passwords. It still doesn’t work.

My error logs on Rasa X side:

ERROR:rasax.community.services.stack_service:401, message=‘Unauthorized’, url=URL(‘http://20.197.106.75:5005/model/train?force=true&save_to_default_model_directory=true&callback_url=http://rasa-x-nlb-rasa-x.rasa-namespace.svc:5002/api/projects/default/models/jobs/1/result?token%3DXXXXXX&token=XXXXX’)

My error logs on the Rasa Training Container:

ERROR rasa.server - User is not authenticated.

Any help in resolving this is appreciated.

#9

Unfortunately I have no experience with that. I think you should write a new forum topic fot that.

#10

OK, I will. Thanks