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
Is the server down ? #671
Comments
I'd recommend providing the console's output for a detailed problem description. |
There is no message in the console. Here is my source code: Nothing happen at all. |
Does the peer you're trying to connect to exist? peer.on('error', function(err) {
console.log("Error: ", err);
}); |
Yes, the peer ID exist, and with the error handler i don't get anything. In the documentation, i just read "API key for the cloud PeerServer. This is not used for servers other than 0.peerjs.com." in the doc, is-it new ? Because I don't use one. I'm very confused, everything worked fine. |
Firefox sometimes give an error: In the network tab i get the 101 HTTP code. |
The public TURN server seems actually down but STUN should be OK. const Config = {
secure: true,
port: 443,
iceServers: [
{ urls: 'stun:stun.l.google.com:19302' },
{ urls: 'stun:stun1.l.google.com:19302' },
{ urls: 'stun:stun2.l.google.com:19302' },
]
};
var peer = new Peer(Config); |
Thank you, I tried but it's the same. It's a waste of time, i liked this librairie but I'll search for an alternative. |
The server seems to be unstable and/or overloaded. When trying to connect to
The aforementioned message looks like this:
|
Would the maintainers of the server consider upgrading it? I would be willing to make a one-time donation or if necessary a recurring one. |
I have the same issue. Everything was working perfectly, now all of a sudden I can't connect to the servers and keep getting: |
@lnogueir EDIT: Since 0.peerjs.com is a signaling-server and not a stun/turn-server its probably an issue with the public peerjs signaling-server |
I'll try to set it up. Thanks! EDIT: |
Would it be a good idea to provide the peerjs instance not with one, but
instead a list of servers and then select one that isn't timeouting? The
signaling Id could then also contain the signaling server URL. We could
then maintain a list of globally available servers.
…On Mon, 25 May 2020, 04:57 Lucas Nogueira, ***@***.***> wrote:
@Florrr <https://github.com/Florrr>
Setting up my own peerjs server fixed all my timeout issues and everything
is back to normal.
Again, thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#671 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALME5UNSH456EHDNAPZ7HDRTHNDHANCNFSM4NEJLYXA>
.
|
Is the server unstable again? I am working on an app that uses this library and ~16 hours ago it was working just fine, now it the connection just times out |
I doubt that that's possible, since both peers need to connect to the same signaling server. If you are choosing the signaling server (more or less) randomly, you cannot guarantee that the same server is used. @HidalgoIvan I'm not the maintainer of the server - so I don't know about the current status of the server. But since the signaling-server seems to be unstable, I'd recommend setting up your own one. As mentioned before this should be relatively cheap and easy to do. (In addition you are able to modify the server to add additional functionalities) |
Feel free to use mine, though no guarantees regarding uptime: https://peerjs.92k.de/ |
Thanks @Prior99 , but since I started making my own server this morning, I would like to finish. I installed peerjs using docker. And if I open port 9000 on my server, this is working, more or less. Problem is that it only works with the ip address, which isn't ssl, not the website address, which is. How did you manage to use peerjs.92k.de as the server address instead of the ip address? |
I instrumented a Hetzner server with ansible. You can check the configuration here: https://gitlab.com/prior99/peerjs-server The important part is using a reverse proxy that handles ssl for you. I am using caddy, as all that I need to do are two lines of confirmation. |
Hi @Prior99 , sorry to bother you, but I am utterly lost with all the things I need to learn to run my server...
It seems to work as I get an ID, but I can't get one peer to connect to another. And this was working perfectly using 0.peerjs.com, I didn't touch anything in my code. Am I creating the peer correctly? |
Peers are created correctly but you still need STUN and TURN servers. STUN are not a problem: there are many you can use free of charge. But you definitely need a TURN server (possibly your own) to make peers able to connect when they're behind a symmetrical NAT.
|
So I tried a lot of combinations and it's still not working. I'm behind a normal NAT.
And I set up the basic example with it. Can you try and see if it works for you? |
Sorry, we’ll restart it a little bit later |
You need to specify
|
I published a number of games which seem to work fine in many browsers on different platforms and in different network setups using my server. For example: |
Thanks @Prior99 , but even using secure: true, I can't get it to work. After two days of try and repeat, it appears that this isn't coming from your server. Since then, I tried with many others and the result is always the same: I manage to obtain the peer code, but nothing else. The weird thing is that everything works perfectly if I use basic setup connect to 0.peerjs.com (when the server is up...). |
The server had some problems at that time. But our processes have improved a lot since then. |
Hello,
Everything worked perfectly, but suddenly since yesterday, it doesn't work anymore. I can connect to it but messages aren't received. (I didn't touch anything)
What happened ? How to fix this ?
Thank you
The text was updated successfully, but these errors were encountered: