Florian Leitner

I wanted to create a pull request but noticed that you did the exact same thing. I've used that message for notifying peerjs that their call-participant disconnected (since I didn't...

**ERR_SSL_PROTOCOL_ERROR** - if you are using the wss:// socket, you need to provide a ssl certificate. ``` const peerServer = PeerServer({ port: 9000, ssl: { key: fs.readFileSync('/path/to/your/ssl/key/here.key'), cert: fs.readFileSync('/path/to/your/ssl/certificate/here.crt') }...

But it seems that the connection to the signaling-server has been established (since there is no error) Verify, that your signaling server is running: is a json displayed when visiting...

When changing the host from `localhost` to a public ip, you need to specify the ssl keys (see https://github.com/peers/peerjs-server for how to specify the keys. e.g Using the CLI with...

Sorry for confusing you.. I'll try to clarify: If you are using "localhost" as the host (which seems to work), no ssl certificate is needed and the `secure` property must...

Your `connect()` method seems to try to connect before the `mobilePeer` is created. Maybe try again using: ``` connect() { //this.connection = this.myPeer.connect(this.remotePeerId) this.mobilePeer = new Peer({ host: 'localhost', port:...

See [https://github.com/peers/peerjs/issues/671#issuecomment-633265565](https://github.com/peers/peerjs/issues/671#issuecomment-633265565). The public signaling server seems to by unstable at the moment. Consider setting up your own signaling-server

@natusdrew you probably need to specify the "host"-value without the `wss://` prefix. this is added automatically (`wss` or `ws` depending on the `secure`-property). If you want to connect using `wss`...