# After upgrade (1.6.0) RASA is blocked by the browser

**URL:** <https://forum.rasa.com/t/after-upgrade-1-6-0-rasa-is-blocked-by-the-browser/23223>\
**Category:** Rasa Open Source\
**Created:** [January 8, 2020, 2:49pm UTC](https://forum.rasa.com/t/after-upgrade-1-6-0-rasa-is-blocked-by-the-browser/23223 "2020-01-08T14:49:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chatbot\_Ra](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/chatbot_ra/32/2238_2.png) [@Chatbot\_Ra](https://forum.rasa.com/u/Chatbot_Ra)\
**Post date:** [January 8, 2020, 2:49pm UTC](https://forum.rasa.com/t/after-upgrade-1-6-0-rasa-is-blocked-by-the-browser/23223/1 "2020-01-08T14:49:26Z")

</div>

Hi

I have upgraded my RASA:

Previous the following packages were installed with `pip install -r requirements_dev.txt` :

```auto
rasa==1.4.0
spacy==2.1.8
rasa-sdk==1.4.0
numpy==1.16.0
python-socketio==4.3.1
python-engineio==3.9.3
livereload
pytest==5.2.2
cx_Oracle==7.2.2
python-dateutil==2.8.0
multidict==4.6.1

```

To start the chatbot I did this:

**Terminal 1:**

```auto
rasa train 

```

**Terminal 2:**

```auto
rasa run --endpoints endpoints.yml --credentials credentials.yml

```

**Terminal 3:**

```auto
rasa run actions --actions actions

```

**Terminal 4:**

```auto
livereload

```

After all these steps the chatbot started running in my browser. Everything was working fine. However, I wanted to use the latest RASA version. Therefore I did an upgrade. _ **I installed the following packages** _:

```auto
rasa==1.6.0
spacy==2.1.8
rasa-sdk==1.6.0
numpy==1.16.0
python-socketio==4.3.1
python-engineio==3.9.3
livereload
pytest==5.2.2
cx_Oracle==7.2.2
python-dateutil==2.8.0
multidict==4.6.1
sanic==19.9.0

```

The rest of the code was kept the same. After I do `rasa train` I run terminal 1 - terminal 4 (see commands above). Now I am facing the following problems:

The browser window keeps **empty** ☹ **The bot is not starting in the browser** (Chrome & Firefox). With `ctrl+shift+i` in chrome I can see the following problems: The bot is getting blocked!

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/rasa/original/2X/8/87b73c5ea02fc6f4ef923cae0eb0a616caa1f744.png)

The **error** says:

```auto
Access to XMLHttpRequest at 
'http://localhost:5005/socket.io/?EIO=3&transport=polling&t=M-5c3RW' from
origin 'http://127.0.0.1:35729' has been blocked by CORS policy: 
No 'Access-Control-Allow-Origin' header is present on the requested resource.

```

This is my _endpoints.yml_:

```auto
action_endpoint:
  url: http://localhost:5055/webhook

```

This is my _credentials.yml_:

```auto
socketio:
  user_message_evt: user_uttered
  bot_message_evt: bot_uttered
  session_persistence: true

rest:
# # you don't need to provide anything here - this channel doesn't
# # require any credentials

rasa:
  url: "http://localhost:5002/api"

```

You have any idea how to solve it?

---

<div class="post-metadata">

**Author:** ![nbeuchat](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/nbeuchat/32/13688_2.png) [@nbeuchat](https://forum.rasa.com/u/nbeuchat)\
**Post date:** [January 8, 2020, 2:59pm UTC](https://forum.rasa.com/t/after-upgrade-1-6-0-rasa-is-blocked-by-the-browser/23223/2 "2020-01-08T14:59:46Z")

</div>

You can add `--cors "*"` to your `rasa run` command. Something like this might work `rasa run --endpoints endpoints.yml --credentials credentials.yml --cors "*"`

Maybe that solves it?

---

<div class="post-metadata">

**Author:** ![Chatbot\_Ra](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/chatbot_ra/32/2238_2.png) [@Chatbot\_Ra](https://forum.rasa.com/u/Chatbot_Ra)\
**Post date:** [January 8, 2020, 3:16pm UTC](https://forum.rasa.com/t/after-upgrade-1-6-0-rasa-is-blocked-by-the-browser/23223/3 "2020-01-08T15:16:28Z")

</div>

Sounds interesting! Thanks a lot.

I changed the command in terminal 2 to this:

```auto
rasa run --endpoints endpoints.yml --credentials credentials.yml --cors "*"

```

The rest was kept the same as mentioned in my first post.

**Bad news:**

- still no output in the browser

**Good news:**

- No error message (see figure in my first post) anymore. Instead it looks like this (in Chrome & Firefox):

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/rasa/original/2X/4/4acb804681a591df0b8f68e07a3799798458e0f0.png)

In **terminal 2** I get the following messages:

```auto
UserWarning: A message without a valid sender_id was received. This message will be ignored. 
Make sure to set a proper session id using the `session_request` socketIO event.
"A message without a valid sender_id "
Exception occurred while handling uri: unknown
NoneType: None
Exception occurred while handling uri: unknown
NoneType: None

```

---

<div class="post-metadata">

**Author:** ![nbeuchat](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/nbeuchat/32/13688_2.png) [@nbeuchat](https://forum.rasa.com/u/nbeuchat)\
**Post date:** [January 8, 2020, 3:21pm UTC](https://forum.rasa.com/t/after-upgrade-1-6-0-rasa-is-blocked-by-the-browser/23223/4 "2020-01-08T15:21:31Z")

</div>

Cool! At least one problem less 🙂

I have never used `socketio` so I can’t help much here. How were the sender\_id normally set?