Replies: 6 comments
-
Could you find the answer? |
Beta Was this translation helpful? Give feedback.
-
unfortunately not yet, I tried everything and had no result, usually in development we pass the port but not in production, but I still haven't found a way to do this without using a port |
Beta Was this translation helpful? Give feedback.
-
Out of curiosity, have you tried port |
Beta Was this translation helpful? Give feedback.
-
I forgot to update here. @samhirtarif suggestion fixed the problem for me. Also I figured out that if you do not pass the port parameter it also uses the |
Beta Was this translation helpful? Give feedback.
-
The port is encapsulated in the available domain, so if I pass the port it doesn't work, locally as I use localhos:port it works perfectly, but when it's in production it doesn't work |
Beta Was this translation helpful? Give feedback.
-
I'm not sure what exactly the problem is. Please note that every WebSocket/TCP connection has a port, you can not avoid setting one, and 443 is the default encrypted web port and a sane default. You can override this if you want. If you want to use the same port number as your current page, you could use something like new Peer({ port: location.port }) Could you please provide additional details to better understand your situation: your goal, your code, your server URL, and your expected outcome? |
Beta Was this translation helpful? Give feedback.
-
I'm trying to create a new Peer(), and I have a server in node.js on render.com, it happens that the render doesn't provide the port, and PeerJs adds a port automatically if you don't pass this parameter
The question is:
How do I instantiate the Peer without the port?
Beta Was this translation helpful? Give feedback.
All reactions