-
Notifications
You must be signed in to change notification settings - Fork 0
Here are some frequently asked questions! If you feel like there should be something added please edit this page!
So you need to download the latest release (You can find this in the Status settings page).
Once you have downloaded the latests .zip (Unblock if on Windows) you can then just overwrite your previous install directory. All your settings will stay, since Plex Requests.Net creates a Database when it starts (PlexRequests.sqlite), so you will not be overwriting the database (which contains all of your settings).
This is because you never unblocked the .zip file!
You will need to Right Click the .zip > Properties > Unblock.
You can now extract the .zip and run PlexRequests.Net !
If you want to run Plex Requests.Net as a non administrator, you will need to add a URL reservation for the port Plex Requests.Net is listening on.
You can do this with the following command in an admin cmd window:
netsh http add urlacl url=http://+:8080/ user=DOMAIN\username
Replace 8080 with the port you plan running Plex Requests.Net under, and also replace DOMAIN\username with the user you want it to run under, you can use everyone.
This is what I run under a fresh install of Plex Requests.Net
netsh http add urlacl url=http://+:3579/ user=EVERYONE
Here is some more information about netsh.
This is because HttpListener is built on top of http.sys which will listen on the port you specified on behalf of your program.
I haven't found a way to allow only a single program using HttpListener through the Windows Firewall, but you might want to limit your inbound rule to system components only by:
- Entering typing system in the field "This program" in the tab "Program and services"
- Selecting protocol type TCP in the tab "Protocols and Ports" together with the port you will be listening on
How can I run this on FreeBSD - Thanks to derblub
- Create a new standard 64bit jail
- SSH into your freenas server
- jexec <jail_name> tcsh
- pkg update && pkg upgrade
- pkg install wget mono
- echo 'jail_sysvipc_allow="YES"' >> /etc/rc.conf
- unzip | wget <release.zip>
- mv <release_dir> /var/db/plex_requests
- screen mono /var/db/plex_requests/PlexRequests.exe
- dedatch screen with ctrl + a d
You can do this by passing a valid port via the command line/terminal e.g. PlexRequests.exe 8080.
This will start the application up on port 8080 but it will not save this port to the settings. So if you then launch the application without passing in the port like the above it will go back to the old settings.
How to run PlexRequests.Net with NSSM - Thanks theginger3469:
- Hit Windows Key
- Type "CMD" (Command Prompt should pop up as top hit)
- Right click the CMD result and select "Run as Administrator" OR Ctrl+Shift+Enter (This will start it as admin as well)
- Navigate to where you have NSSM (For me its "CD C:\nssm\win64")
- type "nssm install plexrequest" (it will pop up the NSSM GUI)
- In the Application tab select the
...next to Path. - Navigate to where you unzipped
PlexRequest.exeand select it. - Notice that the Path is the path to PlexRequest.exe and Start directory should be the directory that PlexRequest.exe resides in.
- Click Install Service
- In the same CMD admin window type "nssm start plexrequest"
- Type "nssm start plexrequest"
- Enjoy!
Useful CMD commands for plexrequest:
- "nssm status plexrequest" - status of the service
- "nssm stop plexrequest" - stops the service
- "nssm start plexrequest" - starts the service
- "nssm restart plexrequest" - restarts the service All of these assuming you named the service plexrequest and your cmd session is navigated to where you have nssm installed.
1: Go to Email Notifications in the Plex Request.Net menu, and make sure "Enabled" and "Enable SMTP authentication" is checked. If you want to activate user email notifications as well, make sure that is checked. 2: In the SMTP Host name or IP, use smtp.office365.com for O365 or smtp.gmail.com for gmail 3: In SMTP port use 587 for O365, or 465 for gmail 4: In Email sender use your o365 or gmail address. Do note that setting up an alias on your o365/gmail mailaccount allows you to use an address other than your main one. 5: Set email recipient to any email you want to test against. 6: Fill in your full email address and password in the username and password field.
Submit these settings, and then you can run a test, and check that everything is working.