Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to claim on a NAS from windows?? #41

Open
JJs-Code opened this issue Sep 26, 2023 · 8 comments
Open

How to claim on a NAS from windows?? #41

JJs-Code opened this issue Sep 26, 2023 · 8 comments

Comments

@JJs-Code
Copy link

Windows has its own installer, and linux and mac, have theirs, there is also some documentation on how to claim to a nas from linux or mac, but absolutely nothing at all of any sort whatsoever even slightly mentioning about how to claim to a NAS from windows.

a little help please.

@trumpy81
Copy link
Collaborator

trumpy81 commented Sep 26, 2023

I guess you missed the Wiki page here: https://github.com/ukdtom/ClaimIt/wiki

NAS is covered near the bottom of the page.

You will find a link there that will take you to the ClaimPMS4Win Wiki page where you will find a link to download the ClaimPMS4Win application on the Downloads page (in the menu on the right of page).

Download the file and unzip it to your desktop. Run the program and follow the instructions on the How To page.

Make sure you enter the details you use to log into Plex from your NAS (if they are different from your PC).

Also, when you open Plex/Web, make sure you open it with your NAS IP Address.

E.G. http://192.168.0.14:32400/web

Substitute your NAS IP Address for 192.168.0.14

@JJs-Code
Copy link
Author

the claim button remains greyed out, and it says no pms server found, presumably because it is not running on windows, it is running on the nas, the how to page mentions nothing at all about NAS pms's. I have chrome with the pms window open in the correct address 192.168.0.4/32400/web

@JJs-Code
Copy link
Author

consequently i have dusted off my ancient mac and slowly managed to run the mac os way which eventually returned the error 500, looking at the documentation, it says it could be:

My preferences.xml file, which i have never heard of, ive done a thorough search on my pc and cannot find any file by that name that relates to plex.

A dodgy pms install, highly unlikely, ive only just reinstalled it, following various different version installs after desperately trying to get it to work, so reinstalling it again for the 5th or so time, i cant see making any difference. One thing to note tho is that im using a seagate personal cloud nas, which are pretty old now, and im wondering if there are some compatibility issues with these? i dont believe seagate even make NAS's any more so i was quite sure that when i picked Seagate as the PMS version on their website that this was the correct thing to do.

PMS cant access the internet, ive ran a ping test "ping 192.168.0.4" and it comes back straight away with a very fast ping, so i think thats unlikely. I cant run ping ping-test.net because PMS is not running from the mac or my pc so i have no terminal to run this command in

my dns server is too slow, try googles DNS, well i have done this on my PC, but as far as i can tell i have no way of doing this on my NAS, so this doesnt seem like an option either

@trumpy81
Copy link
Collaborator

trumpy81 commented Sep 26, 2023

Error 500 means there is an internal server issue with the Plex server running on the NAS. The preferences.xml file lives on the NAS, not on your PC/Mac.

On a Seagate NAS, it is found here: /data/plex_conf/Library/Application Support/Plex Media Server.

See this page for more details on accessing it via SSH: https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/

Make sure you have installed the correct version of Plex to suit the make/model and OS version of your NAS.

Also, be aware that Plex must be a recent/current version, younger than Oct 2021. Older versions may not be supported any longer.

If you are able to, SSH into the NAS and run the claimpms.sh file you copied to the NAS. You may also run ping ping-test.net from the SSH prompt to check if the NAS has a connection to that address on the internet.

Follow the instructions found here: https://github.com/ukdtom/ClaimIt/wiki/How-To-Linux%2C-Mac to setup and run the claimpms.sh file.

Running ping from your PC/Mac to the NAS IP Address will only show if your Local LAN connection is OK or not, it tells you nothing about a WAN connection which is needed.

If you still get the 500 error, then PMS is most likely not installed or configured correctly on the NAS or it is too old or the network connection to the NAS is flaky in some way.

Try rebooting your modem/router and everything connected to it. That should correct any DNS issues you may be having and give you a good clean connection, if not, then you will need to troubleshoot your LAN/WAN connections.

If all else fails, install Plex on your Win10/11 PC and allow it to access your files on the NAS. You will need to have the PC and NAS running when you want to use Plex, but otherwise you should not have any issues.

@JJs-Code
Copy link
Author

if i have never touched the preferences.xml file, it would seem like a poor use of time trying to find it now no? surely there would be no reason for me to try to correct it when i have never touched it in the first place.

i am running the following plex server version: 1.32.5.7516-8f4248874 September 18, 2023 well within the cut off date of oct 2021.

in terms of making sure this is the correct version of plex to suit the make/model of my nas, well i just looked through the list and there is only one seagate option so i figure it must be that, but if there are other seagate versions that i am not seeing then where would i find these? are the seagate distributions one size fits all or are there specific hardware appropriate versions?

the claimpms.sh file was not copied into the nas it was just copied to the downloads folder in my mac, because i do not have a terminal in the nas to access it from, if this is not the case, please would you elaborate on how to do that, i have read the mac how to multiple times and it does not give nas specific instructions.
https://github.com/ukdtom/ClaimIt/wiki/How-To-Linux%2C-Mac

There is a sentence at the bottom that states:
Note: If your Plex Media Server is on a remote machine, you should upload the file to the remote machine and use the local IP Address of the machine running PMS. When running the script directly on the remote PMS server itself, enter an IP address of 127.0.0.1.

but this explains nothing about how to run the file from the nas, its skipping the most important part. also the last sentence suggests that you can execute scripts from within PMS, is this correct? if so, how would you go about doing this?

in terms of the PMS not being installed or configured correctly, the install process is literally just clicking one button, you dont have to do anything, or select what parts to install, so how can there be anything that can go wrong. once its installed its installed, there is not setup process afterwards.

I have just tried rebooting the router, and unfortunately that has not fixed the error either. I've ran the script from the mac again (this time after placing it in the nas drive) and it still gives me a "fatal error" "HTTP returned status 500" error

I dont want my pc running 24/7 just for the luxury of having a plex server, especially when it has been running smoothly on my NAS for years now, that not an acceptable compromise.

@trumpy81
Copy link
Collaborator

First of all, I gave you the details to access preferences.xml just in case you ever wanted to, not because you had to.

SSH (Secure Shell) is the 'terminal' program you use to access the NAS with. All commands actually run on the NAS using the Linux OS installed there.

You may need to grant permission to use SSH in your NAS settings somewhere, so do check for that.

Then to use SSH, open a terminal window on your Mac or PC and type in:

ssh admin@NAS_IP_Address

Note: admin may be a user with admin privileges, use that users name instead. NAS_IP_Address is the IP address of your NAS. E.G. 192.168.0.4

Check your NAS documentation, the admin account may be called something else on your NAS.

If you have setup to use a port number other than 22, then type -p Port Number at the end of the above command.
E.G. ssh admin@NAS_IP_Address -p 44

Once you have logged into the NAS via SSH, you use Linux commands such as CD (change directory) or LS to list the contents of the current directory.


Your NAS is NOT a remote device, it is Local to you on your Local network, otherwise the information does relate to your NAS, so use 127.0.0.1 when asked for the IP Address while running claimpms.sh on the NAS itself.

Follow the instructions shown on the How To Linux, Mac page after you log into the NAS using SSH and after you copy the claimpms.sh file to the NAS.

You will need to cd to the location on the NAS where you saved the claimpms.sh file etc.

I am not familiar with Seagate NAS so you will need to search for the relevant Linux commands and how to use them on your NAS.

All Linux BASH commands can be found here: https://ss64.com/bash/

Do note: that not all Linux BASH commands may be available on your NAS.

Also, check your NAS settings and make sure Plex has all of the needed permissions to run and access your files on the NAS. Linux is VERY particular when it comes to permissions.

That may be another reason you see the 500 error.

As for Plex versions for your NAS, you may well be using the correct one. Some NAS have multiple versions though.

@JJs-Code
Copy link
Author

The issue has been fixed now, the problem was simply that my NAS was not set to the correct date and time, upon updating this, claiming the server worked immediately

@trumpy81
Copy link
Collaborator

Thanks for getting back to me and letting me know what the solution was, it is always helpful to know. :)

I am glad you were able to find the solution and I hope you can enjoy Plex now that it is solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants