-
Notifications
You must be signed in to change notification settings - Fork 17
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
Plex Home support #29
Comments
+1 for this. |
+1 as well for this, would love to try this tool out. |
Does this mean that if I have Plex Home setup that I am unable to use plexReport? |
+1 @bonyboy: yes |
+1 for support for Plex Home is this the corresponding error?
|
I just enabled Plex Home on my system, and everything works fine. Plex Home specifically should not be breaking this, as far as I can tell. I suspect the issue here isn't Plex Home, but that users are using the wrong 'token' (which is my fault, since my instructions could be clearer). For people getting the following error:
Can you please try the following:
|
I've emailed you on brian@stascavage.com with the requested files. I've verified using the correct tokens, as far as I am aware. |
I'm 99% sure I'm using the correct token as well. Its the one specific to the unRAID server. |
I was able to reproduce the issue. To help me verify, I created a new branch with Plex Home code. To test, in your plexReport directory, run
After that, give the script a try. To switch back to the old code, you can run:
|
When I run this command I get the following message: |
I then ran: git checkout -b plexhome This resulted in the following I subsequently ran: bin/plexReport.rb -v I still get the same result: |
Clone the repo to a different folder, and then try my steps (make sure you copy your config over) |
Managed to run it with option -v. Created a log of about 112MB. At the end the terminal screen shows the following error /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/net/smtp.rb:541:in |
After rereading the Plex Forum I switched from using my hosted mail provider to Gmail (ensuring that I had set the security settings to the 'lesssecureapps' setting) and I set the SMTP port to 587 (TLS) and not to 465 (SSL) Low and behold, the report appeared. Maybe a good addition to the installation guide to mention that people should use for example Gmail instead of a hosted mail provider |
Good call, thanks! |
Initial code for Plex Home support. Fixes #29
still getting same error on unRAID with latest changes. /opt/plexReport/bin/plexReport.rb:92:in On Mon, Feb 2, 2015 at 10:20 AM, Brian notifications@github.com wrote:
|
What is your plexWatch.log look like? |
Logfile created on 2015-02-02 11:01:13 -0500 by logger.rb/31641I, [2015-02-02T11:01:13.594004 #20] INFO -- : Starting up PlexReport looks clean On Mon, Feb 2, 2015 at 1:10 PM, Brian notifications@github.com wrote:
|
I don't think you actually updated the code then. The newest code would log an error if it cannot connect to the Plex server. You can see that on line 32 of bin/plex.rb |
No description provided.
The text was updated successfully, but these errors were encountered: