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.

Sign up for GitHub

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

Jump to bottom

Multiroom-client error - Failed to connect, connection refused, error in socket #579

Open
jjotto opened this issue Jun 12, 2022 · 4 comments
Open

Multiroom-client error - Failed to connect, connection refused, error in socket #579

jjotto opened this issue Jun 12, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@jjotto
Copy link

jjotto commented Jun 12, 2022

Device Information:
Board: Intel NUC NUC5i5MYBE
Type: Intel NUC
BalenaOS: 2.98.33
Supervisor: 14.0.3

I'm getting a series of errors that show this information in the logs. I've tried to re-install BalenaOS and Supervisor a few times and tried a few different versions.

multiroom-client [Error] (Connection) Failed to connect to host 'localhost', error: Connection refused
multiroom-client [Error] (Controller) Error: Connection refused
multiroom-client [Error] (Connection) Error in socket shutdown: Socket not connected

image

image
@jjotto jjotto added the bug Something isn't working label Jun 12, 2022
@frindaddy
Copy link

frindaddy commented Dec 9, 2022 •
edited
Loading

I am also consistently getting this error, although on a Raspberry Pi 4. I believe this results in my multiroom-client cutting in and out during Spotify play.

EDIT: I managed to fix this and the stuttering by plugging in an ethernet cable into the Pi.

@jkr442
Copy link

jkr442 commented Feb 27, 2023

I am getting the same issue on my Intel NUC. I don't have the option of ethernet where this device is to be used.

@IIxauII
Copy link

IIxauII commented Mar 3, 2023

Running into the same issue, pi zero w setup as MULTI_ROOM_CLIENT - wifi connection

@MaximUltimatum
Copy link

Googling around and delving through the forums. I think this issue should have been fixed in #466
See forum post here
Other thing to check would be make sure you don't have client device isolation enabled on the wifi network. This is easy to check in Unifi routers on the wifi settings page.

All that said, I just upgraded my network from 3's to 4's and now I'm having this issue. Will try deleting existing fleet and recreating a new one to see if that helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@MaximUltimatum @jkr442 @jjotto @IIxauII @frindaddy