At the SH command line -
Please type the following and share the results:
sudo sh
which curl
I already tried that at least 8 or 9 times.
An the results are what I am showing above.
It connects to the plex account but with nowhere to claim anything
Then I am not able to help you further.
I will ask the team working on WD to join in here.
I work on Linux (workstation and server) for RedHat & Debian/Ubuntu , Synology (DSM 6 & 7), and QNAP (QTS & QuTS).
I know some of the NAS systems because they have SSH access and the command line.
Your NAS does not have SSH command line access – by design.
This is why I cannot help
Thanks a lot for all the help you gave me.
I understand.
They will contact me dorectly or through the chat.
I have another idea but it is risky. It is to delete my account. Then create a new one from scratch.
Would it solve anything?
Deleting your account won’t help
You might be able to delete the server (uninstall the package – which SHOULD erase all the metadata) and then start over
BUT
I am not certain.
I have NO ACCESS to any MyCloudHome NAS systems.
The engineering team has complete control right now for their work.
He will reach out to you either here or via PM.
Ok, thanks a lot.
I have dsm 7 DS920+
I too am a linux noobie and need very simple instructions if you have them
I replied to your post on a different thread.
Give me 5 minutes to update it.
I have already deleted my server off the list
I am running dsm 7
version is 1.21.0-3744
Thanks for the info.
See this post: Unable to reclaim my Plex Server after password reset and sign-out - #27 by FordGuy61
@ChuckPa When i use root, it doesn’t find curl :
root@premier-clap:/volume1/Download # which curl
root@premier-clap:/volume1/Download #
As admin :
admin@premier-clap:/volume1/home/admin $ which curl
/usr/builtin/bin/curl
Hah! That was dumber/easier than I thought, it was definitely just a DNS problem. Fixed it (Synology-side) and had it back up and running in no time! Thank you for writing such a great little tool, and for always being the go-to guy for Plex! Seriously though - happy to pay for both the right answer and the looks, LOL
1 Like
root@ASUSTOR-AS6704T:/volume1/.@root #
root@ASUSTOR-AS6704T:/volume1/.@root # whoami
root
root@ASUSTOR-AS6704T:/volume1/.@root # which curl
/usr/builtin/bin/curl
root@ASUSTOR-AS6704T:/volume1/.@root # grep -i version /etc/nas.conf
Version = 4.1.0.RKM1
Lastversion = 4.1.0.RKM1
Baseversion = 4.1.0.RKM1
TlsVersion = 1.1
root@ASUSTOR-AS6704T:/volume1/.@root #
If I need to make a ${CURL} variable for each host, I will but curl and wget are standard issue on $PATH / $path
Did you customize yours?
Notice: builtin is on $PATH
root@ASUSTOR-AS6704T:/volume1/.@root # echo $PATH
/sbin:/usr/sbin:/bin:/usr/bin:/usr/builtin/sbin:/usr/builtin/bin:/usr/local/sbin:/usr/local/bin:/opt/sbin:/opt/bin
root@ASUSTOR-AS6704T:/volume1/.@root #
Based on the above, what’s different with your machine?
Hello @ChuckPa ,
Thank you for your help.
Here are my results :
root@premier-clap:/volume1/home/admin # whoami
root
root@premier-clap:/volume1/home/admin # which curl
root@premier-clap:/volume1/home/admin # grep -i version /etc/nas.conf
Version = 4.1.0.RKM1
Lastversion = 4.1.0.RKM1
Baseversion = 4.1.0.RKM1
TlsVersion = 1.1
root@premier-clap:/volume1/home/admin # echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
root@premier-clap:/volume1/home/admin #
Curl doesn’t seem to be find.
And $PATH is not the same. I don’t have change that at all.
@ChuckPa ,
I finally succeed to reset the server credential with you script.
I add the path to $PATH…
root@premier-clap:/volume1/home/admin # export PATH=/usr/builtin/bin:$PATH
root@premier-clap:/volume1/home/admin # echo $PATH
/usr/builtin/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
root@premier-clap:/volume1/home/admin # which curl
/usr/builtin/bin/curl
root@premier-clap:/volume1/Download # sh UserCredentialReset.sh
Thank you very much for your help.
Hi @ChuckPa, do you know when they will contact me?
I am more and more thinking to get rid of it and change the whole system. What a waste of money and time.
I get this error on my Netgear ReadyNAS: ERROR: Could not get credentials from plex.tv (Error: 6)
Can you please advise?
@pierre_2449 Not sure where that team is located. However, if US based, be aware Monday is a national holiday in the USA. Many people are taking advantage of the long weekend for end of summer travel.
@kpfletcher_gmail_com
Plex Media Server must be able to communicate with systems at plex.tv in order to claim a server.
Verify the default gateway and DNS settings on your NAS.
Consider using a public DNS server such as 8.8.8.8 (Google), 1.1.1.1 (Cloudflare), or 9.9.9.9 (Quad9).
If you change the settings on your NAS, stop, then restart Plex Media Server.
The team member who will contact you is in New Zealand . It is only now their Monday.
If you don’t mind erasing the existing server and starting over… you can do that right now. (Uninstall / remove, restart the NAS, reinstall)
I changed the DNS settings to 1.1.1.1 and 8.8.8.8, stopped and restarted plex server, no change, stopped and restarted the NAS, no change. I can see the error in the log that the resource cannot be located. The NAS box can see the internet because plex brings down pictures for the standard services from the local web. I am based in the UK. The NAS was always accessible from the internet before, we have downloaded files from our server when we have been on holiday, for example.
