search

SamDel / ChromeCast-Desktop-Audio-Streamer

Stream the sound of your desktop to your Chromecast Audio device
MIT License
415 stars 30 forks source link

"Check firewall"-issue when using ProtonVPN #156

Closed Alucard712 closed 8 months ago

Alucard712 commented 8 months ago

Is there any way to get it to work while being connected to ProtonVPN?

All is fine as long Proton is not connected. I already tried to white-list ChromeCast.Desktop.AudioStreamer.exe via Split Tunneling, but that did not change anything.

Besides, https://github.com/matbee-eth/chromecast-audio-stream does work with Proton, but I am missing some features with this one :-(

Edit: I tried white-listing dotnet.exe as well, but that did not change anything, either.

SamDel commented 8 months ago

The application tries to connect to the ip of the device when you want to start streaming. When using VPN it looks for the ip on the VPN network (not the local network).

I'm not an expert there but maybe this works: https://community.spiceworks.com/how_to/113798-accessing-local-network-resources-while-using-vpn !?

Alucard712 commented 8 months ago

Hi, thanks for your reply.

Sadly, the options mentioned in the linked article are no longer available. It is 9 years old...

Instead, I brute-forced myself through all Proton settings, more or less randomly. In the end changing the protocol type to UDP did the trick, nothing else was needed. I am kind of a network-settings-noob, so I do not know why, but it does work at the moment.

EDIT: Nope, UDP does not work reliably, either :-(

SamDel commented 8 months ago

I just tried: Installed ProtonVPN with a free account, pressed 'Quick Connect' to connect to a vpn.

For me the application worked as expected after being connected to the vpn. I tested streaming (for 5 minutes during this test) and discovery. I also tried to change the protocol from Smart to OpenVPN - TCP, and to OpenVPN - UDP.

What goes wrong for you exactly? Can you post the log?

Alucard712 commented 8 months ago

Well, this makes me look rather stupid...

Yesterday I got so frustrated with this, that I stopped trying and de-installed the Streamer and reset Proton to my original settings.

I gave it another try today after I read your last post and everything worked fine right away. I have no f***ing idea what is different now and what my problems were on the first attempt.

I really (really!) hope that I keeps working, but if it fails again, I will post the log here.

SamDel commented 8 months ago

😃

Please let it know, also when it's still working in a week or two!

Alucard712 commented 8 months ago

Damn, here we go again. It stopped working yesterday and I could not recover it for now. Log file from today attached...

Log_Alucard_230116.txt

SamDel commented 8 months ago

There are two types of connections with this application:

  1. connections from the application to the devices to send control and status messages
  2. connections from the devices to the application to load the stream

For the first it looks like it works fine in the first part of the log, but at the end the connection is lost. The incoming connections from the device to load the stream fail somehow, that when you get the firewall state.

The VPN is active all the time I assume!?

Alucard712 commented 8 months ago

Correct, VPN was active all the time.

When using the Windows Spotify App all is fine even with running VPN. So, I am afraid, this issue is somewhat Streamer-specific.

I can try again to white-list certain EXEs or IPs via split-tunneling - but I need to know which ones. (As I already wrote the obvious candidates did not improve anything.)

SamDel commented 8 months ago

When using Spotify the stream is loaded from the internet, the device doesn't connect back to the application. That's easier in this case.

Have you tried to exclude the ip's 192.168.178.37 and 10.2.0.2 in the VPN?

Alucard712 commented 8 months ago

Spotify: Ah, alright, makes sense.

IPs: I tried 192.168.178.37 before with no effect, but together with 10.2.0.2 it does work at the moment - hope this was the solution. I will keep you updated. Thanks so far :-)

SamDel commented 8 months ago

In your setup the device (192.168.178.37) should connect to the application (10.2.0.2) when loading the stream, that was were it went wrong. So 10.2.0.2 should be excluded. Hope it keeps working!

Alucard712 commented 8 months ago

It is still working since white-listing 10.2.0.2. Besides, the device's own IP (..37 in my case) does not need to be white-listed.

I think we finally can regard this issue as solved.

SamDel commented 8 months ago

Nice! Thanks for letting it know. I've added a line in the wiki about it.