Announcement
Collapse
No announcement yet.
Sign in to MySqueezebox.com to improve your account security
Collapse
This is a sticky topic.
X
X
-
If you're indeed using LMS 7.9 as your signature suggests, then yes, you should definitely upgrade.Leave a comment:
-
We've recently been working on improving the way in which we store your password on MySqueezebox.com (and UESmartRadio.com). But we can only save your password the new way when you provide it to us. This usually happens when you sign in to the service.
If you're using LMS 8.3 or more recent, this change shouldn't have any impact. If you haven't upgraded yet, please do so now, as otherwise we can't improve the security of your account.
If you are running a compatible LMS version I'd suggest you head over to https://www.mysqueezebox.com and/or https://www.uesmartradio.com and sign in again. You don't have to do anything but sign in to the service. And you obviously only have to do this if you have an account on the service.
In a few months from now we plan to enable the migration for all users. If you haven't upgraded LMS by then you will no longer be able to integrate LMS with MySB. Please see https://forums.slimdevices.com/forum...de-information for some more context.
hello
i've listened to music with lms players yesterdau after a long time and i got the message of update. should i update on the players? i use lms players but lms is installed on raspberry and picoreplayer. should i update from picoreplayer?Leave a comment:
-
I'll send the IP via PN, upload is done. I've restarted the LMS to clean up the 90 MB last server.log ;-)Leave a comment:
-
No particular setting required. Just send the file. 503 actually might mean you've been rate limited due to too many requests by MySB. Please also share your public IP address of where LMS is running. That way I might find some more hints in our log files.Leave a comment:
-
mherger I will upload a server.zip, sure. But just that the "right" data is included, which loggers / parts shall I set to debug before upload? If setting the Rhapsody to debug, there is not much more than these in a repeated manner per title:
[23-05-18 19:40:04.3362] Slim::Plugin::RhapsodyDirect::ProtocolHandler::_go tTrackError (414) Error during getTrackInfo: 503 Service Unavailable
[23-05-18 19:40:04.3476] Slim::Plugin::RhapsodyDirect::ProtocolHandler::get NextTrack (184) Checking player with Rhapsody: baby -- Squeezebox Radio
[23-05-18 19:40:04.3491] Slim::Plugin::RhapsodyDirect::ProtocolHandler::_ge tTrackInfo (331) getTrackinfo trying: Tra.230032312
[23-05-18 19:40:04.3501] Slim::Plugin::RhapsodyDirect::ProtocolHandler::_ge tTrackInfo (367) Getting next track playback info from SN
[23-05-18 19:40:05.2628] Slim::Plugin::RhapsodyDirect::ProtocolHandler::__A NON__ (337) getTrackInfo failed: 503 Service Unavailable
Server:
Logitech Media Server Version: 8.3.1 - 1676361197 @ Fri Feb 17 06:43:16 CET 2023
Hostname: LogitechMediaServer
IP-Adresse des Servers: xxxxx
Server-HTTP-Portnummer: 9002
Betriebssystem: Debian (Docker) - DE - utf8
Plattformarchitektur: x86_64-linux
Perl-Version: 5.32.1 - x86_64-linux-gnu-thread-multi
Audio::Scan: 1.06
IO::Socket::SSL: 2.069
Datenbankversion: DBD::SQLite 1.58 (sqlite 3.22.0)
Anzahl erkannter Player: 1
Player-Modell: Squeezebox Radio
Gerätetyp: baby
Firmware: 7.7.3-r16676
IP-Adresse des Players: xxx
MAC-Adresse des Players: 00:04:20:xxxxx
Stärke des drahtlosen Signals: 100%
(I've also tried upgrading the radio to the community firmware some weeks ago when playing around, but using rhapsody with the community firmware is a mess...)
Leave a comment:
-
yosherl I can't find any trace of a Napster failure on our end. Would you mind sharing your full server.log.zip with me? (https://www.dropbox.com/request/T3RctyzGgNg0oFDubq6a)
Are you using a LMS 8.3 or more recent?Leave a comment:
-
That would be an independent issue. I’ll have to look into this once I’m back at a computer.Leave a comment:
-
Hm, is there any connection to the RhapsodyDirect Plugin not working since two days ago?
Logfile on Napster / Rhapsody reports 503 errors for two days now.
[23-05-17 17:58:06.8950] Slim::Plugin::RhapsodyDirect::ProtocolHandler::__A NON__ (337) getTrackInfo failed: 503 Service Unavailable
[23-05-17 17:58:06.8958] Slim::Plugin::RhapsodyDirect::ProtocolHandler::_go tTrackError (414) Error during getTrackInfo: 503 Service Unavailable
Is there any debug option to improve the logging to show the complete URL that is tried to be fetched? (I'll open a separate thread if this is not connected to the above improvement)Leave a comment:
-
mherger, since some weeks, I think from the start of the hcaptcha on the Web interfaces, the login from our Android UE Smart Radio app slowly died. First we could only change the audio level and now credentials are not accepted anymore. I checked with no root firewall, and the app uses the same URL as the webinterface. (Eu server) After reading your post above, I changed the password again successfully and even can place the cookies on Android and windows devices in order to ommit the hcaptcha for the weblogin. I two have difficulties distinguishing a dog from another annimal🤪.
Can we expect the access from this app to come to live in the (near) future?
Leave a comment:
-
He he. I couldn't actually log out until I cleared away cookies for the site.
And then I had great difficulty logging back in again, because I found it difficult to distinguish a cow from a horse. But that has now been resolved.
👍 1Leave a comment:
Leave a comment: