There were two things:
1) proxy settings has to be set directly in MediaMonkey.ini for MM2024, as described here: https://www.ventismedia.com/mantis/view.php?id=18585
2) there was bug causing, that these setting were not used anyway, fixed as https://www.ventismedia.com/mantis/view.php?id=21571 in builds >=3152.

OK, resent.

[quote=MiPi post_id=526649 time=1743437122 user_id=27459]
I have sent you adjusted last .FM script to PM, please test it and let me know the result.
[/quote]
Hi MiPi, it seems that your private message has not arrived to my PM inbox for some reason. May I ask you to resend? Thank you.

I have sent you adjusted last.FM script to PM, please test it and let me know the result.

Hello MiPi,

Thank you for the contact. I am unable to reply to you in private messages as it seems that I am not trusted as a new forum member.

I carried out the steps you instructed and unfortunately I see no change in the Last .fm scrobble login behaviour. At my end, it looks like nothing is changed.

Thank you for looking into this issue.

Application Error

Application throw an exception "Cannot read properties of
undefined (reading 'chbScrobblerOff')"

TypeError: Cannot read properties of undefined (reading
'chbScrobblerOff')
    at eval (file:///dialogs/dlgOptions/pnl_lastFM.js:64:26)
    at invokeCallback (file:///promise.js:399:19)
    at publish (file:///promise.js:457:9)
    at publishRejection (file:///promise.js:637:7)
    at MutationObserver.flush (file:///promise.js:193:9)
Callstack: Script: file:///mminit.js ; Func: window.myAlert ; Row:
313 ; Col: 17
Script: file:///mminit.js ; Func: window.alertException ; Row: 324
; Col: 9
Script: file:///promise.js ; Func: invokeCallback ; Row: 404 ; Col:
13
Script: file:///promise.js ; Func: publish ; Row: 457 ; Col: 9
Script: file:///promise.js ; Func: publishRejection ; Row: 637 ;
Col: 7
Script: file:///promise.js ; Func: flush ; Row: 193 ; Col: 9

Would you like to restart MediaMonkey in Safe mode?

Error

Runtime error 217 at 0183396B

My odyssey continues:

I uninstalled the debug version and reinstalled the regular MM2024. This seemed to break the connection to Last .fm, even though MM2024.1 still told me that I am logged to Last .fm. I then pressed the Scrobbler off radio button (to see if I can get the login prompt screen again), and now I got this application error in regular release of MM2024.1.0.3113:

[code]Application Error

Application throw an exception "Cannot read properties of
undefined (reading 'chbScrobblerOff')"

TypeError: Cannot read properties of undefined (reading
'chbScrobblerOff')
at eval (file:///dialogs/dlgOptions/pnl_lastFM.js:64:26)
at invokeCallback (file:///promise.js:399:19)
at publish (file:///promise.js:457:9)
at publishRejection (file:///promise.js:637:7)
at MutationObserver.flush (file:///promise.js:193:9)
Callstack: Script: file:///mminit.js ; Func: window.myAlert ; Row:
313 ; Col: 17
Script: file:///mminit.js ; Func: window.alertException ; Row: 324
; Col: 9
Script: file:///promise.js ; Func: invokeCallback ; Row: 404 ; Col:
13
Script: file:///promise.js ; Func: publish ; Row: 457 ; Col: 9
Script: file:///promise.js ; Func: publishRejection ; Row: 637 ;
Col: 7
Script: file:///promise.js ; Func: flush ; Row: 193 ; Col: 9

Would you like to restart MediaMonkey in Safe mode?[/code]

Buttons: "Restart", "Restart in Safe mode", "Continue"


When I pressed "Restart", I got the dialog window:

[code]Error

Runtime error 217 at 0183396B[/code]

Buttons: "OK"

And after all this, I do not indeed get the Last .fm login prompt screen in the regular release of MM2024.1.

This is really peculiar. I installed the MM2024.1.0.3113 debug version, and in the debug version's options the application instantly gave me the web browser prompt window to log on to Last .fm. I had never seen this window before in the regular release.

I set my login information, and now this same Last .fm connection works for the regular release of MM2024 too. I have no clue why the debug version worked and the regular never even showed me the prompt window.

This situation is now solved for me, but the reasons are still obscured.

Hi,
As for Proxy settings MM5+ uses https://www.last.fm/api for connecting to Last.FM you can check what MM calls it uses.

I can confirm it works fine here too. It's probably your network environment that's preventing the scrobbling.

Hi,
Just re-tested and can't replicate.
[url=https://ibb.co/Tdg7fRn][img]https://i.ibb.co/Tdg7fRn/image.png[/img][/url]

Maybe if you create full debug log as described at https://www.mediamonkey.com/forum/viewtopic.php?t=86643 maybe it would show why is is skipped.

[quote=Peke post_id=526547 time=1742978196 user_id=213]
Hi,
try to logout and login again to Last .fm?
[/quote]
Hello Peke,

Thank you for your reply. Last .fm log out and log in had no effect on the scrobbling problem I encounter in MM2024.1.

Hi,
try to logout and login again to Last.fm?

Hello,

I am experiencing non-functioning Last. fm scrobbling with MM2024.1.

In Options, when I turn Scrobbler submission state "On", no fields for logging in appear, and after a minute or so the selection reverts back to "Off". MediaMonkey does not inform what is happening, no error is given and I am left with puzzlement. I have experienced this since the first release of MM5.

My system is Windows 11 22H2 (OS Build 22621.4890) and this specific computer is in a proxy environment and I suspect this is the reason for this behaviour.

I would hope for more explicit information in MM so that other users in my position could have the most accurate information what the scrobbler system is doing.

Thank you on your valued and continued work on MediaMonkey.