-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox can't establish a connection to the server at wss://localhost/peerjs?key=peerjs&id=ZNfSEBbys&token=cklszm3tnu. #239
Comments
Response headers to wss://localhost/peerjs?key=peerjs&id=ZNfSEBbys&token=5h161q1gq5m X-Powered-By: Express
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
Content-Type: application/json; charset=utf-8
Content-Length: 140
ETag: W/"8c-OP0zOSq0rX5Ungn973BP6obbpvw"
Date: Sat, 06 Mar 2021 00:50:44 GMT
Connection: keep-alive
Keep-Alive: timeout=5```
|
Request headers
|
|
Console output
|
https://localhost/peerjs responds with
|
https://localhost/peerjs/id responds with a 404 |
I've tried giving it the path /peerjs in both front and back end, but it results in identical behaviour. |
|
Which makes it look like router is taking over and not respecting app.use('/peerjs', peer); I've tried moving it up and down, but to no avail. |
With the code as it is, if I try to set the path in the front end to
/peerjs, before I get to the current error,
wss://localhost/peerjs/peerjs?key=peerjs&id=ZNfSEBbys&token=d9krdtoczq8
returns a 404
…On Sun, Mar 7, 2021 at 8:01 AM Daniel Mills ***@***.***> wrote:
It looks like you are setting the peer js path in your express app to
/peerjs but in the front end setting it to /
const peer = new Peer(
'<%- peerId %>',
{
host:'localhost',
path:'/',
port:443
}
);
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW3ORDYRBW76T3RH6Y4IH3TCMXGDANCNFSM4YWELI7Q>
.
|
If I set the path on the back end to /rtc, then the URI localhost https://localhost/peerjs/rtc/ resolves and returns the expected JSON |
The body of the 404, provided by node, is
|
I went through most of the trouble that you have and ended up with this combination not producing the error, may be it will help you to take a look at it here. |
www.js, which is what is run by npm looks like so
The front end code looks like
https://localhost/peerjs returns the expected JSON
Any attempt to hoist a peerjs connection fails.
The text was updated successfully, but these errors were encountered: