SqueezePlay: This player is already linked to another SqueezeNetwork account

**Paul Webster** · 2021-12-02, 19:33

I would expect that they can be run without needing access to mysqueezebox ... but first question ... did you edit the log or is that a MAC address that you can configured for the player?

I think that the MAC address that the player is giving mysqueezebox is already used by someone else. But it does look odd ...

If you configured it then ... unconfigure it and let your real MAC address go through ... or are you running in a VM of some sort and cannot get a real MAC address?

**Redrum** · 2021-12-02, 20:14

Disclaimer, I have no experience with squeezeplay.

I know that this doesn't address your issues, but might you consider trying/running squeezelite-x? I really like it as a "PC Player".

Maybe it would/wouldn't work that might help in your debug.

Jim

**bkerouan** · 2021-12-03, 06:05

Originally posted by Paul Webster

are you running in a VM of some sort and cannot get a real MAC address?

Yes, one of the Windows 10 instances I use to test Squeezeplay is running on a VM, nevertheless the Wireshark capture shown above is from my laptop (running Win11 Preview, that may be an issue).

The network capture clearly shows that Squeezeplay sends a MAC address that looks weird ("mac":"00:00:00:00:99:01"), although not related to the physical MAC address of my laptop network interface. Since this is an unaltered installation of Squeezeplay I'm wondering where this address comes from. I didn't take time to look at the source code to understand how the initial handshake with the server at startup is done.

**bkerouan** · 2021-12-03, 06:25

Originally posted by Redrum

might you consider trying/running squeezelite-x?

Thanks Jim, I didn't know this player. I tried it and indeed it connects to my LMS without issue, so thanks for the tip. That's a nice workaround but I'm still curious and would like to solve this Squeezeplay issue!

**Paul Webster** · 2021-12-03, 08:31

I just tried on Win10 and it worked OK.
The local LMS showed the correct reported MAC address.

If you can get in .... you could enable lots of logging (Settings/Advanced/Logging).
The logs go to
%TEMP%\stderr-SqueezePlay.txt
%TEMP%\stdout-SqueezePlay.txt

(timestamps are Unix time)

**Paul Webster** · 2021-12-03, 08:36

However, I cannot get it to login to mysqueezebox.com
I see this in the log

Code:

1638520483.092 INFO   squeezebox.server - :744 connected mysqueezebox.com
1638520483.093 INFO   applet.SlimMenus - SlimMenusApplet.lua:1323 not registered or not yet connected with SN, so not fetching SN menus. connected:true

**Paul Webster** · 2021-12-03, 08:41

I have a menu item of "Test" ... in there I can connect to mysqueezebox ... and it works

Code:

1638520753.831 WARN   net.comet - :883 Comet {mysqueezebox.com}: _response, nil id=nil failed: forced reconnect
1638520753.831 INFO   net.comet - :1014 Comet {mysqueezebox.com}: handleAdvice state=CONNECTED
1638520753.831 INFO   squeezebox.server - :768 disconnected mysqueezebox.com idleTimeoutTriggered: nil
1638520753.831 WARN   applet.SlimMenus - SlimMenusApplet.lua:188 notify_networkOrServerNotOK
1638520753.831 WARN   applet.SlimBrowser - SlimBrowserApplet.lua:3084 notify_networkOrServerNotOK()
1638520753.831 WARN   applet.SlimBrowser - SlimBrowserApplet.lua:3089 this is a server error
1638520753.831 INFO   net.comet - :1055 Comet {mysqueezebox.com}: advice is handshake, connect in 0 seconds
1638520754.227 INFO   squeezebox.server - :744 connected mysqueezebox.com
1638520754.227 WARN   squeezeplay - :612 no value for skinParam THUMB_SIZE_MENU found
1638520754.716 INFO   applet.SlimMenus - SlimMenusApplet.lua:502 _menuSink(45) SlimServer {mysqueezebox.com} menuDirective: nil isCurrentServer:nil

edit:
and mysqueezebox shows it is connected and it shows the correct MAC address.

**Paul Webster** · 2021-12-03, 08:52

You might be able to force logging on (if you cannot get into the menus) by closing SqueezePlay and then creating ...

%APPDATA%\SqueezePlay\userpath\logconf.lua
and put in it

Code:

return { appender={  }, category={ ["net.slimproto"]="DEBUG" } }

You might be able to force SqueezePlay to think that it has completed registration etc by editing

Code:

%APPDATA%\SqueezePlay\userpath\settings\SlimDiscovery.lua

(change the MAC address below (in 2 places) to be your real one - or maybe the bad one.

Code:

settings = {playerId="11:22:33:44:55:66",serverUuid="1-2-3-4-5",currentPlayer="11:22:33:44:55:66",serverInit={ip="192.168.1.3",},squeezeNetwork=false,playerInit={name="Squeezeplay",model="squeezeplay",},serverName="MyLMS",}

**bkerouan** · 2021-12-03, 09:20

Originally posted by Paul Webster

You might be able to force logging on...

Wow, thanks Paul for those investigations, I'll try that today and send a feedback.

**bkerouan** · 2021-12-03, 09:52

Originally posted by Paul Webster

You might be able to force logging ...

1. Created logconf.lua and started Squeezeplay. It creates the 2 log files in %temp% but they are empty.

2. I changed the MAC address to my real wifi interface MAC in the SlimDiscovery.lua file, and the issue seems solved on the first player (on my laptop).

However I noticed that for the second player (the one running on a Win10 VM), I'm unsuccessful to connect to my local LMS. I'll investigate with the logs ;-)

Thank you Paul for the good support, now everything works well and I learned a bit about the internals of Squeezeplay.

Bruno

**Paul Webster** · 2021-12-03, 10:04

Might show as zero size in file manager ... but try opening them.

**gordonb3** · 2021-12-03, 12:05

Originally posted by bkerouan

[{"ext":{"mac":"00:00:00:00:99:01","uuid":"132eb15d 21c2d306e6628325758d9f6b","rev":"7.8.0 r1291"},"supportedConnectionTypes":["streaming"],"version":"1.0","channel":"\/meta\/handshake"}]HTTP/1.1 200 (OK)
Date: Thu, 02 Dec 2021 14:46:04 GMT
Server: SqueezeNetwork Jived/7.5.4 appj007.euw/611
Content-Length: 264

Did you edit this section? I'm asking because this is not a valid MAC address, so it would appear that you have some type of virtual switch running on your laptops - a virtualization platform (QEMU, Hyper-V, VMWare, ...) maybe? If so you should go into the settings of that virtualization application and see if you can change the internal MAC address. The recommended entry is to copy the MAC address of your actual network interface or wifi adapter but change the first two digits to `02` (i.e. if you have 56:78:90:ab:cd:ef change this to 02:78:90:ab:cd:ef). This indicates that the MAC address is locally administered, so it will never match any physical device.

Edit: Just noticed that I'm asking more or less the same question as Paul did. In any case the idea here is that virtualization platforms often create a virtual internal network to allow your virtual machines to communicate with the internet by using the host computer as a masquerading router. You can verify this by running `ipconfig /all` and locate the adapter with the weird 00:00:00:00:99:01 MAC address.

Oh, and another thought: does this MAC address actually show with the ipconfig command? Another possibility is that this is a preconfigured fall-back address within squeezeplay and it returns this address because your system denies the application access to this information (User Account Control). What edition of Windows 10 are you running? Education/Home/Pro/Enterprise - did you fiddle with policies?

**bkerouan** · 2021-12-04, 12:33

Originally posted by gordonb3

Oh, and another thought: does this MAC address actually show with the ipconfig command? Another possibility is that this is a preconfigured fall-back address within squeezeplay and it returns this address because your system denies the application access to this information (User Account Control). What edition of Windows 10 are you running? Education/Home/Pro/Enterprise - did you fiddle with policies?

My guess, as the capture was done on a physical (ie non virtualized) Microsoft Laptop Go running Win11 Preview, it's very probable the MAC address is a fallback one after being denied from getting the real one.

**gordonb3** · 2021-12-04, 14:58

Originally posted by bkerouan

My guess, as the capture was done on a physical (ie non virtualized) Microsoft Laptop Go running Win11 Preview, it's very probable the MAC address is a fallback one after being denied from getting the real one.

I agree that is likely, but could you still verify whether that MAC address is also shown when you run `ipconfig /all`?

Obviously, since someone beat you in registering this MAC address with mysqueezebox you are not the first to encounter this issue and it seems plausible that you will not be the last as well. Knowing the cause will help with future incidents and possibly allow creating a workaround to prevent it completely.

SqueezePlay: This player is already linked to another SqueezeNetwork account

SqueezePlay: This player is already linked to another SqueezeNetwork account

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment