More > JRiver Media Center 33 for Linux
Trouble installing JRiver on a new Debian Trixie install
anonymous:
Thank you for the quick replies!
Just tried to enable logging on my eight or ninth OS install and it works. It appears the JRiver server was was much more down than up yesterday, but that prohibited me from setting up my JRemote which was all I cared about. So, a suggestion going forward would be to eliminate the requirement to speak with a JRiver server to enable JRemote via an access key.
On another topic, is Xfce on Debian the testing/building environment? Thought Gnome, so just checking since I want to use whatever you do.
Thanks again for the quick reply.
bob:
--- Quote from: anonymous on April 01, 2025, 02:25:38 pm ---Thank you for the quick replies!
Just tried to enable logging on my eight or ninth OS install and it works. It appears the JRiver server was was much more down than up yesterday, but that prohibited me from setting up my JRemote which was all I cared about. So, a suggestion going forward would be to eliminate the requirement to speak with a JRiver server to enable JRemote via an access key.
On another topic, is Xfce on Debian the testing/building environment? Thought Gnome, so just checking since I want to use whatever you do.
Thanks again for the quick reply.
--- End quote ---
XFCE
mwillems:
--- Quote from: anonymous on April 01, 2025, 02:25:38 pm ---Just tried to enable logging on my eight or ninth OS install and it works. It appears the JRiver server was was much more down than up yesterday, but that prohibited me from setting up my JRemote which was all I cared about. So, a suggestion going forward would be to eliminate the requirement to speak with a JRiver server to enable JRemote via an access key.
--- End quote ---
So just FYI the whole point of the access key is that it pings JRiver's servers so the servers can automagically supply the IP address of the local jriver instance to the client (both internal and external IP address). The access key allows JRiver's servers to perform IP matchmaking between JRemote or other clients and local JRiver instances so they can find each other successfully. For that reason, the access key requires JRiver's servers to work at all; it's an internet enabled service that JRiver provides to make it easier to use remotes or otherwise connect JRiver instances.
If you want to avoid pinging JRiver's servers you can assign your server a static IP address (in your router), and then you can manually enter that IP address into JRemote. Then you'll have no trouble when JRiver's servers are unavailable. It's more trouble to setup on the user's end, but it can let you keep using remotes when JRiver's servers are temporarily unreachable. For example, I use a manual IP setup and had no JRemote or Gizmo trouble yesterday even when JRiver's website was inaccessible to me.
JimH:
The Access Key routine running on your computer checks the IP addresses on your machine periodically and updates our servers. The main reason to do this is that addresses can change. If you reboot your router, it will probably change, for instance. The Access Key will reflect this within a few minutes.
Navigation
[0] Message Index
[*] Previous page
Go to full version