"Changes could not be saved"

[kendrakirai]

Haven't changed anything since updating ASS and HAMA April last year. ASS appears to work, Hama gives "Changes unable to be saved".

Possibly ASS is having problems as well, but Hama won't even let the library be saved.

Edit to add: Already made libraries still work, but new ones can't be made.

Edit again: What the hell, updating to the newest plex server (only a few hours older than this post) fixed it??

[KakersUK]

I ran into this issue myself, changing my library over to use HamaTV. The agent was there... but I couldn't apply and 'use' the agent.

In the end I was able to do it using the '127.0.0.1' address rather than going through the 'app.plex.tv' proxy. Either the proxy or SSL getting in the way somehow. 🤷

[KakersUK]

Looking into this further as I like to know why something happens... For me this is possibly a macOS specific issue 😅 where sometimes requesting 'localhost' defaults to the IPv6 address '::1', which is being blocked for whatever reason (maybe AV or networking config) rather than the IPv4 address '127.0.0.1'.

Could remove the DNS resolution completely and hardcode '127.0.0.1', however aware this might cause issues for the very minor number of people using IPv6 exclusively. Honestly though... most people aren't changing their settings every 2 seconds, so no great issue.

I'll probably log onto my system and access it through the IPv4 loopback address if/when my token expires. Mostly posting this as an FYI for others. 😊