strike

Re-fraising a bit. Yes, you do need an incoming port, but since you're using PIA you don't have to worry about that, this container does it for you. All you need to do is the 2 things I mentioned. 1. Make sure you have strict port forwarding enabled and 2. connect to a supported endpoint. But you said you confirmed that you got an incoming port in the logs, so that should all be ok. The reason an open incoming port is important is that if you don't have that, nobody can connect to you and thus you can't upload anything. But your issue seems to be something else since you do have an open incoming port. Have you checked your private tracker? What does it say? The site may have an indication if your "connectable" or not. How do you add you torrents do deluge?

Glad to help!

This is your issue. This container doesn't officially support customs networks, you need to switch to bridge or host. Which also means you have to switch any other containers who connects to deluge to bridge or host. I'm one of the few who have customs network working in this container but I don't know why it works for me and not for most people. The only advice I have is to try to set the the "Privileged" flag to ON in the container template then try again, if that doesn't work you'll have to switch to bridge/host.

You do need an open incoming port, but if you're using PIA this container does the port forwarding for you automatically. All you have to do is enable strict port forward in the container template and connect to a supported endpoint. Have you confirmed that you get an incoming port? Check the log. Also if you're on a private tracker make sure to disable peer exchange and dht in the deluge settings.

Can't see anything wrong in your log. What network type do you have in the container template? And what address do you use when you're trying to connect to the webui?

Be sure to not use any special characters in your username/password, use only 0-9,a-z,A-Z

I'm sorry this happened to you, but what you're saying is simply not true. Unraid can perfectly recover deleted files IF you have the recycle bin plugin installed and running. Also, unraid does have snapshot capability, you just have to use BTRFS, then you can snapshot all you want. And if you're a regular user of this forum you should have seen users mention over and over again that Unraid IS NOT A REPLACEMENT FOR BACKUPS. Now, that being said you might be lucky and MAYBE can recover your files. MAYBE... Several users have accidentally deleted files and been able to recover them using UFS explorer: https://www.ufsexplorer.com/ this is probably your best bet.

I have no idea, I've never tried the rtorrentvpn container. But I bet you'll find it on the github page which is normally linked in the support thread.

That I don't know as I've never tried it. Moving the torrents it's the easy part, but you have to set the file location for each torrent then force a recheck to be able to pick up where you left of. I think I remember (vaguely) someone in this thread doing it, so you might find some info if you search (use the site option in google for better search then the forum).

Deluge doesn't handle many torrents that well, this is a known issue. You might want to look at rtorrentvpn instead, as it's reported to handle 1000++ torrents very well. You also have qbittorrentvpn if you want to try that instead.

It's Friday night, so I'm awesome! And I'll try to be nice, but I can't promise anything. As I said it's Friday night so anything can happen

I'm not being a dick, I seriously think you should read it again as you're clearly seeing something that isn't there.... If you need to re-read all the posts, We have already given you the answer multiple times, but hey if you don't want to follow them then that's on you.

Either you need glasses or you can't read really well, please check the link again...

Please remove anything you have in the options variable and try again.

br0 is currently not supported by this container. Well, the truth is that some of us have it working but most people are unable to connect to the webui using bro and nobody knows why. I've had it working for a long time and it's still working, but I don't know why others have issues. One thing you can try is to set the privileged flag to on, then try again. Other than that I have no idea...

Did you even look at the link @darrenyorston posted? According to your log you're still connecting to an endpoint that doesn't support port forwarding. Please check either the link or the log as the list of supported endpoints are in there too, then try again.

This is wrong, see Q4 https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

To change the connection port you have to replace .ovpn file with a different one that uses the port you want. Search PIA's website for it, I think the link is in this thread also. The default port is 1198 UDP. But they have a link with alternative ports. Have you confirmed that you get an incoming port from the server? check the logs

That looks good. Do you have a cache drive or are your downloads share on the array? If you have a cache drive I want you to try and change your /mnt/user/downloads to /mnt/cache/downloads and change your appdata to use cache instead of user also. Restart the conatiner after. If you still have issues please follow this procedure: https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

Just make a change in the container template, change it back then hit apply. The docker run command will then pop up in a window. paste it here, but redact any username/password

I'm guessing misconfigured volume mappings. Please post your docker run command or screenshot of the template settings and a screenshot of the deluge download settings. Edit: And be sure to redact any username/password

Ah, you're totally right. I did restore the appdata from a backup, forgot I did that. I will try adding a subdomain, hopefully that will fix it. Thank you sir! Edit: I also copied the appdata using MC and forgot to check the preserve symlinks "button", that was probably the thing that messed it up..

So I got an e-mail yesterday that my certificate expires in 20 days. I check the let's encrypt log and it says that the renewal conf file is broken, how do I fix it? cronjob running on Wed Jan 30 02:08:00 CET 2019 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/example.domain.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/certbot/renewal.py", line 67, in _reconstitute renewal_candidate = storage.RenewableCert(full_path, config) File "/usr/lib/python2.7/site-packages/certbot/storage.py", line 461, in __init__ self._check_symlinks() File "/usr/lib/python2.7/site-packages/certbot/storage.py", line 520, in _check_symlinks "expected {0} to be a symlink".format(link)) CertStorageError: expected /etc/letsencrypt/live/example.domain.com/cert.pem to be a symlink Renewal configuration file /etc/letsencrypt/renewal/example.domain.com.conf is broken. Skipping. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - No renewals were attempted. No hooks were run. Additionally, the following renewal configurations were invalid: /etc/letsencrypt/renewal/example.domain.com.conf (parsefail) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0 renew failure(s), 1 parse failure(s)

Have you read my post further up? Link to it: https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=715291 Just ignore the first part regarding the password, that was for another user.

If you read the FAQ you should have seen that you need to redact your vpn user/pass from the log. The first thing you need to do is change your password asap. Also in the FAQ (somewhere), you should've seen that in order to get the optimal speed you should reduce your upload speed, have you done that? You need to limit it to about 80% of what your connection can handle. And you have followed the rest of the FAQ, specifically Q6 here: https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=433613 In addition to that here's another tip: