Skip to content
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

Cannot add IP manually, entry form blocked behind "Searching" overlay #142

Closed
Nindaleth opened this issue Jun 13, 2021 · 4 comments
Closed

Comments

@Nindaleth
Copy link

Hello, I'd love to try the Unofficial Sonos Controller, however I'm hitting an issue right at the beginning.

Environment

  • I'm on Fedora 34 and have installed the official RPM 0.2.5 from the Releases page.
  • Here's the list of my opened ports as listed by the active firewalld:
    ports: 1025-65535/udp 1025-65535/tcp

Issue

  • getting the eternal "Searching for your Sonos system..." even though the speaker is on the same network (I can see its IP from the Android app) and my ports shouldn't be blocked by the firewall
  • tried the Developer -> Add IP manually but I only get this, I'd probably call it pop-under (see the faint window under the overlay)
  • doesn't seem like I can type into the underlying window/form
    add_ip_manually

Is there anything else I can do about this?

@pascalopitz
Copy link
Owner

pascalopitz commented Jun 14, 2021

Odd. Can you try the AppImage and check if that's acting the same?

@Nindaleth
Copy link
Author

I've tried the almost identical Fedora 34 + RPM environment that I have on my work computer within the same network - the speaker is found immediately.

The difference is that on my personal computer I'm running Mullvad (a VPN client) - there's an exception in place for local network addresses because I need to access my local NAS, phone etc. I've tried the following:

  • disconnecting the VPN and restarting Sonos Controller - fixes the issue
  • the VPN supports starting apps outside of the VPN which was verified to work as intended with other apps, doesn't help here though

I can only guess; from the observed behaviour I'd say that it's the additional network interface created by the VPN client that's causing trouble in some way.

@pascalopitz
Copy link
Owner

Possible, and very little I can do about that I think. The prompt hidden behind the loader doesn't help though. Confirmed and I'll fix that, it's a simple zindex issue.

@Nindaleth
Copy link
Author

Thanks a lot for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants