INTERACT FORUM
Linux => JRiver Media Center 32 for Linux => Topic started by: Marcellus on June 04, 2024, 07:49:58 am
-
Library sync between the library server and desktop not working, the message from system is; There was a problem sending changes to the server: Changes are only accepted from authenticated clients. Enable authentication on the server in Options > Media Network. Did this on the system with the server role, and then went to the desktop pc, disconnected the library, reconnected the library, but it never asks for credentials. What am I missing here?
-
Restart MC on the server.
-
Thank you, unfortunately, that did not help. If i change something on the library server, restart both the client and the server MC, it is reflected to the client MC, but yeah, it uses the library from the server. Changing things on the client does nothing on the server. Forcing it with the procedure above results in the same message. Again, I am never asked for the username and password.
-
You may not have authentication set on the server. Double check and try the wiki.
-
You may not have authentication set on the server. Double check and try the wiki.
Of course I did. I wrote just above here; "Enable authentication on the server in Options > Media Network. Did this on the system with the server role"..
Expected behavior would be: when trying to change (for example the amount of stars for a track) something; the server asks for authentication. When connecting (again) to the database, the server asks for auth. But this does not happen.
I added screenprints 1st is server 2nd is client...
one thing is a bit weird though, on the client, it says that " 'mozart (Bibliotheek server)' is a client of the Library Server with the access key YWjVku" but that is one and the same system. 1st screenprint is taken from mozart, the server..
-
Read-only Authentication is set to Everyone, that's why. When that option is set you can't make any changes as it's read-only. Set Read-Only Authentication to Username and password and then setup an additional read-only authentication login username/password (e.g. readonly/readonly) to use with clients you don't want making server changes.
-
Thnx, Awesome Donkey, that solved the issue. It is a bit weird, normally one would say, read-only for everyone, write access only for authenticated users. So read-only access SHOULD be without password in my opinion, because if one never changes these settings, that's exactly what is the case... Still, I am happy with this solution.