plex-sync icon indicating copy to clipboard operation
plex-sync copied to clipboard

How to get this working with cloud?

Open townsmcp opened this issue 8 years ago • 10 comments

Is it possible to get Plex-sync working with Plex Cloud?

townsmcp avatar Jan 11 '17 00:01 townsmcp

Yep, it works just the same as local, you just have to figure out the web address of your remote server. I'm pretty sure if you find a movie or TV episode, choose "Get Info" from the menu on the left, then click on "View XML" at the bottom of the dialog that pops up, then you will be taken to a page directly using the server hostname.

jacobwgillespie avatar Jan 11 '17 17:01 jacobwgillespie

I gave that a go last night and managed to get the Google Drive location (seems like it is IPv6 addressing - certainly not IPv4 addressing). I used the following commands though: ./plex-sync [email protected]:32400/7,r https://[email protected]/1,w but I get an error message: google drive Any suggestions?

Also, when I try syncing between my main media server and a readynas, I get a message up saying completed but no changes are actually made (using the same token number and correct library number with 'w' set as the destination. I even tried MATCH_TYPE= precise both both Cloud sync and non cloud sync and got no changes from none cloud and errors on cloud

townsmcp avatar Jan 12 '17 22:01 townsmcp

Looks like it can't connect to that address at that port - not sure if it helps, but #20 was able to connect to Plex Cloud over https. Perhaps the combination of https, omitting the port, or another address would help?

jacobwgillespie avatar Jan 17 '17 01:01 jacobwgillespie

Damn. Still gives out the same error message with or without https and with or without the port (for both my internal and the Google Drive). I just double checked the IP and my Plex token and both are correct

townsmcp avatar Jan 17 '17 08:01 townsmcp

Try using http:// with explicit defining port 80 and the token. http://[email protected]:80/1,w This way I was able to sync.

revog avatar Jan 19 '17 13:01 revog

Thanks for the advice Revog. That worked. The process went through fully.

After running the code do you do anything with the server instance? Doesn't it tak long for you have have the watched status changed where appropriate? Although I got no error messages a lot of the statuses haven't changed for me in Plex Cloud (using the right user token etc) Thanks

townsmcp avatar Jan 20 '17 07:01 townsmcp

@townsmcp: Nice to hear, it's working on your site aswell. I had the same findings as you wrote. But I think i figured out why this happened. I'm using German Titles. So the titles must be equal on both sides otherwise the matching with the precise flag did not work 100% reliable. I fixed this issue by correcting the assignment. I don't know yet why the name must be 100% equal, because as far as I know plex-sync should be aware of the imdb id, shouldn't it?

revog avatar Jan 20 '17 08:01 revog

It should know about IMDb or TMDb ID, yeah, so long as the libraries are set up the same. The default is fuzzy matching, which compares via an exact match of year, title, and optionally show name, season, etc depending on the type. Which I'm realizing now that calling it "fuzzy" can be confusing - essentially it compares names, whereas "precise" means the underlying IMDb or TMDb ID has to match.

So, what I'd do is try with the DRY_RUN flag so it prints out what it's planning to do, and try with and without the precise matching to see if one is better than the other. If it's still not doing anything, we can debug from there. Something like:

$ DRY_RUN=1 MATCH_TYPE=precise plex-sync ...

$ DRY_RUN=1 plex-sync ...

Should print out a report of items it's going to mark as watched.

jacobwgillespie avatar Jan 21 '17 06:01 jacobwgillespie

Worked for me with forced port 443: plex-sync https://foobar.ams.plex.services:443/1

hashworks avatar Mar 10 '17 22:03 hashworks

no luck for me forcing port 443 :(

FernandoMiguel avatar Jan 14 '18 13:01 FernandoMiguel