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
After creating the SSL certs, I removed *.pem from .gitignore and committed the changes. Then I pushed signalmasters master branch to Heroku. Everything works smoothly and for Heroku logs I see &yet -- signal master is running at: https://localhost:33054
The issue I am having is that I am unable to connect to the signaling server. In the console of my WebRTC application, I keep seeing the following error:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://secure-meadow-12345.herokuapp.com/socket.io/?EIO=3&transport=polling&t=1523771011090-81. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
If I set Heroku NODE_ENV to development mode, I don't have this issue.
The text was updated successfully, but these errors were encountered:
I am trying to depoly signalmaster to Heroku.
After creating the SSL certs, I removed
*.pem
from.gitignore
and committed the changes. Then I pushed signalmasters master branch to Heroku. Everything works smoothly and for Heroku logs I see&yet -- signal master is running at: https://localhost:33054
The issue I am having is that I am unable to connect to the signaling server. In the console of my WebRTC application, I keep seeing the following error:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://secure-meadow-12345.herokuapp.com/socket.io/?EIO=3&transport=polling&t=1523771011090-81. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
If I set Heroku NODE_ENV to development mode, I don't have this issue.
The text was updated successfully, but these errors were encountered: