PlexAmp headless - issue upgrading

Server Version#: 4.106.1
Player Version#: 4.6…0
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I have installed PlexAmp headless on the Raspberry Pi running Debian. Perfect. Except after a few seconds of playing, the remote connection to the Pi (both via PlexAmp on my phone, and SSH) fails. The music keeps playing though, so the connection to the server is working.

I decided to run the script again to upgrade to version 4.7.4 - the script seems to execute the upgrade

unfortunately, after the reboot, and logging in via SSH, it shows PlexAmp version 4.6.0 - so I assume the upgrade did not succeed.

Should I run a fresh install, or share a log (~/.cache/logs/Plexamp ?), or anywhere else I can look?

Thanks and regards

Matt

when you updated from 4.6.0 to 4.7.4, did you also update to node version 16? I think 4.6.0 was still using node 12

We moved to Node 16 in 4.5.3, see below:

Headless: Upgrade to node v16!

If SSH is failing, it sounds like something outside of Plexamp’s control is dying. Logs might tell the story.

Thanks for the assistance. I did do the update to the latest version of Node in the installation script, however, running a full apt upgrade, node.js seems to be “held back” - I am looking into that.

I may just do a fresh install - might be simpler :slight_smile:

You can upgrade like this:

echo "--== Install node.v16 ==--"
apt-mark unhold nodejs
apt-get purge -y nodejs
curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bash -
apt-get install -y nodejs=16.*-1nodesource1
apt-mark hold nodejs

This is what I do in my script.

2 Likes

Thanks @odinb1

The upgrade to nodejs 16 was successful

I also note that the PlexAmp logo and version on the bash prompt when using SSH, is different from the actual version

I am now testing if I can replicate the original error where the player refuses connection.

BTW - the only things running on the Pi are the OS and PlexAmp. Only when PlexAmp is playing did the failure occur. Hopefully this is now resolved :slight_smile:

Thanks everyone for the help!

Rerun the full script, stating yes to prepare for uppgrade, and upgrade prompts, after that, manually reboot, and it should be fixed.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.