You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @timgrossmann thanks for the pointer. I found this,
The base issue was, that you will receive a CORS-Exception if you run the project locally (also on robotopia.co) using existing hub. See console of browser if you run presenter mode: http://robotopia.co/#presenter ->
No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://robotopia.co' is therefore not allowed access. The response had HTTP status code 403.
To get a easy setup to run, I thought it could be a good idea to add the hub internally.
BTW, I switched for now to https://signalhub-jccqtwhdwc.now.sh/, which works for me for the moment.
For local installation it would be cool to add possibility to start the hub internal. something like:
The text was updated successfully, but these errors were encountered: