August 31, 20169 yr Author hi aptalca, the calibre web server doesn't work, it loads and when clicking on 'All books', it shows the next errror message: TypeError: this.undef is not a function at Object.createException (http://192.168.1.43:8081/static/stacktrace.js:81:18) at Object.run (http://192.168.1.43:8081/static/stacktrace.js:66:25) at printStackTrace (http://192.168.1.43:8081/static/stacktrace.js:57:62) at render_error (http://192.168.1.43:8081/static/browse/browse.js:134:18) at booklist (http://192.168.1.43:8081/static/browse/browse.js:271:29) at HTMLDocument. (http://192.168.1.43:8081/browse/category/allbooks:34:17) at Function.ready (http://192.168.1.43:8081/static/jquery.js:392:9) at HTMLDocument.DOMContentLoaded (http://192.168.1.43:8081/static/jquery.js:745:10) Can you post a screenshot of your settings and also a log? I'm assuming you set a custom library location and it may not have been set up correctly Attached are my settings and log. When you launched calibre the first time, did you select /config or /unraid-books as the library location. If latter, did you set the environment variable LIBRARYINTERNALPATH? To be honest, I don't remember... Shall I start from scratch? Sent from my SM-G901F using Tapatalk I would recommend that. Make sure you read the docker hub page for it. It explains how to set it up correctly
August 31, 20169 yr Anyone successfully reverse proxy the Unraid GUI with this? Or other dockers that possibly have multiple sub directories they pull files from? I am trying to get https://mydomain.com/unraid to load http://tower BUT I use muximux on my root / directory and would like to keep using that at the root. I'd really like to know how to do this too... Trying to pass through a docker's web site that runs at it's root folder, but want to put it at "/something" instead and cannot. Sadly a few of them don't have variables to reset their baseurl's.
September 1, 20169 yr hi aptalca, the calibre web server doesn't work, it loads and when clicking on 'All books', it shows the next errror message: TypeError: this.undef is not a function at Object.createException (http://192.168.1.43:8081/static/stacktrace.js:81:18) at Object.run (http://192.168.1.43:8081/static/stacktrace.js:66:25) at printStackTrace (http://192.168.1.43:8081/static/stacktrace.js:57:62) at render_error (http://192.168.1.43:8081/static/browse/browse.js:134:18) at booklist (http://192.168.1.43:8081/static/browse/browse.js:271:29) at HTMLDocument. (http://192.168.1.43:8081/browse/category/allbooks:34:17) at Function.ready (http://192.168.1.43:8081/static/jquery.js:392:9) at HTMLDocument.DOMContentLoaded (http://192.168.1.43:8081/static/jquery.js:745:10) Can you post a screenshot of your settings and also a log? I'm assuming you set a custom library location and it may not have been set up correctly Attached are my settings and log. When you launched calibre the first time, did you select /config or /unraid-books as the library location. If latter, did you set the environment variable LIBRARYINTERNALPATH? To be honest, I don't remember... Shall I start from scratch? Sent from my SM-G901F using Tapatalk I would recommend that. Make sure you read the docker hub page for it. It explains how to set it up correctly I got it working, thanks!
September 1, 20169 yr Would it be possible to run the RDP-calibre docker as a specific, non-root, user?
September 1, 20169 yr Author Would it be possible to run the RDP-calibre docker as a specific, non-root, user? You can pass the USER_ID and GROUP_ID numbers as environment variables. The default are 99 and 100
September 1, 20169 yr Would it be possible to run the RDP-calibre docker as a specific, non-root, user? You can pass the USER_ID and GROUP_ID numbers as environment variables. The default are 99 and 100 Great, thanks!
September 2, 20169 yr So I don't use a lot of dockers, but I got it installed and running. I pointed it to the address for my Sonarr and CP, added my api, and everything said "Success!" when I tested. Then I went to add the directories and realized I had to set up the mapping so I set that up in the dockers's settings. After I did that and everything was running again, I added the directories in my settings and hit the test button and I got "Error". If I remove the directories and test, it still says it is successful. Add them back, and I get an error. Can anyone suggest what I might be doing wrong? Thanks! COMMANDS: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rm -f PlexRequests PlexRequests The command finished successfully! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexRequests" --net="bridge" -e BRANCH="master" -e TZ="America/Chicago" -p 3000:3000/tcp -v "/mnt/cache/apps/plexrequests/config":"/config":rw -v "/mnt/cache/apps/couchpotato/":"/couch":rw -v "/mnt/cache/apps/Sonarr/":"/sonarr":rw -v "/mnt/user/TV/":"/tv":rw aptalca/docker-plexrequests 0a0517dd9085eabd9d1cd9af6250d43f10f1075ac2f33700a6fd15226c922413 The command finished successfully! LOGS: <--------------------------------------> <--------------------------------------> Starting container on Thu Sep 1 10:20:19 CDT 2016 Updating repository HEAD is now at 984e05c Add logging for updating download status Already up-to-date. Selecting the desired branch Using the master branch 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 <--------------------------------------> <--------------------------------------> Starting container on Thu Sep 1 10:20:19 CDT 2016 Updating repository HEAD is now at 984e05c Add logging for updating download status Already up-to-date. Selecting the desired branch Using the master branch 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 Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.10 accounts-password upgraded from 1.1.4 to 1.3.0 allow-deny added, version 1.0.5 autoupdate upgraded from 1.2.4 to 1.2.8 babel-compiler* upgraded from 5.8.24_1 to 6.9.1 babel-runtime upgraded from 0.1.4 to 0.1.11 base64 upgraded from 1.0.4 to 1.0.9 binary-heap upgraded from 1.0.4 to 1.0.9 blaze upgraded from 2.1.3 to 2.1.8 blaze-html-templates upgraded from 1.0.1 to 1.0.4 blaze-tools upgraded from 1.0.4 to 1.0.9 boilerplate-generator upgraded from 1.0.4 to 1.0.9 caching-compiler upgraded from 1.0.0 to 1.0.4 caching-html-compiler upgraded from 1.0.2 to 1.0.6 callback-hook upgraded from 1.0.4 to 1.0.9 check upgraded from 1.1.0 to 1.2.3 ddp upgraded from 1.2.2 to 1.2.5 ddp-client upgraded from 1.2.1 to 1.2.5 ddp-common upgraded from 1.2.2 to 1.2.5 ddp-rate-limiter upgraded from 1.0.0 to 1.0.5 ddp-server upgraded from 1.2.2 to 1.2.6 deps upgraded from 1.0.9 to 1.0.12 diff-sequence upgraded from 1.0.1 to 1.0.6 ecmascript upgraded from 0.1.6 to 0.5.8 ecmascript-runtime upgraded from 0.2.6 to 0.3.14 ejson upgraded from 1.0.7 to 1.0.12 email upgraded from 1.0.8 to 1.1.16 fastclick upgraded from 1.0.7 to 1.0.11 geojson-utils upgraded from 1.0.4 to 1.0.9 hot-code-push upgraded from 1.0.0 to 1.0.4 html-tools upgraded from 1.0.5 to 1.0.10 htmljs upgraded from 1.0.5 to 1.0.10 http upgraded from 1.1.1 to 1.2.9 id-map upgraded from 1.0.4 to 1.0.8 jquery upgraded from 1.11.4 to 1.11.9 launch-screen upgraded from 1.0.4 to 1.0.11 livedata upgraded from 1.0.15 to 1.0.18 localstorage upgraded from 1.0.5 to 1.0.11 logging upgraded from 1.0.8 to 1.1.15 meteor upgraded from 1.1.10 to 1.2.17 meteor-base upgraded from 1.0.1 to 1.0.4 minifier-css added, version 1.1.13 minifier-js added, version 1.1.13 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.17 mobile-experience upgraded from 1.0.1 to 1.0.4 mobile-status-bar upgraded from 1.0.6 to 1.0.12 modules added, version 0.7.6 modules-runtime added, version 0.7.6 mongo upgraded from 1.1.3 to 1.1.12 mongo-id upgraded from 1.0.1 to 1.0.5 npm-bcrypt upgraded from 0.7.8_2 to 0.9.0 npm-mongo upgraded from 1.4.39_1 to 1.5.48 observe-sequence upgraded from 1.0.7 to 1.0.12 ordered-dict upgraded from 1.0.4 to 1.0.8 promise upgraded from 0.5.1 to 0.8.4 random upgraded from 1.0.5 to 1.0.10 rate-limit upgraded from 1.0.0 to 1.0.5 reactive-dict upgraded from 1.1.3 to 1.1.8 reactive-var upgraded from 1.0.6 to 1.0.10 reload upgraded from 1.1.4 to 1.1.10 retry upgraded from 1.0.4 to 1.0.7 routepolicy upgraded from 1.0.6 to 1.0.11 service-configuration upgraded from 1.0.5 to 1.0.10 session upgraded from 1.1.1 to 1.1.6 sha upgraded from 1.0.4 to 1.0.8 spacebars upgraded from 1.0.7 to 1.0.12 spacebars-compiler upgraded from 1.0.7 to 1.0.12 srp upgraded from 1.0.4 to 1.0.9 standard-minifier-css added, version 1.0.8 standard-minifier-js added, version 1.0.8 standard-minifiers upgraded from 1.0.2 to 1.0.6 templating upgraded from 1.1.5 to 1.1.9 templating-tools upgraded from 1.0.0 to 1.0.4 tracker upgraded from 1.0.9 to 1.1.0 ui upgraded from 1.0.8 to 1.0.11 underscore upgraded from 1.0.4 to 1.0.9 url upgraded from 1.0.5 to 1.0.10 webapp upgraded from 1.2.3 to 1.3.11 webapp-hashing upgraded from 1.0.5 to 1.0.9 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.4.1.1. Changes to your project's package version selections from updating package versions: accounts-base upgraded from 1.2.10 to 1.2.11 alanning:roles upgraded from 1.2.14 to 1.2.15 aldeed:autoform upgraded from 5.7.1 to 5.8.1 aldeed:collection2 upgraded from 2.5.0 to 2.10.0 aldeed:collection2-core added, version 1.2.0 aldeed:schema-deny added, version 1.1.0 aldeed:schema-index added, version 1.1.0 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.34 autoupdate upgraded from 1.2.8 to 1.2.11 caching-compiler upgraded from 1.0.4 to 1.1.7 coffeescript upgraded from 1.0.11 to 1.0.17 ddp-client upgraded from 1.2.5 to 1.2.9 ddp-common upgraded from 1.2.5 to 1.2.6 ddp-server upgraded from 1.2.6 to 1.2.10 email upgraded from 1.1.16 to 1.1.17 fastclick upgraded from 1.0.11 to 1.0.12 fortawesome:fontawesome upgraded from 4.4.0 to 4.5.0 fourseven:scss upgraded from 3.4.1 to 3.9.0 iron:router upgraded from 1.0.12 to 1.0.13 launch-screen upgraded from 1.0.11 to 1.0.12 less upgraded from 2.5.1 to 2.5.7 mdg:validation-error added, version 0.2.0 minifier-css upgraded from 1.1.13 to 1.2.14 minifier-js upgraded from 1.1.13 to 1.2.14 momentjs:moment upgraded from 2.10.6 to 2.14.4 npm-bcrypt upgraded from 0.9.0 to 0.9.1 npm-mongo upgraded from 1.5.48 to 1.5.49 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 retry upgraded from 1.0.7 to 1.0.8 shell-server added, version 0.2.1 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.3.4 standard-minifier-css upgraded from 1.0.8 to 1.2.0 standard-minifier-js upgraded from 1.0.8 to 1.2.0 standard-minifiers removed from your project templating upgraded from 1.1.9 to 1.1.14 themeteorchef:bert upgraded from 2.1.0 to 2.1.1 useraccounts:bootstrap upgraded from 1.12.4 to 1.14.2 useraccounts:core upgraded from 1.12.4 to 1.14.2 The following top-level dependencies were not updated to the very latest version available: * ongoworks:security 1.3.0 (2.0.1 is available) * twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available) Newer versions of the following indirect dependencies are available: * autoupdate 1.2.11 (1.3.11 is available) * coffeescript 1.0.17 (1.2.4_1 is available) * ddp-client 1.2.9 (1.3.1 is available) * ddp-server 1.2.10 (1.3.10 is available) * less 2.5.7 (2.7.5 is available) * mdg:validation-error 0.2.0 (0.5.1 is available) * templating 1.1.14 (1.2.14 is available) To update one or more of these packages, pass their names to `meteor update`, or just run `meteor update --all-packages`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Sep 1 10:25:21 0a0517dd9085 syslog-ng[491]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. => Started MongoDB. [34mW20160901-10:25:39.775(-5)? (STDERR) [39m[35mNote: you are using a pure-JavaScript implementation of bcrypt.[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mWhile this implementation will work correctly, it is known to be[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mapproximately three times slower than the native implementation.[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mIn order to use the native implementation instead, run[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m meteor npm install --save bcrypt[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35min the root directory of your application.[39m [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection tv [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection movies [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection settings [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection permissions => Started your app. => App running at: http://localhost:3000/
September 5, 20169 yr hi aptalca, everything was running fine until I have an unclean shutdown. My UPS battery died, and just then I had a power out for the first time in months... Murphy's law. Since then, I can't connect to the RDP, the log show this error message on a loop: Openbox-Message: Failed to open the display from the DISPLAY environment variable. Fatal server error: Server is already active for display 1 If this server is no longer running, remove /tmp/.X1-lock and start again. I tried restarting the docker, but doesn't work. How can I remove this lock?
September 5, 20169 yr If this server is no longer running, remove /tmp/.X1-lock How can I remove this lock? Either delete it (rm /tmp/.X1-lock), or reboot. Anything in /tmp is in RAM, so gone on reboot.
September 5, 20169 yr If this server is no longer running, remove /tmp/.X1-lock How can I remove this lock? Either delete it (rm /tmp/.X1-lock), or reboot. Anything in /tmp is in RAM, so gone on reboot. I already tried to restart the docker, didn't work, will try again. Sent from my SM-G901F using Tapatalk
September 5, 20169 yr If this server is no longer running, remove /tmp/.X1-lock How can I remove this lock? Either delete it (rm /tmp/.X1-lock), or reboot. Anything in /tmp is in RAM, so gone on reboot. I already tried to restart the docker, didn't work, will try again. Sent from my SM-G901F using Tapatalk He meant reboot the computer, not restart the docker. Anything in /tmp will be wiped out on reboot since that folder is in RAM. Or delete it from the command line with the command he gave.
September 5, 20169 yr Hey, so I'm trying to get Nginx-LetsEncrypt set up but it refuses to start if the Network type is set to Bridge. No logs are generated. Starts if Network type is set to Host or None but the logs say that Nginx has failed. Any ideas? Thanks in advance
September 5, 20169 yr issues with live viewing off cams it seems to recorded fine and images open fine but live view has no image i get errors in logs of zmwatch 776 err shared data size conflict file zmwatch.pl ? any help will be great
September 6, 20169 yr Author Hey, so I'm trying to get Nginx-LetsEncrypt set up but it refuses to start if the Network type is set to Bridge. No logs are generated. Starts if Network type is set to Host or None but the logs say that Nginx has failed. Any ideas? Thanks in advance Post a screenshot of your settings and the docker log please Are you sure that the ports you are trying to forward in bridge mode not used for anything else?
September 6, 20169 yr Author issues with live viewing off cams it seems to recorded fine and images open fine but live view has no image i get errors in logs of zmwatch 776 err shared data size conflict file zmwatch.pl ? any help will be great Which zoneminder container? Did you follow the instructions on the docker hub page? There is a specific setting for fixing live view in v1.29
September 6, 20169 yr Hey, so I'm trying to get Nginx-LetsEncrypt set up but it refuses to start if the Network type is set to Bridge. No logs are generated. Starts if Network type is set to Host or None but the logs say that Nginx has failed. Any ideas? Thanks in advance Post a screenshot of your settings and the docker log please Are you sure that the ports you are trying to forward in bridge mode not used for anything else? Ports arnt being being used for anything else. No logs are generated when in Bridge mode
September 6, 20169 yr Not that I have any clue about this container or its setup, but host port 80 is definitely already in use (by unRaid's emhttp) unless you've changed the port unRaid operates on.
September 6, 20169 yr That is definitely your problem. Try setting the host port to 81 and have your router port forward from 80 to 81.
September 6, 20169 yr Not that I have any clue about this container or its setup, but host port 80 is definitely already in use (by unRaid's emhttp) unless you've changed the port unRaid operates on. that was it, i'm a big dumb dumb. thanks!
September 6, 20169 yr i was running 1.28.1 version not the 1.29 , could that be issue? after update same thing , images are perfect but no video stream update i followed extra set up on github after 1 min all of the streams kicked in thank you
September 6, 20169 yr next issue is ptz on my camera its basic ipcam what do i need to make it control the camera on Control Device and Control Address ? its mainly set up as ONVIF Camera any examples?
September 6, 20169 yr Author Hey, so I'm trying to get Nginx-LetsEncrypt set up but it refuses to start if the Network type is set to Bridge. No logs are generated. Starts if Network type is set to Host or None but the logs say that Nginx has failed. Any ideas? Thanks in advance Post a screenshot of your settings and the docker log please Are you sure that the ports you are trying to forward in bridge mode not used for anything else? Ports arnt being being used for anything else. No logs are generated when in Bridge mode Port 80 is used for unraid's web gui. That may be the problem. I also see in that log that most of the config files are present, but it creates a new dhparams file and gets a new certificate. Are you manually deleting certain files? Also in host mode nginx fails to start. Nginx error log should tell you why. Are you on 6.1.9? If so, use a /mnt/cache location for the config folder Edit: didn't realize others already commented and your issue is fixed, oops
September 6, 20169 yr So if no one has any input on my issue from the previous page, should I just try another docker and see if that works?
September 6, 20169 yr Author So I don't use a lot of dockers, but I got it installed and running. I pointed it to the address for my Sonarr and CP, added my api, and everything said "Success!" when I tested. Then I went to add the directories and realized I had to set up the mapping so I set that up in the dockers's settings. After I did that and everything was running again, I added the directories in my settings and hit the test button and I got "Error". If I remove the directories and test, it still says it is successful. Add them back, and I get an error. Can anyone suggest what I might be doing wrong? Thanks! COMMANDS: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker rm -f PlexRequests PlexRequests The command finished successfully! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexRequests" --net="bridge" -e BRANCH="master" -e TZ="America/Chicago" -p 3000:3000/tcp -v "/mnt/cache/apps/plexrequests/config":"/config":rw -v "/mnt/cache/apps/couchpotato/":"/couch":rw -v "/mnt/cache/apps/Sonarr/":"/sonarr":rw -v "/mnt/user/TV/":"/tv":rw aptalca/docker-plexrequests 0a0517dd9085eabd9d1cd9af6250d43f10f1075ac2f33700a6fd15226c922413 The command finished successfully! LOGS: <--------------------------------------> <--------------------------------------> Starting container on Thu Sep 1 10:20:19 CDT 2016 Updating repository HEAD is now at 984e05c Add logging for updating download status Already up-to-date. Selecting the desired branch Using the master branch 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 <--------------------------------------> <--------------------------------------> Starting container on Thu Sep 1 10:20:19 CDT 2016 Updating repository HEAD is now at 984e05c Add logging for updating download status Already up-to-date. Selecting the desired branch Using the master branch 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 Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.10 accounts-password upgraded from 1.1.4 to 1.3.0 allow-deny added, version 1.0.5 autoupdate upgraded from 1.2.4 to 1.2.8 babel-compiler* upgraded from 5.8.24_1 to 6.9.1 babel-runtime upgraded from 0.1.4 to 0.1.11 base64 upgraded from 1.0.4 to 1.0.9 binary-heap upgraded from 1.0.4 to 1.0.9 blaze upgraded from 2.1.3 to 2.1.8 blaze-html-templates upgraded from 1.0.1 to 1.0.4 blaze-tools upgraded from 1.0.4 to 1.0.9 boilerplate-generator upgraded from 1.0.4 to 1.0.9 caching-compiler upgraded from 1.0.0 to 1.0.4 caching-html-compiler upgraded from 1.0.2 to 1.0.6 callback-hook upgraded from 1.0.4 to 1.0.9 check upgraded from 1.1.0 to 1.2.3 ddp upgraded from 1.2.2 to 1.2.5 ddp-client upgraded from 1.2.1 to 1.2.5 ddp-common upgraded from 1.2.2 to 1.2.5 ddp-rate-limiter upgraded from 1.0.0 to 1.0.5 ddp-server upgraded from 1.2.2 to 1.2.6 deps upgraded from 1.0.9 to 1.0.12 diff-sequence upgraded from 1.0.1 to 1.0.6 ecmascript upgraded from 0.1.6 to 0.5.8 ecmascript-runtime upgraded from 0.2.6 to 0.3.14 ejson upgraded from 1.0.7 to 1.0.12 email upgraded from 1.0.8 to 1.1.16 fastclick upgraded from 1.0.7 to 1.0.11 geojson-utils upgraded from 1.0.4 to 1.0.9 hot-code-push upgraded from 1.0.0 to 1.0.4 html-tools upgraded from 1.0.5 to 1.0.10 htmljs upgraded from 1.0.5 to 1.0.10 http upgraded from 1.1.1 to 1.2.9 id-map upgraded from 1.0.4 to 1.0.8 jquery upgraded from 1.11.4 to 1.11.9 launch-screen upgraded from 1.0.4 to 1.0.11 livedata upgraded from 1.0.15 to 1.0.18 localstorage upgraded from 1.0.5 to 1.0.11 logging upgraded from 1.0.8 to 1.1.15 meteor upgraded from 1.1.10 to 1.2.17 meteor-base upgraded from 1.0.1 to 1.0.4 minifier-css added, version 1.1.13 minifier-js added, version 1.1.13 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.17 mobile-experience upgraded from 1.0.1 to 1.0.4 mobile-status-bar upgraded from 1.0.6 to 1.0.12 modules added, version 0.7.6 modules-runtime added, version 0.7.6 mongo upgraded from 1.1.3 to 1.1.12 mongo-id upgraded from 1.0.1 to 1.0.5 npm-bcrypt upgraded from 0.7.8_2 to 0.9.0 npm-mongo upgraded from 1.4.39_1 to 1.5.48 observe-sequence upgraded from 1.0.7 to 1.0.12 ordered-dict upgraded from 1.0.4 to 1.0.8 promise upgraded from 0.5.1 to 0.8.4 random upgraded from 1.0.5 to 1.0.10 rate-limit upgraded from 1.0.0 to 1.0.5 reactive-dict upgraded from 1.1.3 to 1.1.8 reactive-var upgraded from 1.0.6 to 1.0.10 reload upgraded from 1.1.4 to 1.1.10 retry upgraded from 1.0.4 to 1.0.7 routepolicy upgraded from 1.0.6 to 1.0.11 service-configuration upgraded from 1.0.5 to 1.0.10 session upgraded from 1.1.1 to 1.1.6 sha upgraded from 1.0.4 to 1.0.8 spacebars upgraded from 1.0.7 to 1.0.12 spacebars-compiler upgraded from 1.0.7 to 1.0.12 srp upgraded from 1.0.4 to 1.0.9 standard-minifier-css added, version 1.0.8 standard-minifier-js added, version 1.0.8 standard-minifiers upgraded from 1.0.2 to 1.0.6 templating upgraded from 1.1.5 to 1.1.9 templating-tools upgraded from 1.0.0 to 1.0.4 tracker upgraded from 1.0.9 to 1.1.0 ui upgraded from 1.0.8 to 1.0.11 underscore upgraded from 1.0.4 to 1.0.9 url upgraded from 1.0.5 to 1.0.10 webapp upgraded from 1.2.3 to 1.3.11 webapp-hashing upgraded from 1.0.5 to 1.0.9 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.4.1.1. Changes to your project's package version selections from updating package versions: accounts-base upgraded from 1.2.10 to 1.2.11 alanning:roles upgraded from 1.2.14 to 1.2.15 aldeed:autoform upgraded from 5.7.1 to 5.8.1 aldeed:collection2 upgraded from 2.5.0 to 2.10.0 aldeed:collection2-core added, version 1.2.0 aldeed:schema-deny added, version 1.1.0 aldeed:schema-index added, version 1.1.0 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.34 autoupdate upgraded from 1.2.8 to 1.2.11 caching-compiler upgraded from 1.0.4 to 1.1.7 coffeescript upgraded from 1.0.11 to 1.0.17 ddp-client upgraded from 1.2.5 to 1.2.9 ddp-common upgraded from 1.2.5 to 1.2.6 ddp-server upgraded from 1.2.6 to 1.2.10 email upgraded from 1.1.16 to 1.1.17 fastclick upgraded from 1.0.11 to 1.0.12 fortawesome:fontawesome upgraded from 4.4.0 to 4.5.0 fourseven:scss upgraded from 3.4.1 to 3.9.0 iron:router upgraded from 1.0.12 to 1.0.13 launch-screen upgraded from 1.0.11 to 1.0.12 less upgraded from 2.5.1 to 2.5.7 mdg:validation-error added, version 0.2.0 minifier-css upgraded from 1.1.13 to 1.2.14 minifier-js upgraded from 1.1.13 to 1.2.14 momentjs:moment upgraded from 2.10.6 to 2.14.4 npm-bcrypt upgraded from 0.9.0 to 0.9.1 npm-mongo upgraded from 1.5.48 to 1.5.49 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 retry upgraded from 1.0.7 to 1.0.8 shell-server added, version 0.2.1 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.3.4 standard-minifier-css upgraded from 1.0.8 to 1.2.0 standard-minifier-js upgraded from 1.0.8 to 1.2.0 standard-minifiers removed from your project templating upgraded from 1.1.9 to 1.1.14 themeteorchef:bert upgraded from 2.1.0 to 2.1.1 useraccounts:bootstrap upgraded from 1.12.4 to 1.14.2 useraccounts:core upgraded from 1.12.4 to 1.14.2 The following top-level dependencies were not updated to the very latest version available: * ongoworks:security 1.3.0 (2.0.1 is available) * twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available) Newer versions of the following indirect dependencies are available: * autoupdate 1.2.11 (1.3.11 is available) * coffeescript 1.0.17 (1.2.4_1 is available) * ddp-client 1.2.9 (1.3.1 is available) * ddp-server 1.2.10 (1.3.10 is available) * less 2.5.7 (2.7.5 is available) * mdg:validation-error 0.2.0 (0.5.1 is available) * templating 1.1.14 (1.2.14 is available) To update one or more of these packages, pass their names to `meteor update`, or just run `meteor update --all-packages`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Sep 1 10:25:21 0a0517dd9085 syslog-ng[491]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. => Started MongoDB. [34mW20160901-10:25:39.775(-5)? (STDERR) [39m[35mNote: you are using a pure-JavaScript implementation of bcrypt.[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mWhile this implementation will work correctly, it is known to be[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mapproximately three times slower than the native implementation.[39m [34mW20160901-10:25:39.807(-5)? (STDERR) [39m[35mIn order to use the native implementation instead, run[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m meteor npm install --save bcrypt[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35m[39m [34mW20160901-10:25:39.808(-5)? (STDERR) [39m[35min the root directory of your application.[39m [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection tv [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection movies [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection settings [34mI20160901-10:25:39.810(-5)? [39mNo change detected for the collection permissions => Started your app. => App running at: http://localhost:3000/ I don't quite understand what your issue is (not using plexrequests myself) and it seems like a settings issue with plexrequests. Based on your log and description, the container seems to run fine and the web gui comes up. You might want to ask in the plexrequests thread on the plex forum
September 6, 20169 yr I don't quite understand what your issue is (not using plexrequests myself) and it seems like a settings issue with plexrequests. Based on your log and description, the container seems to run fine and the web gui comes up. You might want to ask in the plexrequests thread on the plex forum Okay... Thanks!
Archived
This topic is now archived and is closed to further replies.