If you run SABnzbd behind an Apache proxy, you can create free valid certificates using Let's Encrypt.Ī guide is available on the forums. Creating a valid certificate using Let’s Encrypt Please note using a port number below 1024 requires running as root under linux. If you expose SABnzbd to the Internet you can use 443 as port number, as this is the official number for HTTPS and allows you to not specify the port when accessing. Set it to empty to enable HTTPS on the main port. NOTE If you upgraded from an older version of SABnzbd, the HTTPS port (under Advanced) might be set to 9090. If you want it to listen on a different port specific for HTTPS, you can specify this by clicking on Advanced. (be sure to test the connection also) Next under config>folders set the following. If this is not done here, it can be done under config>servers. in the setup wizard it will prompt you to enter your usenet server information. This will enable HTTPS on the main listening port. First we will begin by configuring sabnzbd. To turn on access using HTTPS, you need enable HTTPS in Config->General. You probably only need a basic certificate, but even these are expensive not worth the price for just accessing SABnzbd. If you want trouble-free communication you need to buy a certificate from one of the many Certificate Authorities, for example from Verisign or Let’s Encrypt (see below).īe warned that certificates come with different capabilities and hence, different prices. WARNING Checking passwords is not very fast, the more passwords you list in the file the longer it will take and the more CPU power is lost.You can change the location of these files by entering the full path to both in Config->General. Specify where the file is in Config->Folders. It's a simple ASCII text file (created with Notepad, VI or TextEdit) and should contain one password per line. If you don't set a password per job, you can create a text file containing all passwords to be tried. Or as the x-dnzb-password header when SABnzbd fetches the URL. Indexers and NZB suppliers can include the password inside the NZB head section (see NZB specification): secret The password can be changed until the job enters the post-processing queue. The folder name will be My Job and PASSWORD will be used as the decryption password when unpacking. The / is used as a separator because it cannot be part of a folder name. This will set the the job name to My Job and the password to PW. In the NZB file name you can embed the password like this: My Job. Supposing you know the required password, you can give it to SABnzbd before the download starts post-processing. It’s possible to set a username and password for SABnzbd, meaning you will have to log in with the credentials every time you want to use the program. You can also add the (not very well documented) keyword configlock 1 to the INI file. will reveal the passwords, since they are shown as real '' characters. The GUI will not show the passwords and even looking at the web page source. If none of the passwords work you can set to automatically Pause or Abort the download. Run it as a service under different account and restrict access to the INI file to that account. SABnzbd will try all available passwords when it detects an encrypted job during the downloading. Trying to get a password afterwards is probably a waste of your time and/or money. It's only useful to download a password protected post when you know the password upfront. Sometimes you encounter encrypted (or password-protected) RARs.
0 Comments
Leave a Reply. |