# Cross domain errors when current version that uses socket.io version 1.0.5

**URL:** <https://discourse.lynckia.com/t/cross-domain-errors-when-current-version-that-uses-socket-io-version-1-0-5/135>\
**Category:** Uncategorized\
**Created:** [June 18, 2014, 5:34pm UTC](https://discourse.lynckia.com/t/cross-domain-errors-when-current-version-that-uses-socket-io-version-1-0-5/135 "2014-06-18T17:34:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Wilbert\_Jackson](https://avatars.discourse-cdn.com/v4/letter/w/49beb7/32.png) [@Wilbert\_Jackson](https://discourse.lynckia.com/u/Wilbert_Jackson)\
**Post date:** [June 18, 2014, 5:34pm UTC](https://discourse.lynckia.com/t/cross-domain-errors-when-current-version-that-uses-socket-io-version-1-0-5/135/1 "2014-06-18T17:34:31Z")

</div>

We are getting the No Access-Control-Allow-Origin error when Erizo.js makes  
a call to the ErizoController.js when using the latest Licode version.  
[Socket.io](http://Socket.io) 1.0.5. has replaced 0.9.6 which we had been using without cross  
domain error problems. I have tried all sorts settings in my express based  
server application based on the new origin settings calls in [socket.io](http://socket.io)  
without any luck. Any one else having this problem and a fix.

Thanks

Wilbert Jackson

---

<div class="post-metadata">

**Author:** ![Marlin\_Cobb](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@Marlin\_Cobb](https://discourse.lynckia.com/u/Marlin_Cobb)\
**Post date:** [June 8, 2015, 7:16pm UTC](https://discourse.lynckia.com/t/cross-domain-errors-when-current-version-that-uses-socket-io-version-1-0-5/135/2 "2015-06-08T19:16:12Z")

</div>

the erizoController on the server is not compatible with [socket.io](http://socket.io) \> 1.0.

You will need to edit it and change all the io.sockects.socket ( xxxxx  
).emit  
into  
io.sockects.connected[xxxx].emit

and then force erizonController to use io sockects \> 1.0. The install  
install 0.9.6 version of [socket.io](http://socket.io).

It would be great if that could be put into the source and if the [socket.io](http://socket.io)  
could be removed from erizo.js client file. Would be much cleaner in my  
opinion.On Friday, June 5, 2015 at 4:49:22 AM UTC-4, Cracker F wrote:

> I have the same problem and no solution at the moment.  
> Do you have found out something usefull yet ?
> 
> I posted this as issue on github:  
> [Basic Example not working: Cross-Origin · Issue #303 · lynckia/licode · GitHub](https://github.com/ging/licode/issues/303)
> 
> Am Mittwoch, 18. Juni 2014 19:34:32 UTC+2 schrieb Wilbert Jackson:
> 
> > We are getting the No Access-Control-Allow-Origin error when Erizo.js  
> > makes a call to the ErizoController.js when using the latest Licode  
> > version. [Socket.io](http://Socket.io) 1.0.5. has replaced 0.9.6 which we had been using  
> > without cross domain error problems. I have tried all sorts settings in my  
> > express based server application based on the new origin settings calls in  
> > [socket.io](http://socket.io) without any luck. Any one else having this problem and a fix.
> > 
> > Thanks
> > 
> > Wilbert Jackson

---

<div class="post-metadata">

**Author:** ![Cracker\_F](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.lynckia.com/cracker_f/32/137_2.png) [@Cracker\_F](https://discourse.lynckia.com/u/Cracker_F)\
**Post date:** [June 5, 2015, 8:49am UTC](https://discourse.lynckia.com/t/cross-domain-errors-when-current-version-that-uses-socket-io-version-1-0-5/135/3 "2015-06-05T08:49:22Z")

</div>

I have the same problem and no solution at the moment.  
Do you have found out something usefull yet ?

I posted this as issue on github: [Issues · lynckia/licode · GitHub](https://github.com/ging/licode/issues/303Am) Mittwoch, 18. Juni 2014 19:34:32 UTC+2 schrieb Wilbert Jackson:

> We are getting the No Access-Control-Allow-Origin error when Erizo.js  
> makes a call to the ErizoController.js when using the latest Licode  
> version. [Socket.io](http://Socket.io) 1.0.5. has replaced 0.9.6 which we had been using  
> without cross domain error problems. I have tried all sorts settings in my  
> express based server application based on the new origin settings calls in  
> [socket.io](http://socket.io) without any luck. Any one else having this problem and a fix.
> 
> Thanks
> 
> Wilbert Jackson