I'm moving from a world of transferring manually to a USB to moving to the world of Streaming my video and content flawlessly, wireless & on the go.
I currently have a seedbox setup with Seedbox.cc and they currently have the plex share installed and linked to my email address on plex.tv. (Please see attatched 2 images).
What i now want to do is take full advantage of my raspberry pi, as a client accessing the share and playing content on my tv.
I've tried logging in the Raspberry Pi in the interface settings and it does show up under the connected devices on myplex devices, however none of the content nor sub folders are available to view. Can anyone enlighten if what i am doing is possible ?.
I'm not sure if im able to view the content on my seedbox via the raspberry Pi since its a share from a server.
It is under "Shared Content" in your menu if you have logged in via plex.tv in RasPlex.
KnightOrc, when i get home ill take a look, again to see if i can find "Shared Content". I was going to take it back to out of box and reflash it to make sure i didn't have any corrupt in the installer. Will keep you guys posted =)
I have found no such option available to me when going through the menu, here is a few photos of my general settings on my raspberry PI that i would think could possibly affect this problem.
Note when selecting "Channel Directory" that raspberry pi restarts and comes back with the error attached.
I have tried a complete re image and re program of the pincode to make sure i can eliminate any software writing errors. Please see attatched images.
Do i manually need to provide the IP of the server as listed in photos ?
Anyone else have any ideas why i may be having this problem ??
You never stated clearly that you've followed the instructions shown in your second screenshot of your first post.
By this I mean the requirement to 'Accept invitation' from the sharing server to your sharing account.
Without such formal acceptance performed at plex.tv, the shared libraries will never be passed on to your clients.
So that's one possible explanation for the failed results.
Other possible explanations include network/firewall configuration at either side (seedbox VS your home LAN).
There's also the possibility that you've missed some part of the PMS configuration at the seedbox end.
One way to exclude some of the possibilities is to test access to your Plex account and its shared content through other Plex clients.
Both the Plex/Web client and the "Plex Home Theater" clients are completely free, and both iOS and Android clients are available at a fairly low price.
Once the sharing works properly it should work for all these clients, so if you can see the content in any of them then you know that the problem is on the Raspberry...
I've absolutely no idea how it works with a seedbox-located PMS server, so I don't even know if you can configure it yourself, through Plex/Web as used for a normal home server, or whether the maintenance is done by seedbox site administrators only. If you tell us a little more about it we may be able to give better advice.
You never stated clearly that you've followed the instructions shown in your second screenshot of your first post.
By this I mean the requirement to 'Accept invitation' from the sharing server to your sharing account.
Without such formal acceptance performed at plex.tv, the shared libraries will never be passed on to your clients.
So that's one possible explanation for the failed results.
Other possible explanations include network/firewall configuration at either side (seedbox VS your home LAN).
There's also the possibility that you've missed some part of the PMS configuration at the seedbox end.
One way to exclude some of the possibilities is to test access to your Plex account and its shared content through other Plex clients.
Both the Plex/Web client and the "Plex Home Theater" clients are completely free, and both iOS and Android clients are available at a fairly low price.
Once the sharing works properly it should work for all these clients, so if you can see the content in any of them then you know that the problem is on the Raspberry...
I've absolutely no idea how it works with a seedbox-located PMS server, so I don't even know if you can configure it yourself, through Plex/Web as used for a normal home server, or whether the maintenance is done by seedbox site administrators only. If you tell us a little more about it we may be able to give better advice.
Best regards: dlanor
Dlanor,
I have correctly setup the raspberry Pi with working ends tied to Google chrome Web TV plugin working correctly, please take a moment and spend 5 minutes reading the detailed Reddit Plex post i have posted to answer any questions or queries that you have http://redd.it/2bclqa
Can you post a screenshot of what is visible when you click on the Seedbox server name under your "Shared with me"? And if you can use "Launch" to reach your content?
And that port is for a Plex Media Server, not RasPlex.
Doing a scan of my RasPlex I get the below ports open.
PORT STATE SERVICE
22/tcp open ssh
111/tcp open rpcbind
3005/tcp open deslogin
Wow..... i just went full ■■■■■■ mode.. i was pretty exhausted last night.....
This is a quote from an open ticket with my Seedboxes admin
You cannot connect to a plex server remotely. Plex clients can connect directly to the plex server ONLY, if they are in the local network of each other. You can only access your plex shares, via a plex.tv account. I don't know if the rasplex supports plex.tv(myplex) shares
^ Just incase this effects anything
Below is the link to the request of the screenshots.
Here is a response from the seedbox admin regarding the issue;
"We are aware of this issue already, but i am afraid that this seems to be a bug mostly for plex.tv. We have contacted Plex support about it, and we are working with them to identify it. It is not a problem with our server, it seems to be a problem on the 3rd party clients. For example the plex client for iphone, ipad or android, seem to work pretty good. We noticed this problem with roku. We are waiting to get a roku on our hands (probably this week) in order to try and debug this. The plex support told us, that they know the reason of this happening (if you check the plex forums, you will see many people complaining about this) and that they plan to fix this in the next update."
Seems like its just the waiting game to push an update.
@Mozziimo: I’m not sure what to make of that message from the seedbox people. The fact remains that RasPlex works fine for remote connection to privately run servers on home computers, so it’s clear that their seedbox setup somehow differs from a normal home computer setup in some way that triggers this problem. That they state the impossibility of their servers being responsible is just the standard way for any company to avoid responsibility.
I’m not saying that RasPlex is perfect, or that it’s network behaviour might not somehow contribute to the problem. It probably does, since you can access the media through the Plex/Web browser client, but the server end clearly bears some of the responsibility as well. Else this would be failing for everyone else too, who don’t use a seedbox for the server.
In an earlier post you included this quote from the seedbox admins:
You cannot connect to a plex server remotely. Plex clients can connect directly to the plex server ONLY, if they are in the local network of each other. You can only access your plex shares, via a plex.tv account. I don’t know if the rasplex supports plex.tv(myplex) shares
That reply of theirs is utter nonsense. It’s perfectly valid to connect directly to a Plex server remotely, without using ‘shared content’ but logging in to the server using the account data of the server itself. The only reason that can’t be done with the seedbox is because they won’t allow you to do so (they won’t risk giving you PMS admin access). As for RasPlex, it most definitely is able to access shared content remotely via myPlex login. My brother uses this method every day to access shared content sections of my PMS server through his RPi running RasPlex.
Don’t get me wrong here, as I’m still not saying that the client end is guilt-free in this. I’m just saying that their way of trying to put all the blame on the client is pure nonsense. If their seedbox Plex server did interact with clients identically to a normal home server, you wouldn’t have any problem.
Now to solve the client end of the problem we first need to identify if it is a problem with the ‘upstream’ PHT design for PCs, or if the problem arose in porting that code for the Raspberry Pi. If it is an upstream problem, then it needs to be solved by the official Plex dev team for PHT, while a problem with RasPlex porting needs to be solved by the RasPlex team. And to decide which it is we need you to test PHT access to your server from a normal PC.
So please install the official PHT release on a PC and report your results for accessing your shared server content from that PC. Only then can we decide which team needs to work on this problem.
Thankyou for your detailed response i appreciate the time you dedicated to the post.
i had a feeling after further research That this is going to be a bad situation to be in, both will blame each other.
If you notice the reply from the Seedbox admin never mention once Plex Home Theatre (PHT). Only talks about apps, which more them likely are using port 80 (http) for connections.
Iwill now have to wait it out to see who blinks first, and to be honest, I think it sit fairly well with your seedbox site. They are not using a standard install of Plex media server from what I've researched just now. It's a shared install, so they will have trouble with binding with Network interfaces.
I will install PHT and point it too my shared server and see what we get back in return. I will keep you posted.
