ninthwalker Posted March 28, 2018 Author Share Posted March 28, 2018 (edited) NowShowing v2 is now available for testing as a 'Beta' release! I'm looking for some additional users to try it out and provide feedback before I make it production. So if any of you that visit this forum want to install it, give it a run and let me know how it works for you, that would be appreciated. NOTE: Because of the extensive code rework, a direct upgrade from 'NowShowing' to 'NowShowing v2' is NOT possible. You must install v2 by itself and configure using the new setup and Web GUI. How to Install: 1. Search unRAID Community Apps for 'Now Showing' and install the 'Now Showing v2 - Beta' app. 2. Use a new volume mapping so it will install the new config files. 3. Use a new port if you have the original NowShowing still installed as well. 4. After docker startup, configure settings via the web interface at: http://hostServerIP:hostPort/admin Changelog for NowShowing v2: Primary changes: Web Interface for all settings! (friendly setup wizard too) - No more file editing or docker settings to mess with. Library Filtering - Filter out those adult libraries you don't want everyone to see. Web Tools: Test reports, On-demand reports. Announcement email for maintenance, server downtime, special notice, etc. Other features/fixes: Easy SMTP setup and works with more email providers: Gmail, mail.com, yahoo, office365, outlook, zoho, and more. Sends as BCC instead of individual emails. Easy Plex authentication with token retrieval. Does not save Plex user/pass. Optional fail2ban to prevent brute-force password attempts. Additional features being worked on for after the main v2 release: Show fun statistics from Tautulli. Easy user selection for announcement email. Any other features users would like to see? Edited March 28, 2018 by ninthwalker 1 Quote Link to comment
luisv Posted March 28, 2018 Share Posted March 28, 2018 If you have the previous version installed, you'll need to give it another port as well. When I did that, it simply opened the web page... no wizard to complete the install. Quote Link to comment
ninthwalker Posted March 28, 2018 Author Share Posted March 28, 2018 2 minutes ago, luisv said: If you have the previous version installed, you'll need to give it another port as well. When I did that, it simply opened the web page... no wizard to complete the install. Oh yea. Can't have duplicate ports for dockers. I'll mention that in the post above. Thanks. Quote Link to comment
luisv Posted March 28, 2018 Share Posted March 28, 2018 In the docker log it said I had to visit http://hostServerIP:hostPort/admin to run the wizzard. Running it now. Quote Link to comment
luisv Posted March 28, 2018 Share Posted March 28, 2018 Very nice... I like what I see. Kudos for sure! I ran the test report, but no email yet... any logs other than the docker log so I can look for errors? Quote Link to comment
RXWatcher Posted March 28, 2018 Share Posted March 28, 2018 (edited) So..none unraid(I have unraid but I dont run containers on it). I have v2 running behind nginx-proxy like this: docker create --name=nowshowing \ -e PUID=1000 \ -e PGID=1000 \ -e VIRTUAL_HOST=nowshowing.domain.com \ -e VIRTUAL_PORT=6878 \ -e LETSENCRYPT_HOST=nowshowing.domain.com \ -e [email protected] \ -v /opt/nowshowing:/config:rw \ -v /etc/localtime:/etc/localtime:ro \ --restart=always \ --net=cloudbox \ ninthwalker/nowshowing:v2 plex is at https://plex.domain.com Errors in the docker logs: Saving to: '/config/www/img/avatar.png' 0K .......... ........ 100% 22.6M=0.001s 2018-03-28 16:23:21 (22.6 MB/s) - '/config/www/img/avatar.png' saved [18665/18665] /usr/lib/ruby/2.3.0/net/http.rb:882:in `rescue in block in connect': Failed to open TCP connection to https:80 (getaddrinfo: Name does not resolve) (SocketError) from /usr/lib/ruby/2.3.0/net/http.rb:879:in `block in connect' from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout' from /usr/lib/ruby/2.3.0/timeout.rb:101:in `timeout' from /usr/lib/ruby/2.3.0/net/http.rb:878:in `connect' from /usr/lib/ruby/2.3.0/net/http.rb:863:in `do_start' from /usr/lib/ruby/2.3.0/net/http.rb:852:in `start' from /usr/lib/ruby/2.3.0/net/http.rb:1384:in `request' from /usr/lib/ruby/gems/2.3.0/gems/httparty-0.13.1/lib/httparty/request.rb:93:in `perform' from /usr/lib/ruby/gems/2.3.0/gems/httparty-0.13.1/lib/httparty.rb:521:in `perform_request' from /usr/lib/ruby/gems/2.3.0/gems/httparty-0.13.1/lib/httparty.rb:457:in `get' from /var/lib/nowshowing/plex.rb:29:in `get' from /usr/local/sbin/combinedreport:103:in `getMovies' from /usr/local/sbin/combinedreport:378:in `main' from /usr/local/sbin/combinedreport:402:in `<main>' /usr/lib/ruby/2.3.0/net/http.rb:882:in `rescue in block in connect': Failed to open TCP connection to https:80 (getaddrinfo: Name does not resolve) (SocketError) from /usr/lib/ruby/2.3.0/net/http.rb:879:in `block in connect' from /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout' from /usr/lib/ruby/2.3.0/timeout.rb:101:in `timeout' from /usr/lib/ruby/2.3.0/net/http.rb:878:in `connect' from /usr/lib/ruby/2.3.0/net/http.rb:863:in `do_start' from /usr/lib/ruby/2.3.0/net/http.rb:852:in `start' from /usr/lib/ruby/2.3.0/net/http.rb:1384:in `request' from /usr/lib/ruby/gems/2.3.0/gems/httparty-0.13.1/lib/httparty/request.rb:93:in `perform' from /usr/lib/ruby/gems/2.3.0/gems/httparty-0.13.1/lib/httparty.rb:521:in `perform_request' from /usr/lib/ruby/gems/2.3.0/gems/httparty-0.13.1/lib/httparty.rb:457:in `get' from /var/lib/nowshowing/plex.rb:29:in `get' from /usr/local/sbin/webreport:103:in `getMovies' from /usr/local/sbin/webreport:378:in `main' from /usr/local/sbin/webreport:398:in `<main>' Edit: it looks like you assume non-ssl for plex hostname because if I just enter hostname its working and the nowshowing logs show its generating. I'd suggest having people put in the full URL http://host or https://host to compensate for those of us that only run https. Edited March 28, 2018 by RXWatcher Quote Link to comment
ninthwalker Posted March 28, 2018 Author Share Posted March 28, 2018 26 minutes ago, luisv said: Very nice... I like what I see. Kudos for sure! I ran the test report, but no email yet... any logs other than the docker log so I can look for errors? When you ran the test report did a notification in the web UI say it was sending or sent successfull? besides the dockers log there is also a logs directory in the config file with additional logs. Does the nowshowing.log file there say anything or the main docker log? Quote Link to comment
ninthwalker Posted March 28, 2018 Author Share Posted March 28, 2018 54 minutes ago, RXWatcher said: So..none unraid(I have unraid but I dont run containers on it). I have v2 running behind nginx-proxy like this: docker create --name=nowshowing \ -e PUID=1000 \ -e PGID=1000 \ -e VIRTUAL_HOST=nowshowing.domain.com \ -e VIRTUAL_PORT=6878 \ -e LETSENCRYPT_HOST=nowshowing.domain.com \ -e [email protected] \ -v /opt/nowshowing:/config:rw \ -v /etc/localtime:/etc/localtime:ro \ --restart=always \ --net=cloudbox \ ninthwalker/nowshowing:v2 plex is at https://plex.domain Edit: it looks like you assume non-ssl for plex hostname because if I just enter hostname its working and the nowshowing logs show its generating. I'd suggest having people put in the full URL http://host or https://host to compensate for those of us that only run https. Thanks for the catch and feedback. Yes, it uses http unless a different protocol is specified since a lot of people just put an IP address there and don’t force ssl. I will add add an extra note under that field so users will know to specify a protocol. Let me know if you come across any other quirks like that. Thanks. Quote Link to comment
wgstarks Posted March 28, 2018 Share Posted March 28, 2018 1 hour ago, ninthwalker said: Oh yea. Can't have duplicate ports for dockers. I'll mention that in the post above. Thanks. So the /config and Container Port need to be different from V1? I’d like to continue using V1 while I play around with V2. Maybe something like Container Port=7878 /config= /mnt/cache/appdata/nowshowingV2? Quote Link to comment
ninthwalker Posted March 28, 2018 Author Share Posted March 28, 2018 5 minutes ago, wgstarks said: So the /config and Container Port need to be different from V1? I’d like to continue using V1 while I play around with V2. Maybe something like Container Port=7878 /config= /mnt/cache/appdata/nowshowingV2? Correct. You can keep using the original NowShowing. Just specify a different port and appdata path and both will run concurrently. Quote Link to comment
jedimstr Posted March 29, 2018 Share Posted March 29, 2018 Looks like I'm getting the same old error I used to get with the last versions of the old PlexReports and original Now Showing even with my HAMA based Anime Library excluded: /usr/local/sbin/combinedreport: end of file reached (EOFError) This shows in the log everytime I run a test. SMTP setup works with the announcement email. I'll note (just as I did sometime last year) that I used to be able to run PlexReports without issue since it ignored my HAMA agent based Anime Library, and at some point (probably same time PlexReports started having issues with empty/blank Libraries) PlexReports stopped working. Now Showing V1 and now V2 doesn't seem to fix this situation. I added my Anime Library to the Plex Settings/Libraries To Skip, but it still hits this EOFError. I even added all my personal family video libraries and other home video libraries that shouldn't be an issue to the Libraries To Skip list, only leaving Movies, TV Shows, and my music libraries (which this should be skipping anyway since they're not videos). Still no go. Quote Link to comment
ninthwalker Posted March 29, 2018 Author Share Posted March 29, 2018 2 hours ago, ninthwalker said: Thanks for the catch and feedback. Yes, it uses http unless a different protocol is specified since a lot of people just put an IP address there and don’t force ssl. I will add add an extra note under that field so users will know to specify a protocol. Let me know if you come across any other quirks like that. Thanks. v2 has been updated to allow http/s and various port/url combinations for the plex server host/IP. Quote Link to comment
ninthwalker Posted March 29, 2018 Author Share Posted March 29, 2018 (edited) 24 minutes ago, jedimstr said: Looks like I'm getting the same old error I used to get with the last versions of the old PlexReports and original Now Showing even with my HAMA based Anime Library excluded: /usr/local/sbin/combinedreport: end of file reached (EOFError) This shows in the log everytime I run a test. SMTP setup works with the announcement email. I'll note (just as I did sometime last year) that I used to be able to run PlexReports without issue since it ignored my HAMA agent based Anime Library, and at some point (probably same time PlexReports started having issues with empty/blank Libraries) PlexReports stopped working. Now Showing V1 and now V2 doesn't seem to fix this situation. I added my Anime Library to the Plex Settings/Libraries To Skip, but it still hits this EOFError. I even added all my personal family video libraries and other home video libraries that shouldn't be an issue to the Libraries To Skip list, only leaving Movies, TV Shows, and my music libraries (which this should be skipping anyway since they're not videos). Still no go. Is it correctly skipping your Anime and other 'Libraries to skip'? In the logs\nowshowing.log it should have a line in there about 'skipping My Anime's Library' EDIT: Oh, or is it not even generating the above log becasue it errors out? Edited March 29, 2018 by ninthwalker Quote Link to comment
jedimstr Posted March 29, 2018 Share Posted March 29, 2018 (edited) 12 minutes ago, ninthwalker said: Is it correctly skipping your Anime and other 'Libraries to skip'? In the logs\nowshowing.log it should have a line in there about 'skipping My Anime's Library' EDIT: Oh, or is it not even generating the above log becasue it errors out? Barely generates anything when it errors out... This is what that log has: :/mnt/cache/appdata/NowShowingv2/logs# tail nowshowing.log I, [2018-03-28T20:51:36.777404 #1208] INFO -- : Announcement Email Sent. I, [2018-03-28T20:54:53.374364 #1213] INFO -- : Starting up NowShowing I, [2018-03-28T20:58:53.251809 #1226] INFO -- : Starting up NowShowing I, [2018-03-28T21:01:42.762540 #1239] INFO -- : Starting up NowShowing I, [2018-03-28T21:42:04.322653 #1188] INFO -- : Starting up NowShowing And the container log has this after a fresh restart and test report run: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 10-apply-perms: applying... [fix-attrs.d] 10-apply-perms: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-set-uidgid: executing... usermod: no changes ----------------------------------------- NowShowing ----------------------------------------- Brought to you by: Ninthwalker/GroxyPod/Limen75 ----------------------------------------- User xyz set to: 99 Group xyz set to: 100 ----------------------------------------- [cont-init.d] 10-set-uidgid: exited 0. [cont-init.d] 20-setup: executing... Advanced config file detected. Keeping existing files rm: can't remove '/etc/fail2ban/jail.d/*': No such file or directory Server ready Please go to http://hostServerIP:hostPort/admin to configure settings [cont-init.d] 20-setup: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2018-03-28 21:40:41: (log.c.217) server started /usr/local/sbin/combinedreport: end of file reached (EOFError) Edited March 29, 2018 by jedimstr Quote Link to comment
luisv Posted March 29, 2018 Share Posted March 29, 2018 (edited) 14 hours ago, ninthwalker said: When you ran the test report did a notification in the web UI say it was sending or sent successfull? besides the dockers log there is also a logs directory in the config file with additional logs. Does the nowshowing.log file there say anything or the main docker log? I was able to figure it out. I noticed an error in the docker log with server IP and port listed twice, so I went back to the Plex tab and I mistakenly entered the port number along with the Plex server's IP address... I'm just used to typing in the port # so did it out of habit. Once I removed the port number, and tried it again, it ran successfully and the email was sent. It took another min or two to update the web page. Edited March 29, 2018 by luisv Quote Link to comment
wgstarks Posted March 29, 2018 Share Posted March 29, 2018 (edited) V2 seems to be working properly for me. Test worked as expected.? We'll see how the regular automated features do. One question. Using the wizard for initial setup, if I select “Already have a token” is it still necessary to enter plex user/password? Really doesn’t matter now but I wondered if I really needed both. Edit: Got to say I really love the new admin page. Very nicely done. Edited March 29, 2018 by wgstarks Quote Link to comment
GroxyPod Posted March 29, 2018 Share Posted March 29, 2018 PSA to anyone using NameCheap Hosting that wants to use the email functionality of NowShowingV2 NameCheap specifically states that your SSL SMTP address is domain.com however this will not work properly with the NowShowingV2 application. You need to use the back-end CPANEL address that you were initially instructed to visit prior to your domain being setup <eg: server##.web-hosting.com> as the SMTP address. If you do not use this address, the application will encounter an SSL certificate error ('host does not match the server certificate') and you will not be able to send email. 1 Quote Link to comment
GroxyPod Posted March 29, 2018 Share Posted March 29, 2018 PSA to anyone using InMotionHosting's hosting services that wants to use the email functionality of NowShowingV2 Similar to NameCheap, you will need to utilize the SSL SMTP address instead of your domain name for the SMTP address <eg: server##.inmotionhosting.com> Quote Link to comment
ninthwalker Posted March 29, 2018 Author Share Posted March 29, 2018 (edited) 6 hours ago, wgstarks said: V2 seems to be working properly for me. Test worked as expected.? We'll see how the regular automated features do. One question. Using the wizard for initial setup, if I select “Already have a token” is it still necessary to enter plex user/password? Really doesn’t matter now but I wondered if I really needed both. Edit: Got to say I really love the new admin page. Very nicely done. The "already have token' is there for uses that don't wan't to enter in a username/password. So those fields can be left blank if entering your own. Either way, the new v2 docker does not store the Plex username/password anymore like the old version. Glad you like the new update! Edited March 29, 2018 by ninthwalker Quote Link to comment
ninthwalker Posted March 29, 2018 Author Share Posted March 29, 2018 16 hours ago, jedimstr said: Barely generates anything when it errors out... This is what that log has: :/mnt/cache/appdata/NowShowingv2/logs# tail nowshowing.log I, [2018-03-28T20:51:36.777404 #1208] INFO -- : Announcement Email Sent. I, [2018-03-28T20:54:53.374364 #1213] INFO -- : Starting up NowShowing And the container log has this after a fresh restart and test report run: /usr/local/sbin/combinedreport: end of file reached (EOFError) Bummer. I was hoping that the Library filtering would solve your Hama agent issues as well by not looking at them. The Hama agent must embed itself pretty good into plex if Skipping the Library it's attached to also makes it error out. Unfortunately I think this docker is still a bust for you. =( Quote Link to comment
ninthwalker Posted March 29, 2018 Author Share Posted March 29, 2018 6 hours ago, luisv said: I was able to figure it out. I noticed an error in the docker log with server IP and port listed twice, so I went back to the Plex tab and I mistakenly entered the port number along with the Plex server's IP address... I'm just used to typing in the port # so did it out of habit. Once I removed the port number, and tried it again, it ran successfully and the email was sent. It took another min or two to update the web page. Great. This little Server host/ip quirk was also brought up by @RXWatcher yesterday. I pushed a little fix and added a note next to that field. If an ip is entered it defaults to 32400 for people that just enter an IP. For people that use a cloud based, or hostname, they can enter in http:// or https:// and it will only use what's entered in the field so SSL can be forced or nonstandard ports, etc. 1 Quote Link to comment
jedimstr Posted March 29, 2018 Share Posted March 29, 2018 (edited) 1 hour ago, ninthwalker said: Bummer. I was hoping that the Library filtering would solve your Hama agent issues as well by not looking at them. The Hama agent must embed itself pretty good into plex if Skipping the Library it's attached to also makes it error out. Unfortunately I think this docker is still a bust for you. =( Definitely a bummer... thanks anyway. If you encounter something in the future that you may want to try, I can test. If it helps any, here's the github repo for the Absolute Series Scanner and HAMA agent with plugin and scanner install instructions: https://github.com/ZeroQI/Hama.bundle Thanks! Edited March 29, 2018 by jedimstr Quote Link to comment
ksarnelli Posted April 5, 2018 Share Posted April 5, 2018 I run an internal Postfix SMTP relay server and it seems as though NowShowingv2 currently requires TLS. Can you add an option to select the transport encryption (in this case, none)? Thanks! Quote Link to comment
ninthwalker Posted April 5, 2018 Author Share Posted April 5, 2018 7 hours ago, ksarnelli said: I run an internal Postfix SMTP relay server and it seems as though NowShowingv2 currently requires TLS. Can you add an option to select the transport encryption (in this case, none)? Thanks! Are you using v2? (with the web interface). It's set for auto tls, so if the server responds that it doesn't support that then it shouldn't use it. What are your smtp settings? port? auth type? (ie login,plain) Quote Link to comment
ksarnelli Posted April 5, 2018 Share Posted April 5, 2018 4 hours ago, ninthwalker said: Are you using v2? (with the web interface). It's set for auto tls, so if the server responds that it doesn't support that then it shouldn't use it. What are your smtp settings? port? auth type? (ie login,plain) Yep, using v2 with the web interface. I don't see a place to specify auth type. I get the following in the logs when trying to send a test email: /usr/lib/ruby/2.3.0/openssl/ssl.rb:318:in `post_connection_check': hostname "**removed**" does not match the server certificate (OpenSSL::SSL::SSLError) from /usr/lib/ruby/2.3.0/net/smtp.rb:601:in `tlsconnect' from /usr/lib/ruby/2.3.0/net/smtp.rb:564:in `do_start' from /usr/lib/ruby/2.3.0/net/smtp.rb:521:in `start' from /usr/lib/ruby/gems/2.3.0/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:112:in `deliver!' from /usr/lib/ruby/gems/2.3.0/gems/mail-2.6.3/lib/mail/message.rb:252:in `deliver!' from /var/lib/nowshowing/mailAnnouncement.rb:100:in `sendMail' from /usr/local/sbin/announcementreport:87:in `main' from /usr/local/sbin/announcementreport:91:in `<main>' Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.