Hey there!
So, I installed Plex Requests using this guide:
I am running on Ubuntu Server 16.04 LTS.
That aspect is spinning like a top, which is nice! Thanks for the great guide! I'm having a heck of a time getting it to reverse proxy using nginx. I've tried several different configurations of my /location. The latest I tried was found on the Plex Request GitHub, here:
Here is my current version of location:
** In the above, I changed the port from 3030 to 3000, as that's what Plex Requests is running on. Also, doing a $ sudo nginx -t says everything looks OK.
The last step in the GitHub guide indicates to run this command:
**Again, I changed port 3030 in the above mentioned GitHub page to 3000.
Unfortunately, that command yields this error in terminal:
My question(s): Any suggestions on working with this error? Or, is there a different version of Plex Requests I should try? I saw a guide on this site regarding running Plex Requests on a .net framework. Would that be easier/a little more straightforward? If so, how would I go about removing my installed build and starting over with Plex Requests?
I'm completely open to removing the current service and starting over on it. The Nginx forwarding block looks to be a bit more straight forward in the other guides on this site. I just don't want to screw up any other dependencies by accidentally deleting something that's needed elsewhere.
Thanks in advance!
So, I installed Plex Requests using this guide:
Quote:http://www.htpcguides.com/install-plex-r...untu-14-x/
I am running on Ubuntu Server 16.04 LTS.
That aspect is spinning like a top, which is nice! Thanks for the great guide! I'm having a heck of a time getting it to reverse proxy using nginx. I've tried several different configurations of my /location. The latest I tried was found on the Plex Request GitHub, here:
Quote:https://github.com/lokenx/plexrequests-m...erse-Proxy
Here is my current version of location:
Quote:location /plexrequests/ {
proxy_pass http://127.0.0.1:3000;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
# For keepalive sessions and WebSockets:
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
# On every application update the name of the CSS and JS files are
# different, so they can be cached indefinitely. However, the root path
# **must not** be cached!
if ($uri != '/plexrequests/') {
expires 30d;
}
}
** In the above, I changed the port from 3030 to 3000, as that's what Plex Requests is running on. Also, doing a $ sudo nginx -t says everything looks OK.
The last step in the GitHub guide indicates to run this command:
Quote:$ROOT_URL=http://127.0.0.1:3000/plexrequests meteor
**Again, I changed port 3030 in the above mentioned GitHub page to 3000.
Unfortunately, that command yields this error in terminal:
Quote:/usr/local/lib/meteor/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
Error: EACCES, open '/usr/local/lib/meteor/.git/hooks/pre-commit.meteor-hook'
My question(s): Any suggestions on working with this error? Or, is there a different version of Plex Requests I should try? I saw a guide on this site regarding running Plex Requests on a .net framework. Would that be easier/a little more straightforward? If so, how would I go about removing my installed build and starting over with Plex Requests?
I'm completely open to removing the current service and starting over on it. The Nginx forwarding block looks to be a bit more straight forward in the other guides on this site. I just don't want to screw up any other dependencies by accidentally deleting something that's needed elsewhere.
Thanks in advance!