Cross-origin issue about peerjs-server

[zovt]

I have the same issue. Any new info?

[michelle]

Ah, sorry for the delay in answering--that's really strange. Is this Firefox only?

[zovt]

Seems so, everything worked fine in Chrome.

EDIT: I should add that I'm using node.js to set up the peerjs server using a self-signed certificate for testing purposes. I'm also using nginx to serve up the static content, but have a proxy set up for anything dynamic to pass it to nodejs. I can post my nginx.conf and both the client and server code I am using if it helps

[michelle]

Yeah, the server code would be helpful. Do you find that this still happens without nginx (just using something simple to serve statics?) Are you trying with the chat demo?

[michelle]

I've just pushed a hack that will fix CORS issues with restify. The real fix will come when we switch back to express (I really hope to find some time to do that this weekend, so in the meantime I will leave this issue open).

At the time we built the server, we chose to use restify over express because it was leaner. However, express is now much better than it was before, and has a much support than restify does, so it makes sense to switch back.

This same bug also exists on the cloud server right now, and I'll also fix that as soon as we switch over to express.

[michelle]

(Let me know if the latest patch, 0.2.7 doesn't fix this issue for you!)

[zovt]

Still no dice. Would you like me to post the server and client code?

[michelle]

Hum, that's strange. Yeah that'd be helpful. What'd also help is a dump of
the request you're sending (from the network panel equivalent in FF, I
guess!)

Michelle

On Fri, Aug 29, 2014 at 10:46 AM, Ragesalmon [email protected]
wrote:

Still no dice. Would you like me to post the server and client code?

—
Reply to this email directly or view it on GitHub
#49 (comment).

[zovt]

Sure thing. Here's the error I'm getting in firefox

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://localhost:9000/peer/peerjs/lF1J56BNg762Uu5y/1d6aecjftkt/id?i=0. This can be fixed by moving the resource to the same domain or enabling CORS.

Server Code:

var ps = new PeerServer({
    path: '/peer/',
    port: 9000,
    ssl: {
    key: fs.readFileSync('../ssl/server.key'),
    certificate: fs.readFileSync('../ssl/server.crt')
    }
});

Client code:

peer = new Peer(id, {host: 'localhost', port: 9000, path: "/peer/"});

Would you like me to post my nginx config as well?

[michelle]

Nah, that's fine. I think what'd be most helpful is the request dump--what
headers is the request sending, what's the actual method it's failing on,
etc.

Michelle

On Fri, Aug 29, 2014 at 10:57 AM, Ragesalmon [email protected]
wrote:

Sure thing. Here's the error I'm getting in firefox

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://localhost:9000/peer/peerjs/lF1J56BNg762Uu5y/1d6aecjftkt/id?i=0. This can be fixed by moving the resource to the same domain or enabling CORS.

Server Code:

var ps = new PeerServer({
path: '/peer/',
port: 9000,
ssl: {
key: fs.readFileSync('../ssl/server.key'),
certificate: fs.readFileSync('../ssl/server.crt')
}
});

Client code:

peer = new Peer(id, {host: 'localhost', port: 9000, path: "/peer/"});

Would you like me to post my nginx config as well?

—
Reply to this email directly or view it on GitHub
#49 (comment).

[zovt]

https://i.imgur.com/dAW2tDS.png

There are two requests at the bottom of the log, and neither of them have any response data. I could get the dump from chrome as well, which works.

[michelle]

Hm! But they no longer 405 as before?

Michelle

On Fri, Aug 29, 2014 at 11:18 AM, Ragesalmon [email protected]
wrote:

https://i.imgur.com/dAW2tDS.png

There are two requests at the bottom of the log, and neither of them have
any response data. I could get the dump from chrome as well, which works.

—
Reply to this email directly or view it on GitHub
#49 (comment).

[zovt]

Seems so. The only thing showing up now is the CORS issue in console

[zovt]

Just a question, have you been able to reproduce the bug on your end? If it helps, I'm using the latest firefox nightly

[michelle]

I haven't been able to reproduce, but I am on Firefox stable. I'll try
nightly :).

Michelle

On Fri, Aug 29, 2014 at 1:42 PM, Ragesalmon [email protected]
wrote:

Just a question, have you been able to reproduce the bug on your end? If
it helps, I'm using the latest firefox nightly

—
Reply to this email directly or view it on GitHub
#49 (comment).

[zovt]

Alright. I can boot up firefox stable and give it a shot.

[zovt]

Just tried it on stable, still the same error

[zovt]

I should also note that I am using socket.io with no problem, if that changes anything

[zovt]

I'm going to try using something simpler than nginx to serve the pages. Does this project work better with express or restify?

[michelle]

Did you confirm it's an nginx issue?

On Friday, August 29, 2014, Ragesalmon [email protected] wrote:

I'm going to try using something simpler than nginx to serve the pages.
Does this project work better with express or restify?

—
Reply to this email directly or view it on GitHub
#49 (comment).

Sent from Gmail Mobile

[zovt]

Not yet. I've been working all day, so I'm taking a bit of a break. I'll update as soon as I test it.

[michelle]

Thanks, that'd be amazing :). I'm just getting around to trying more things
now, too.

Michelle

On Fri, Aug 29, 2014 at 9:28 PM, Ragesalmon [email protected]
wrote:

Not yet. I've been working all day, so I'm taking a bit of a break. I'll
update as soon as I test it.

—
Reply to this email directly or view it on GitHub
#49 (comment).

[zovt]

Thanks for all your help! i really appreciate it

[zovt]

Hi! Sorry for the delay. Unfortunately, no matter what webserver we tested, we still had the issue with the CORS request.

[michelle]

We've just switched over to using Express. Hopefully this helps!

[michelle]

Also just upgraded the CORS middleware we're using.

[zovt]

Thanks! I'll check sometime this week

[peveuve]

In case you still wonder what happened, the problem is very likely that the certificate used is self-signed. In the context of a secured web page, browsers block such unsecured requests, so adding CORS response headers is useless.
Either use a real certificate, or load the called URL once in your browser so you can add a security exception and load the certificate.
I had the same issue today when switching the HTTPS in Dev, quite annoying but nothing to do with PeerJS.

[zovt]

@peveuve thanks man, seems that this was the issue <3 and thanks @michelle for working to fix it.

[fyyyyy]

Having this issue with build:0.3.13 and Firefox 35.0.1
I did not see this issue before upgrading from 0.3.9 to 0.3.13 yesterday. Happens on localhost with express server. I will look into certificates.

[bitnom]

Same issue on both Chrome and Firefox CORS header ‘Access-Control-Allow-Origin’ missing

I'm running: bin/peerjs --port 8880 --key myKey123 --path /broker

[merksam]

Guys, if I'm not mistaken you can run express version of peerjs-server and add cors package to allow cross-origin requests.

[nboulikas]

Guys, if I'm not mistaken you can run express version of peerjs-server and add cors package to allow cross-origin requests.

How?

[peerjs-bot]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.