Hi Michael
the example was from local LAN. backuppc is running and working and nginx runs
with a lot other services behind it.
I'm not that new to nginx, more a "new" user to backuppc.
normally the directive /pathto/ needs a change in the base url of some web
services behind nginx. This "could" help sometimes.
I do not know where to change the base url in the backuppc server
Regards
Matt
________________________________
From: Michael Stowe <michael.st...@member.mensa.org>
Sent: Monday, April 15, 2019 9:48 PM
To: General list for user discussion, questions and support
Cc: Mathew Perry
Subject: Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on
another host
On 2019-04-15 12:13, Mathew Perry wrote:
it's not that easy 🙂
Did you ensure that it was working locally first?
with this directive:
location /backuppc/ {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header Host $http_host;
proxy_max_temp_file_size 0;
proxy_pass http://ipaddress:port/;
proxy_redirect http:// https://;
proxy_redirect off;
}
leads to: “The Requested URL /BackupPC_Admin was not found on this server”
i wouldn't ask here if only a proxy pass is needed....
-------------------------
FROM: Johan Ehnberg <jo...@molnix.com>
SENT: Monday, April 15, 2019 10:08 AM
TO: backuppc-users@lists.sourceforge.net
SUBJECT: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on
another host
I accidentally sent my reply just to Matthew. Here is a copy for
future reference.
-------- Forwarded Message --------
SUBJECT:
Re: [BackupPC-users] backuppc behind nginx which is on another host
DATE:
Mon, 15 Apr 2019 12:25:51 +0300
FROM:
Johan Ehnberg <jo...@molnix.com>
TO:
Mathew Perry <mamema2...@hotmail.com>
Hi Matthew,
I would recommend using the nginx server as a reverse proxy.
So, set up the backuppc server normally (i.e. with its own web
server), and on nginx, use something like the following if you will
connect remotely over TLS and Let's Encrypt certificate:
server {
listen 80;
server_name backuppc.example.com;
return 301 https://$server_name$request_uri [1];
}
server {
listen 443 ssl http2;
server_name backuppc.example.com;
ssl_prefer_server_ciphers on;
ssl_ciphers
EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;
ssl_certificate
/etc/letsencrypt/live/backuppc.example.com/fullchain.pem;
ssl_certificate_key
/etc/letsencrypt/live/backuppc.example.com/privkey.pem;
ssl_session_cache shared:SSL:5m;
ssl_session_timeout 1h;
add_header Strict-Transport-Security max-age=15768000 always;
location / {
include /etc/nginx/proxy_params;
proxy_pass http://10.0.0.2:80;
}
}
Change domains and IP to taste.
Best regards,
Johan Ehnberg
On 4/15/19 11:19 AM, Mathew Perry wrote:
Hi
i'm using latest backuppc and want to connect emotely to it. I have nginx on
another host, not on same host where backuppc is running on.
So, i'm struggling to get the nginx config working to connect to the backuppc
host. The configs on the internet are all for nginx configs if backuppc and
nginx are on the same host.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
