bug-tracker
bug-tracker copied to clipboard
RainwayApp
Chromebook WebRTC Connection Failed
ChromeOS version 71.0.3578.127 (Official Build) (64-bit)
Attempting to connect to play.rainway.com results in "WebRTC Connection Failed". This connection has a desktop running Rainway and another desktop running the latest build of Chrome on Windows 10 Pro had no issue connecting to the gaming desktop to stream games. Android phones also have the same issue on this network (and via 4G cellular).
Please advise.
I am having the Exact Same Problem On a Chromebook It was working for a bit and now there is just the WebRTC Connection Failed.
Also having this issue, only Opera client works, Chrome and Chromium get that error. Edit: Opera stopped working as well... Tried both Windows and Linux clients.
Is there a way to debug this? I tried HTTPS Decrypt MITM in Fiddler but that caused Connection lost. My NAT type is Full Cone at both ends. Also tried disabling firewall server-side.
Connection issues over the last few days were caused by hardware outages on our infrastructure. Those were resolved as of last night and you need to restart Rainway.
Connection issues over the last few days were caused by hardware outages on our infrastructure. Those were resolved as of last night and you need to restart Rainway.
I was trying it today for the first time, fresh install. I restarted Rainway at least 3 times in the process too. As of now it still does not work. And those people before wrote months ago.
Teamviewer works fine, but is slow and choppy. I'm sad because when Rainway worked for me it worked great (for the hour or so), unlike TW.
WebRTC not working can be caused by a number of things:
- You might have a browser extension blocking it. Try running Chrome in Incognito and disabling any browser extensions to see if you can connect.
- You might need to port forward (see here)
- There could be an issue still with your Dashboard not registering properly. If you delete the Rainway folder from AppData this will reset it.
It started working for me again, what i did was boot the Windows host physically instead of running it in a VM. But now it works in the VM as well. Maybe just needed a reboot; strange. Not sure how related this is to other people's issues in this thread though.