CHBMB Posted February 10, 2017 Share Posted February 10, 2017 Not at the moment Quote Link to comment
grandprix Posted February 16, 2017 Share Posted February 16, 2017 Not at the moment Anxiously but patiently keeping my eyes peeled for this to change. Thank you for what you do. obideuce: Because I have only elementary knowledge of Dockers, I'm not sure if this would work in the meantime or not.. much less how to apply it (I've grown reliant on docker containers being built for me, bad I know but..): https://github.com/rogueosb/docker-ombi Quote Link to comment
obideuce Posted February 16, 2017 Share Posted February 16, 2017 Thanks grandprix. Funny enough, I moved to ombi this week. So far, so good. Quote Link to comment
CHBMB Posted February 17, 2017 Share Posted February 17, 2017 Sparklyballs actually did an Ombi container about a month ago, but we forgot about it, this reminded me and we've done a template tonight and released it.... It's not a drop in replacement for plexrequests though, it requires a fresh install. Quote Link to comment
grandprix Posted February 17, 2017 Share Posted February 17, 2017 Sparklyballs actually did an Ombi container about a month ago, but we forgot about it, this reminded me and we've done a template tonight and released it.... It's not a drop in replacement for plexrequests though, it requires a fresh install. Many thanks! So very many thanks. Quote Link to comment
obideuce Posted February 17, 2017 Share Posted February 17, 2017 Oh, cool, thanks guys. I found another one in CA that I setup, but I'll give yours a shot this weekend. Quote Link to comment
naturalcarr Posted March 2, 2017 Share Posted March 2, 2017 Now that Ombi is out, will PlexRequests still receive updates, or should I grab the Ombi container now? Quote Link to comment
CHBMB Posted March 2, 2017 Share Posted March 2, 2017 This will still receive updates atm. That may change in the future, but for now, you're good. Quote Link to comment
afkrejci90 Posted March 5, 2017 Share Posted March 5, 2017 (edited) Just installed plex requests docker but can't seem to get to the WebUI. The log shows that it is starting but somewhere it fails. Any ideas with what is going wrong? Here is the log: *** Running /etc/my_init.d/firstrun.sh... Starting container on Sat Mar 4 22:55:05 CST 2017 Updating repository HEAD is now at 66e822c Fix issue sending movie to radarr when approval is needed Already up-to-date. Selecting the desired branch Using the master branch Already on 'master' Your branch is up-to-date with 'origin/master'. Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting => Errors while initializing project: While loading package fourseven:[email protected]: error: Command failed: module.js:340 throw err; ^ Error: Cannot find module '../' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/home/.meteor/packages/fourseven_scss/.3.4.1.rq7oh5++os.linux.x86_64+web.browser+web.cordova/plugin.compileScssBatch.os.linux.x86_64/npm/node_modules/meteor/compileScssBatch/compileScssBatch/node_modules/.temp-1egyg5f/node_modules/node-sass/node_modules/cross-spawn/node_modules/spawn-sync/node_modules/try-thread-sleep/node_modules/thread-sleep/node_modules/.bin/node-pre-gyp:15:20) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) npm ERR! Linux 4.9.10-unRAID npm ERR! argv "node" "/home/.meteor/packages/meteor-tool/.1.3.5_1.t8l6l2++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm" "rebuild" "--no-bin-links" "--update-binary" npm ERR! node v0.10.46 npm ERR! npm v3.10.5 npm ERR! code ELIFECYCLE npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 8 npm ERR! Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the thread-sleep package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs thread-sleep npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls thread-sleep npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/.meteor/packages/fourseven_scss/.3.4.1.rq7oh5++os.linux.x86_64+web.browser+web.cordova/plugin.compileScssBatch.os.linux.x86_64/npm/node_modules/meteor/compileScssBatch/compileScssBatch/node_modules/.temp-1egyg5f/npm-debug.log module.js:340 throw err; ^ Error: Cannot find module '../' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object.<anonymous> (/home/.meteor/packages/fourseven_scss/.3.4.1.rq7oh5++os.linux.x86_64+web.browser+web.cordova/plugin.compileScssBatch.os.linux.x86_64/npm/node_modules/meteor/compileScssBatch/compileScssBatch/node_modules/.temp-1egyg5f/node_modules/node-sass/node_modules/cross-spawn/node_modules/spawn-sync/node_modules/try-thread-sleep/node_modules/thread-sleep/node_modules/.bin/node-pre-gyp:15:20) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Function.Module.runMain (module.js:497:10) npm ERR! Linux 4.9.10-unRAID npm ERR! argv "node" "/home/.meteor/packages/meteor-tool/.1.3.5_1.t8l6l2++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm" "rebuild" "--no-bin-links" "--update-binary" npm ERR! node v0.10.46 npm ERR! npm v3.10.5 npm ERR! code ELIFECYCLE npm ERR! [email protected] install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 8 npm ERR! Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the thread-sleep package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs thread-sleep npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls thread-sleep npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/.meteor/packages/fourseven_scss/.3.4.1.rq7oh5++os.linux.x86_64+web.browser+web.cordova/plugin.compileScssBatch.os.linux.x86_64/npm/node_modules/meteor/compileScssBatch/compileScssBatch/node_modules/.temp-1egyg5f/npm-debug.log Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 106 Mar 4 22:55:39 5422e7f8533c syslog-ng[113]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. Unexpected mongo exit code 14. Restarting. => Meteor 1.4.3.1 is available. Update this project with 'meteor update'. Unexpected mongo exit code 14. Restarting. Unexpected mongo exit code 14. Restarting. Can't start Mongo server. Unspecified unrecoverable error. Exit was not clean Edited March 5, 2017 by afkrejci90 Quote Link to comment
HotRod48m Posted March 6, 2017 Share Posted March 6, 2017 I have everything working but when the request button is clicked, it just says "Requesting" forever and the request is never processed. Any ideas on what I may be doing wrong? Quote Link to comment
CHBMB Posted March 6, 2017 Share Posted March 6, 2017 Not really, regardless I'd recommend switching to Ombi. Quote Link to comment
phil1c Posted October 2, 2017 Share Posted October 2, 2017 Hey! Trying to run the LS.IO docker for PlexRequests. Installs no problem, I'm able to connect CP to it with no issue, but for some reason SickRage keeps showing an error whenever I click "Test Server" (both exist on the same unRaid server). The logs don't show anything of use. I've tried: 1) Verifying IP address and server port 2) Changing SR server port 3) Changing SR API key 4) Restarting SR 5) Restarting PlexRequests 6) Connecting to SR without and with SSL 7) Adding "SickRage Sub-Directory" of "/sickrage", "/", "/sickrage/", "/home" and nothing has helped. Any clue as to what is going on? What additional information would you like to see? Cheers, Philip Quote Link to comment
phil1c Posted October 6, 2017 Share Posted October 6, 2017 Anyone have any insight? Quote Link to comment
evan Posted October 11, 2017 Share Posted October 11, 2017 Looks like there is something going on with this docker right now and request errors. Here is an open Github issue discussing it: https://github.com/lokenx/plexrequests-meteor/issues/492 1 Quote Link to comment
digiblur Posted October 12, 2017 Share Posted October 12, 2017 Didn't switch to Ombi? Quote Link to comment
evan Posted October 12, 2017 Share Posted October 12, 2017 Current Ombi docker is crashing for me and others reported on this page. Quote Link to comment
DavidIrwin Posted October 12, 2017 Share Posted October 12, 2017 On 10/11/2017 at 6:18 PM, evan said: Looks like there is something going on with this docker right now and request errors. Here is an open Github issue discussing it: https://github.com/lokenx/plexrequests-meteor/issues/492 I am suffering from this error so if any details are needed ping me and I can test or play with my system. Thanks David Quote Link to comment
j0nnymoe Posted October 12, 2017 Share Posted October 12, 2017 This image has been updated now. A manual update was pushed by @sparklyballs. Our images are updated every friday at 11pm GMT and the update that fixed this bug was released after that. 1 Quote Link to comment
evan Posted October 13, 2017 Share Posted October 13, 2017 It's working great now! Quote Link to comment
marshal.anson Posted November 30, 2017 Share Posted November 30, 2017 On 8/4/2016 at 10:04 AM, danger781 said: Hi, when I try to log in to the admin section it keeps giving me an error stating "Login forbidden". Does this mean the credentials I am supplying are incorrect? If so, how do I retrieve them? Edit: Nevermind I'm an idiot I must be an idiot too, cause I can't figure out why I'm getting the error. What'd you do to fix it? Quote Link to comment
NewDisplayName Posted December 12, 2017 Share Posted December 12, 2017 (edited) Hmm i added this today for plex/sonarr, working great in lokal network, but not from outside (ofc i port forwarded) DO i need to enable anything extra? Edited December 12, 2017 by nuhll Quote Link to comment
CHBMB Posted December 13, 2017 Share Posted December 13, 2017 17 hours ago, nuhll said: Hmm i added this today for plex/sonarr, working great in lokal network, but not from outside (ofc i port forwarded) DO i need to enable anything extra? Can't say based on that why it's not working, but I thought you were security conscious? Why are you opening random ports to the WAN when the more secure approach would be to reverse proxy this with something like the nginx LetsEncrypt container? 1 Quote Link to comment
NewDisplayName Posted December 13, 2017 Share Posted December 13, 2017 (edited) 3 hours ago, CHBMB said: Can't say based on that why it's not working, but I thought you were security conscious? Why are you opening random ports to the WAN when the more secure approach would be to reverse proxy this with something like the nginx LetsEncrypt container? I dont open random ports, i open ports i need and monitor them. Im never said im "security conscios". I just said that i think its more a security breach to install VPN (and dont need it) instead of making a client - server modell, which not even would need to open ports. - where in the worst case the attacker could turn off my unraid instead of overtaking my whole network. Should plexrequest react to requests from outside local network by default? Its in bridge. Edited December 13, 2017 by nuhll Quote Link to comment
CHBMB Posted December 13, 2017 Share Posted December 13, 2017 If you can access it from LAN, but not from WAN then the problem has to be something external to the container. Quote Link to comment
NewDisplayName Posted December 14, 2017 Share Posted December 14, 2017 Yea, seems like, i will try another port. 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.