Rasa version: 1.1.5
I am currently putting together a simple chat system running on an Express Node.js server, that is connected to a Rasa Server through the Socket.IO channel.
Everything works wonderfully until I package the whole thing into Docker Containers with Docker Compose.
I have enabled CORS on the Rasa Server with the RUN command as follows:
command: run --enable-api --cors * --debug
Access to XMLHttpRequest from origin has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header contains multiple values, but only one is allowed.
The header clearly has two of the same IP address as the allowed origin in the response header.
Attempted solutions that did NOT work:
- whitelist just the Node.js server’s IP address
- tried the cors package for Express
- tried the orgins method in the Socket.IO server API
- changed all IP’s to localhost
- Suggested command from JiteshGaikwad:
rasa run -m models --enable-api --cors “*” --debug
Where does Access-Control-Allow-Origin actually get created?
Added JiteshGaikwad’s suggested solution to the ‘Did not work’ list and some minor formating.