rdiff-backup VS Nginx Proxy Manager

Rdiff-backup - close to what you do currently but at least provides versioning. Based on rsync. Source: over 1 year ago

As in just a copy of your files? This I would barely consider a backup, more of just a mirror from a point in time. What're you missing by doing this? Versions of files, deduplication, and encryption (last one being very important for the best kind of backups, which should be off-site). Just because it's not files doesn't mean it's proprietary. Proprietary would mean secret and undocumented. There are many great... Source: over 1 year ago

Rdiff Backup - Reverse differential backups that uses rsync, linking, and can tunnel via ssh. You get a full current backup with increments available to restore any version of the file with minimal storage space used. Source: over 1 year ago

Borg is great. we've been using it for the past 3 years to archive hundreds of file-level backups of servers, database dumps and VM images. Average size of each borg repo is few GB but there are few outliers up to few hundreds of GB. Borg replaced https://rdiff-backup.net/ for us and gave:. - Source: Hacker News / over 1 year ago

Robocopy is great if you don't have access to rsync. If rsync via WSL2 for instance is an option, I'd personally go with rdiffbackup. Source: over 1 year ago

Take a look at NginxProxyManager. This would give you the opportunity to put everything in the form of service1.domain.com , service2.domain.com ,etc. Source: 5 months ago

So I'm going into the log folder and I'm getting this error. It started maybe a week ago. Some of my host will go through, but if the do, its super slow. Others just out right refuse. I've tried deleting nginx entirely and still comes to the same error. I had nginx running for a few months now, but this got started. To be clear, this is what I've been using https://nginxproxymanager.com/ . I don't know if there is... Source: 9 months ago

Hi! I am setting up a home server where I host a number of different services that I want to be accessible exclusively through a proxy (Nginx Proxy Manager). What I mean is that if I serve a website on port 8081, for example, and I try to browse to the server's IP and that port, I won't be able to find the website. Instead I will have to browse to the IP and port that the proxy I set up has configured for that... Source: 9 months ago

As far as website hosting, just set up a few Docker containers: one for a web-server of your choice, and one for a reverse proxy. I recommend Nginx Proxy Manager. It handles SSL certificates for you in a super simple way (both the initial acquisition process as well as auto renewal) and makes it easy to expand to using multiple web servers in the future, or setting up redirects without filling up your DNS records. Source: 10 months ago

I'm trying to set up Nginx Proxy Manager on an existing box. Since it's already set up with a few services I don't want to mess with, and a firewall I don't particularly want to migrate (nftables, a good solution that docker apparently doesn't play nice with), I turned off docker's iptables management (despite the warnings, yes). Source: 10 months ago