Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
1.) i do not even know what your talking about. Haven't tried. I do not want to
touch BackupPC cause it was difficult to make it work as it is.
2.) tried. Nothing changed. Same result.
From: Michael Stowe
Sent: Friday, April 19, 2019 1:31 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-19 06:11, Mathew Perry wrote:
one step further. I now can access the web interface partly. difficult to
describe. everything is top down scrollable, over 3 pages downwards. no css or
so formating.
-
FROM: Michael Stowe SENT: Friday, April 19,
2019 5:25 AM 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-19 02:41, Mathew Perry wrote:
…and just for the record switched backend to https at the very moment:
Outcome: The Requested URL /BackupPC_Admin was not found on this
server
-
FROM: Mathew Perry SENT: Friday, April 19, 2019 1:25
AM TO: General list for user discussion, questions and support SUBJECT: Re:
[BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
404 NOT FOUND
I know you're trying to help, which is very nice, but be advised that
over this nginx server about 20 services are running and working. backends
behind nginx are both http or https. As for example chrome is using HSTS, the
domain runs https for a long time.
I don't think that i need to change a whole working and running nginx
conf on higher level than on the backuppc directive.
-
FROM: Michael Stowe SENT: Thursday, April 18,
2019 7:39 AM 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-18 01:40, Mathew Perry wrote:
hmmm… no!
The Requested URL /BackupPC_Admin was not found on this server
FYI: the url which “comes back” from nginx looks like:
https://domainname/BackupPC_Admin<https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7T8nrzTGGnwx9UNS1WVjQxnVSBGmhdBbJoi5j5f7UDEJ_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX5BsgParPAIJc-2BXhN4yHBTvBztaNgDKke6kqwxoAiOiubyARRiQdgwFnrWGCkiKEeaxuYRDjtYiTBLtvXb3Pds-2BT1vQyPPYiY9mzrUayLIG4PKyWDkuV7oVADmBN3Dd9s38tWCQY30AkCBqYo35AKwHnh6ake2Q0QpmphqeQN7x46jrPkGM-2F74FnP6BtfYK-2F00-3D>
[1] [1]
nginx testet internally (LAN) and externally. Same result
And what happens when you navigate to
http://domainname/backuppc/BackupPC_Admin?<https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX5BsgParPAIJc-2BXhN4yHBTvKmRwIzEnuqPeaDwqBJzd00SQZHQez6SFBJMWMEfkZTGdrradhAfGQIqyrdtDrY3cbr2AYONRH00Bav0uHu7mK0888svtgO9UUlsry-2FaSQ-2Bg7zdjrMrW4QKb5PSzETwhiMmQRleiWcrHPDWnsXodkKOJKQ8QNUXpIxOMqGA7mlMU-3D>
[2] [1]
Also, have you actually set up the back end for https?
To clarify: I don't think it's an http/https problem, but it's worth ensuring
that you're matching what works on the host side.
At any rate, have you tried:
location /BackupPC_Admin {
proxy_pass
http://ipaddress:port/BackupPC_Admin<https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanymOLCu-2BVSO75-2FnYwJXg-2FV4e-2B28ucf3rSWzrrbMJduJe-2F_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX5BsgParPAIJc-2BXhN4yHBTv-2B8L8MEcgSO54BKzMolvk8XfaBArQJqaBD6v5A0np8DHhgQLHtN6gbYsjUP5eI8Q-2Bms5I1ukH9y2mcU7psmibYkUwzYGN-2FyzeY4oTo3sD1qA41eMLFqXM0H4b6fYbWF9irkxCxHSvOWJxPmcLWuLvZtQQPUWqowVjWAGmJHwHAHA-3D>
[3]; }
That's good — so we know that proxying itself is working, but there's something
goofy going on in the redirect/rewrite. (Yes, it sounds like where we started.)
At any rate, two things worth bringing up:
1) Have you tried scgi_pass instead? It removes one step between nginx and
BackupPC. I don't know that it will solve your problem, but at least it's worth
being aware that you don't actually need an http server on the back end.
2) I don't know why the default proxy_redirect wouldn't be behaving itself, but
it clearly isn't. You may just want to make this explicit:
proxy_redirect off proxy_redirect default proxy_redirect
http://backend/<https://u2182357.ct.sendgrid.net/wf/click?upn=YahQ8tVjTExAt0gOS-2Bui2HSH9NT15auMwLJik22QXzw-3D_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX5BsgParPAIJc-2BXhN4yHBTvSyVqbHo4mse-2FPqo0GzyI20IkN6AtDjajg0DZM-2BsUYpwqVzIkvDi0f1zbCwYBT1ih-2BJ-2FqPEzGf72tNOgK-2FIFDTdxLhQnz4xWoL4gdJawCHieNcWLtb37UgVJiJv3aD-2FQ2G2EiK-2BPmiW4UCnxTO30dFoc31kOU1q64bDgi7zK9slI-3D>
http://frontend/backuppc/<https://u2182357.ct.sendgrid.net/wf/click?upn=qCUd6WcJ5OOirVHNEJOdx3XSC1QOgTCDRYnVJypQwOOMQMWSeLTfhLAVAPhpR1-2
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
On 2019-04-19 06:11, Mathew Perry wrote:
one step further. I now can access the web interface partly.
difficult to describe. everything is top down scrollable, over 3 pages
downwards. no css or so formating.
-
FROM: Michael Stowe
SENT: Friday, April 19, 2019 5:25 AM
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-19 02:41, Mathew Perry wrote:
…and just for the record switched backend to https at the very
moment:
Outcome: The Requested URL /BackupPC_Admin was not found on this
server
-
FROM: Mathew Perry SENT: Friday, April 19,
2019 1:25 AM TO: General list for user discussion, questions and
support SUBJECT: Re: [BackupPC-users] Fwd: Re: backuppc behind nginx
which is on another host
404 NOT FOUND
I know you're trying to help, which is very nice, but be advised
that
over this nginx server about 20 services are running and working.
backends behind nginx are both http or https. As for example chrome
is using HSTS, the domain runs https for a long time.
I don't think that i need to change a whole working and running
nginx
conf on higher level than on the backuppc directive.
-
FROM: Michael Stowe SENT: Thursday,
April 18, 2019 7:39 AM 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-18 01:40, Mathew Perry wrote:
hmmm… no!
The Requested URL /BackupPC_Admin was not found on this server
FYI: the url which “comes back” from nginx looks like:
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7T8nrzTGGnwx9UNS1WVjQxnVSBGmhdBbJoi5j5f7UDEJ_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CtHqx5ajFKrIeEAMj67C-2FkYZTfB4c6svpzlmD5aShbi8PRTCt9qZsUXkwXQk48NyHdZiYE5NgidiQjbuMjy-2FMSxNopfjI6SR6MgSrVA8ZTmmsCBE-2FHu4CyKwJUXvjLeATdd05cYm-2Fe4Ui49nzO9OQHSHaNdNmWqNdNu-2Ftv4jhlh813W0Lg0ntRiFnigIfw6bs
[1] [1]
nginx testet internally (LAN) and externally. Same result
And what happens when you navigate to
https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CtHqx5ajFKrIeEAMj67C-2FkYzYtahxwXHsQCgpCInZBJ8OmEWNAriW0H3iFXN4DKYg0-2Bkz3AWdChNzU5qjNgYnWjcdHqfPJGzE67P3IYbavJ-2BbLPQtyWo1rgLFGdt-2FuvWFTRu1rzLHaem0-2F5YdXFb97EjYJKbeCGSSljpXj-2FsN712g-2BHSKbaUYqajfqTrRqrbr
[2] [1]
Also, have you actually set up the back end for https?
To clarify: I don't think it's an http/https problem, but it's worth
ensuring that you're matching what works on the host side.
At any rate, have you tried:
location /BackupPC_Admin {
proxy_pass
https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanymOLCu-2BVSO75-2FnYwJXg-2FV4e-2B28ucf3rSWzrrbMJduJe-2F_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CtHqx5ajFKrIeEAMj67C-2FkbdmzmsxJIXCKDZPIEFsi7XhcRK1qs7-2FyaMSbiB8OB7nwDVKL5zYN8CarktZhKqVmGwVlAd557-2FpdTHnpHHHY2mkajjeLDkq5vsWQTCKI0DVz6Lai1kpbvN-2BFn1UinWGMDedawwF26pgxcKN9jVapOIPlIuiguI4vmhiAfOSTsXY
[3]; }
That's good -- so we know that proxying itself is working, but there's
something goofy going on in the redirect/rewrite. (Yes, it sounds like
where we started.)
At any rate, two things worth bringing up:
1) Have you tried scgi_pass instead? It removes one step between nginx
and BackupPC. I don't know that it will solve your problem, but at
least it's worth being aware that you don't actually need an http server
on the back end.
2) I don't know why the default proxy_redirect wouldn't be behaving
itself, but it clearly isn't. You may just want to make this explicit:
proxy_redirect off
proxy_redirect default
proxy_redirect
https://u2182357.ct.sendgrid.net/wf/click?upn=YahQ8tVjTExAt0gOS-2Bui2HSH9NT15auMwLJik22QXzw-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CtHqx5ajFKrIeEAMj67C-2FkUG7NmDKMSEU7PilrxT3OH65Vshj3AhW5ePICO-2FDzpfkLPaDmNLNDkhqAW3HrUEQl7JrbLx02LOU1Tu01GGzWqUimqovmDR4VRCIoqHBotal-2FozNYvwNekmtSa8a5aly25VOr4dlXIwqNLp20MzngzOFsn89o9XLqVCOhM0ajfWy
https://u2182357.ct.sendgrid.net/wf/click?upn=qCUd6WcJ5OOirVHNEJOdx3XSC1QOgTCDRYnVJypQwOOMQMWSeLTfhLAVAPhpR1-2Fj_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CtHqx5ajFKrIeEAMj67C-2FkRNTVIOldWA4lG4lSUjuccGDrEgvZ-2F9pCQFtQNDubBQLcGsfBRVjfsXb5R-2F3gmju7yJGutjlKh95SN0TSeIDmA3aOrAWfRoGXeaJaOUlP7XoJ93RPwRDnsWw8QBeUwTwQODlnKiLPuZKbWyG4P2KpqSO5ihDdxYs9w1qVT487BT-2B
(Order is important, of course, and the point of off and default is to
rule out global rules which are taking precedence.)
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
one step further. I now can access the web interface partly. difficult to
describe. everything is top down scrollable, over 3 pages downwards. no css or
so formating.
From: Michael Stowe
Sent: Friday, April 19, 2019 5:25 AM
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-19 02:41, Mathew Perry wrote:
…and just for the record switched backend to https at the very moment:
Outcome: The Requested URL /BackupPC_Admin was not found on this
server
-
FROM: Mathew Perry SENT: Friday, April 19, 2019 1:25
AM TO: General list for user discussion, questions and support SUBJECT: Re:
[BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
404 NOT FOUND
I know you're trying to help, which is very nice, but be advised that
over this nginx server about 20 services are running and working. backends
behind nginx are both http or https. As for example chrome is using HSTS, the
domain runs https for a long time.
I don't think that i need to change a whole working and running nginx
conf on higher level than on the backuppc directive.
-
FROM: Michael Stowe SENT: Thursday, April 18,
2019 7:39 AM 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-18 01:40, Mathew Perry wrote:
hmmm… no!
The Requested URL /BackupPC_Admin was not found on this server
FYI: the url which “comes back” from nginx looks like:
https://domainname/BackupPC_Admin<https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7T8nrzTGGnwx9UNS1WVjQxnVSBGmhdBbJoi5j5f7UDEJ_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX7C-2B-2BJQO3jKmunLub-2F3Cg-2BKeccmhIHSPEHetSJdcV8nhM1L8L2KT-2BDjt7uD1Zzumro-2F8n-2FgXUs5qUCLhMagZt8sEtpKQoxu4i4xTNlnYHms60RDrXFLwf2RGzFf0mBnS4DnlMOKqWUgKwttQ5hxs3q7E7AKPWKXeHTZN4ZABps9lAeUcvzefYfrz7dlXyF-2Fxpg-3D>
[1]
nginx testet internally (LAN) and externally. Same result
And what happens when you navigate to
http://domainname/backuppc/BackupPC_Admin?<https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX7C-2B-2BJQO3jKmunLub-2F3Cg-2BK-2BRYwxOEQnqZbr34E2Outv1c5dlNs-2Fqrf84zDOjoXzpeHRDkxe99kh3-2FA5ca-2F3WpGG-2FrhoxQTjTVexPmrgZRfKlGV9916A69qy3hIrwuBZWDVLSDNvSXH1zfrThC81GGbbpZpKB8vJcPNVgHYxZzz66nUggoG6v7qoKhzvXngJHA-3D>
[1]
Also, have you actually set up the back end for https?
To clarify: I don't think it's an http/https problem, but it's worth ensuring
that you're matching what works on the host side.
At any rate, have you tried:
location /BackupPC_Admin {
proxy_pass
http://ipaddress:port/BackupPC_Admin<https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanymOLCu-2BVSO75-2FnYwJXg-2FV4e-2B28ucf3rSWzrrbMJduJe-2F_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX7C-2B-2BJQO3jKmunLub-2F3Cg-2BKz9KE-2Bxaf0GWSgKU8OLgoBE-2FG7VDKutDT7xYHrCK2CcXrwllpwxBENYNvoY-2FbZZ1SP2Yish3wxbS5uSFkfrBLpCEa1PuUVaPnQ0zUp-2FF9R6LffGQEhmg-2BVA5s9Yv8SeKgxzg5YZNapPdOo8sgZR58suSYfiDTLrW5plPVV6bVtWw-3D>;
}
___
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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
On 2019-04-19 02:41, Mathew Perry wrote:
...and just for the record switched backend to https at the very
moment:
Outcome: The Requested URL /BackupPC_Admin was not found on this
server
-
FROM: Mathew Perry
SENT: Friday, April 19, 2019 1:25 AM
TO: General list for user discussion, questions and support
SUBJECT: Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is
on another host
404 NOT FOUND
I know you're trying to help, which is very nice, but be advised that
over this nginx server about 20 services are running and working.
backends behind nginx are both http or https. As for example chrome is
using HSTS, the domain runs https for a long time.
I don't think that i need to change a whole working and running nginx
conf on higher level than on the backuppc directive.
-
FROM: Michael Stowe
SENT: Thursday, April 18, 2019 7:39 AM
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-18 01:40, Mathew Perry wrote:
hmmm… no!
The Requested URL /BackupPC_Admin was not found on this server
FYI: the url which "comes back" from nginx looks like:
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7T8nrzTGGnwx9UNS1WVjQxnVSBGmhdBbJoi5j5f7UDEJ_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CKfGiJvA1PcFpefW3bqr-2BdpF9WaxP-2Fz-2BKPwGTfcmoyofFnLfBLZ5VYphw53qYzl0gbeZuORygwmWGwDvpDlQSdNawmVkYGCuTF5dwS7DRvdIANbkAxXStctxkvXPATRktU8vxmC-2F035IClcRSAjrBOao8FWhvoG1A-2BD3zlepaz3s-3D
[1]
nginx testet internally (LAN) and externally. Same result
And what happens when you navigate to
https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CKfGiJvA1PcFpefW3bqr-2BdoC27FIaHtLukBYdeH0fOfH4TejVaEfG-2BLhAjihRo-2BphmoXvTgTJ2HAfQDEHhhua-2Bs747R1cpnyuL5ipTte1Xs8ElR6m8Xob1ayOwPQ0CyL6Vpn92Ag-2BVIFfmJchYsL3fvHVTc7Gt5ZEld7a8Mk1sCg-3D
[1]
Also, have you actually set up the back end for https?
To clarify: I don't think it's an http/https problem, but it's worth
ensuring that you're matching what works on the host side.
At any rate, have you tried:
location /BackupPC_Admin {
proxy_pass
https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanymOLCu-2BVSO75-2FnYwJXg-2FV4ediqxr1VtC8L6pBcvPM92z_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CKfGiJvA1PcFpefW3bqr-2BdsPURAPOK4uZ9PbBpJOoIHNp8szRytp4rI3pjnVfTyObKR7xW3CAaBmQyTbZwK32fG2Gp72-2BGUzk3-2BQ-2FY4Um3NjWEVhVV64Jmj-2Bz4dk12QrNfzY04GEUEYfCvwm9h7oHwwxvMvsOikkLeIgMIK62bY0-3D
}
___
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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
On 2019-04-19 01:25, Mathew Perry wrote: 404 NOT FOUND I know you're trying to help, which is very nice, but be advised that over this nginx server about 20 services are running and working. backends behind nginx are both http or https. As for example chrome is using HSTS, the domain runs https for a long time. I don't think that i need to change a whole working and running nginx conf on higher level than on the backuppc directive. - FROM: Michael Stowe SENT: Thursday, April 18, 2019 7:39 AM 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-18 01:40, Mathew Perry wrote: hmmm… no! The Requested URL /BackupPC_Admin was not found on this server FYI: the url which "comes back" from nginx looks like: https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7T8nrzTGGnwx9UNS1WVjQxnVSBGmhdBbJoi5j5f7UDEJ_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CDUbOmcsxmenBQMf51gjd4USN4gIiwaoql9mVcjNIqzj8hcBHEQlyR24336jD7LcPFz2GieWLMWjSoXdgIng8hqnkLXJDrudqTHv9huJoOsXtq-2FhKEuSZvqLfmc50I-2BNuaWquWpEoMZg48Fet0BHpkDN2ZIjxrjQwSO4G0QshyPo-3D [1] nginx testet internally (LAN) and externally. Same result And what happens when you navigate to https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CDUbOmcsxmenBQMf51gjd4TVyg-2BYdpw8kJcU9segSE0bMAvnuZ2XwltlPOPdk-2FfZu2sCjOTINw6bVpbqEzq2lDun9uFxeRfRGUJ-2FxQmbwh-2BxvGHlIjJcyE1A8lZdC-2B0hRCpyc0Ao4J5pNVwL5Qv12izJLNUCckNo7tHWcXwAOC0s-3D [1] Also, have you actually set up the back end for https? I'm not suggesting you change the working of nginx, I'm suggesting you work through the symptoms to locate what's incompatible with your setup. Thus, this question (for which I haven't seen an answer): https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1CYbZiJw-2BhyFQbv2HpLjVSQ-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CDUbOmcsxmenBQMf51gjd4XCUdNUvmSlOnuuXGa0pZHUnNjtL8IS1y2MtAlfH8qCvrZaXmNScjTxbuXfWRA1ba-2BInmooiAhkrtUa-2BfivcNooCsoQVs1WiOPRCxOGBgaHhd1NYribvpT84KhDeS9n-2FsTVMCoxei783GTq56Kxml04-3D Call it from http or https as appropriate, sure. I'm not impugning your decisions, I'm trying to understand them so that I can offer more than broad advice. ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
...and just for the record switched backend to https at the very moment: Outcome: The Requested URL /BackupPC_Admin was not found on this server From: Mathew Perry Sent: Friday, April 19, 2019 1:25 AM To: General list for user discussion, questions and support Subject: Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host 404 Not Found I know you're trying to help, which is very nice, but be advised that over this nginx server about 20 services are running and working. backends behind nginx are both http or https. As for example chrome is using HSTS, the domain runs https for a long time. I don't think that i need to change a whole working and running nginx conf on higher level than on the backuppc directive. From: Michael Stowe Sent: Thursday, April 18, 2019 7:39 AM 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-18 01:40, Mathew Perry wrote: hmmm… no! The Requested URL /BackupPC_Admin was not found on this server FYI: the url which "comes back" from nginx looks like: https://domainname/BackupPC_Admin [1] nginx testet internally (LAN) and externally. Same result And what happens when you navigate to http://domainname/backuppc/BackupPC_Admin?<https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX61qNAgblIGERahjhkrsGyQxxPV-2B5NlIv2cJXb2bnhpPfFAGjouCVoi38BELsTdSJHoZEe5RP93lBYCEuIKEEoTkfDi8K8KoVjpYLEpFPE86Pymq3v9W41tT5m8z-2BgA9IWFc-2BAlkal454XqOv-2Fk3AbpaJRPOtgNPfd2RGb51KTvqpKyq1YWVvQcWJ3qF4dVUOM-3D> Also, have you actually set up the back end for https? ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
404 Not Found I know you're trying to help, which is very nice, but be advised that over this nginx server about 20 services are running and working. backends behind nginx are both http or https. As for example chrome is using HSTS, the domain runs https for a long time. I don't think that i need to change a whole working and running nginx conf on higher level than on the backuppc directive. From: Michael Stowe Sent: Thursday, April 18, 2019 7:39 AM 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-18 01:40, Mathew Perry wrote: hmmm… no! The Requested URL /BackupPC_Admin was not found on this server FYI: the url which "comes back" from nginx looks like: https://domainname/BackupPC_Admin [1] nginx testet internally (LAN) and externally. Same result And what happens when you navigate to http://domainname/backuppc/BackupPC_Admin?<https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX61qNAgblIGERahjhkrsGyQxxPV-2B5NlIv2cJXb2bnhpPfFAGjouCVoi38BELsTdSJHoZEe5RP93lBYCEuIKEEoTkfDi8K8KoVjpYLEpFPE86Pymq3v9W41tT5m8z-2BgA9IWFc-2BAlkal454XqOv-2Fk3AbpaJRPOtgNPfd2RGb51KTvqpKyq1YWVvQcWJ3qF4dVUOM-3D> Also, have you actually set up the back end for https? ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
On 2019-04-18 01:40, Mathew Perry wrote: hmmm... no! The Requested URL /BackupPC_Admin was not found on this server FYI: the url which "comes back" from nginx looks like: https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7T8nrzTGGnwx9UNS1WVjQxnVSBGmhdBbJoi5j5f7UDEJ_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CxFeNcoCh25-2Fubo8rY9bYNs3Ku7bT-2BL9gcEFJWKWFiFj-2FhL7Fzg3rWmP-2Fk5Uy1RNQ89pK4L-2Fu2H-2F-2B7NxpdnZ0l0Dub299FjAYAOx6GUR2LllNFGgvOqt9L27Qt1VXZCZGnvbjETQXz-2F8xmQPTEUt-2FU74FU9JC-2Bn0gbduBJh22nTM-3D [1] nginx testet internally (LAN) and externally. Same result And what happens when you navigate to https://u2182357.ct.sendgrid.net/wf/click?upn=gHC-2FQ4aFf0eQjtLJSQQ-2BdZtT-2B1GrVoFn98d8hTvP5qh8-2FeTY2bBOm6Nhq8PRhzM1JS12fyMe1gWKiZkCKxHdYg-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CxFeNcoCh25-2Fubo8rY9bYNoD1xiEbyugVWedRTENls6PrQovtqBJcmIRDketR-2FO2dL3iezRi1me9fjiJvSVkJkoEXFd2Ps2DKvOTVOSCzJJe1nPR-2BmP3ODdOoCtYmoVEM-2F-2BqK0-2FMk0LXUMBvRUTg6j5RN1vmmSawurlmdXej8e-2BQ-3D Also, have you actually set up the back end for https? ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
hmmm... no!
The Requested URL /BackupPC_Admin was not found on this server
FYI: the url which "comes back" from nginx looks like:
https://domainname/BackupPC_Admin<https://www.frameworx.ch/BackupPC_Admin>
nginx testet internally (LAN) and externally. Same result
From: Michael Stowe
Sent: Thursday, April 18, 2019 12:50 AM
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-17 21:27, Mathew Perry wrote:
you explained it exactly. But i've posted my directive already. If i would know
what to do know with my nginx config, i wouldn't ask here.
Ah. Let's fix it.
This should suffice:
location /backuppc/ {
proxy_pass http://ipaddress:port/;
}
And you posted:
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;
}
The headers are superfluous and perhaps innocuous, but where the breakage
occurs here is in the proxy_redirect directives, where the first one breaks the
default redirect by telling nginx that instead of properly replacing the back
end server's url with the front end server's url, you'd like to force the front
end to use https on the wrong url. The second proxy_redirect directive turns
that off, so that instead of properly replacing the back end server's url with
the front end server's url, you'd like to just use the wrong url. I'd recommend
removing all this nonsense.
leads to: “The Requested URL /BackupPC_Admin was not found on this server”
Yes, you've specifically told it not to redirect to the proper server
i wouldn't ask here if only a proxy pass is needed
That is literally all you need, although it's possible to break the proxy pass
with additional directives.
___
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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
On 2019-04-17 21:27, Mathew Perry wrote:
you explained it exactly. But i've posted my directive already. If i
would know what to do know with my nginx config, i wouldn't ask here.
Ah. Let's fix it.
This should suffice:
location /backuppc/ {
proxy_pass
https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanyrAnO8bh02MVVnzKtEAq6iQ-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91COiLZEGT-2Bli7V3p-2F2jKE-2FjCkVx6E-2BPxPP4oLsyhDPgbYUVy64Fki9hMO6LYlb3CArUXWLH2Qrs-2FCVFaE-2F7TH7-2FLNAbyUrWh-2FtGBC4Rf2QmHNKYixVy-2FrOIvuFuIhfT79l35Sq085ChbOvMyc1oRLbsU7y6saFfiW1J4VeOYE7qtM-3D
}
And you posted:
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
https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanyrAnO8bh02MVVnzKtEAq6iQ-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91COiLZEGT-2Bli7V3p-2F2jKE-2FjDig91GlK9N0KqgtqdyVo8zz9eXBRFvw84nUj8xGVBZCN1vG0ChpN9Rr7pEoEe6kr6AdJ8G1fws-2BPC6f6GH6IJjmOYhNLieCw0yAsIPqYOM62bAESC-2B1j-2F13MOcfax2zgHNZPXl0psSZ4VTW7eg-2F7xw-3D
proxy_redirect
https://u2182357.ct.sendgrid.net/wf/click?upn=q9oknVuBMf-2FjuIJ06YpcAg-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91COiLZEGT-2Bli7V3p-2F2jKE-2FjFM0tYwnIO18E7YkiE9-2F7qvQOMt6QcsDSnYsHfl0QPP8jyCRf6987sm6GimwV36WL23xP5Hr8FF9uPBdNRbC4umXMjiGE-2FbFVeIGOB6Ec9aa8iT-2FNKZLtQgC2CAQnQ8RqXaSHJ1luc-2BHUXuvOME83rs-3D
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7SmCwE3HeriTlvqQE-2FYLnDc-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91COiLZEGT-2Bli7V3p-2F2jKE-2FjKnM-2F9M6G4WPOJN7rHvzf04JkR0YG9osUFHUrD5p-2Bntv6sRRLFah1hs-2BYU7itjIVT2TccezF5XNasBs-2F84xRJTB-2F17l3qB8IJ6v8gvTN8IwN5YkJiL573t0Vjia6kXWyLdfeSiq3XSFg9uho11tntqI-3D
proxy_redirect off;
}
The headers are superfluous and perhaps innocuous, but where the
breakage occurs here is in the proxy_redirect directives, where the
first one breaks the default redirect by telling nginx that instead of
properly replacing the back end server's url with the front end server's
url, you'd like to force the front end to use https on the wrong url.
The second proxy_redirect directive turns that off, so that instead of
properly replacing the back end server's url with the front end server's
url, you'd like to just use the wrong url. I'd recommend removing all
this nonsense.
leads to:
"The Requested URL /BackupPC_Admin was not found on this server"
Yes, you've specifically told it not to redirect to the proper server
i wouldn't ask here if only a proxy pass is needed
That is literally all you need, although it's possible to break the
proxy pass with additional directives.
___
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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
you explained it exactly. But i've posted my directive already. If i would know what to do know with my nginx config, i wouldn't ask here. From: Michael Stowe Sent: Wednesday, April 17, 2019 2:57 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-16 05:39, Mathew Perry wrote: it does without nginx internally (direct access of the backuppc host via http:\\internalname or ip:port but through nginx neither internally nor externally (split dns running – same domain name – fyi) backuppc isn't accessible. - FROM: Michael Stowe SENT: Tuesday, April 16, 2019 4:40 AM 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-16 01:23, Mathew Perry wrote: 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 Hang on — if the local UI doesn't work, it won't work through a reverse proxy. So if BackupPC is on Server “A” and nginx is on Server “B”, Server “A” really needs to be serving up the UI first. Sorry for the top-posting/non-top-posting combination; I know it can make a thread hard to follow. At any rate, it's best to work through step-by-step. A straightforward reverse-proxy shouldn't need any changes to the base URL of the host service unless you're trying to move it up in the hierarchy. (If so, that's a whole different set of issues to contend with. One of the ways to solve this problem is to change the hierarchy in the host server, but this usually isn't necessary.) Assuming the host server is working, if you're having problems navigating between pages, then the issue is that your transparent rewrite rules aren't set up properly. Another way to solve this is to make the server think it's actually part of the nginx server (I believe this is what you mean when you're talking about the base URL) but it doesn't work when the server dynamically self-references, and is generally a poor practice as it breaks the host server. If this is the case, you need to implement a transparent rewrite rule instead. ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
it does without nginx internally (direct access of the backuppc host via http:\\internalname or ip:port but through nginx neither internally nor externally (split dns running - same domain name - fyi) backuppc isn't accessible. From: Michael Stowe Sent: Tuesday, April 16, 2019 4:40 AM 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-16 01:23, Mathew Perry wrote: 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 Hang on — if the local UI doesn't work, it won't work through a reverse proxy. So if BackupPC is on Server “A” and nginx is on Server “B”, Server “A” really needs to be serving up the UI first. ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
On 2019-04-16 01:23, Mathew Perry wrote: 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 Hang on -- if the local UI doesn't work, it won't work through a reverse proxy. So if BackupPC is on Server "A" and nginx is on Server "B", Server "A" really needs to be serving up the UI first. ___ 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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
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
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
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
TO:
Mathew Perry
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/
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
https://u2182357.ct.sendgrid.net/wf/click?upn=OIcehkuoae0CzVKCEzanyrAnO8bh02MVVnzKtEAq6iQ-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91ClCxQ1Qsn89oEtKqFdiYBtl93CUqCAPaeb2zgXoldnEbTgpCzAUVKZxXb-2B4JzRy1cK1m0NXJBgFz5JQ-2FM0LzSw1eqHjeHCpf42fU-2FTxXB2fFB16f4P-2F-2FkcjwBabI1woU40tZq8bWR4TZXTRGzhMSNJXoH-2Ffrt-2B1LtI-2Bh2OQKz0Uc-3D
proxy_redirect
https://u2182357.ct.sendgrid.net/wf/click?upn=q9oknVuBMf-2FjuIJ06YpcAg-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91ClCxQ1Qsn89oEtKqFdiYBtt2iAyFgLJ6VjTyV3i13b8yYL9INm7q2JrvP8lpPl8pq8izVHGLF5UBqDxf7VWnjbD9ThQ7XSg8CpkGNLRbXYpYhMaPeU66DdpxdmhAyOWWhs5LLg2dgczwUg3G0ClLiNhkSgWxrBUUbJfFrd0Z4ILw-3D
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7SmCwE3HeriTlvqQE-2FYLnDc-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91ClCxQ1Qsn89oEtKqFdiYBthz3Oq3LUsj9ziTBIFHGqG8g-2BLR2rvBx-2BNIhUPDGo72MjNFqZURIBLNO1JEQc7OI3ZDH1jCV9bBryhqms7A8RXyhjKz0dGsKHx3Vg-2FYFOBcfscujazm4UQG1HjDAQdatSgMryiwPMRc9HnMz0Flmafc-3D
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
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
TO:
Mathew Perry
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://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7TC34CkM-2FTKiyIQzRymkOx1xdqYC5E3Bp3F7k5LtuoC1_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91ClCxQ1Qsn89oEtKqFdiYBtoa1ObICDPceySbFC-2F3ih5oq3hg-2FkhYIFcNLmvtIBTmGJJe-2F964lNoHAGDnQds-2Fxmlmr9hfr8PAnq56dnLpCgZL5RBs5scEWSsAWx7xIQObJ5hyDJUkTJjeuRTt1isxmmyWe7fiR7n4YUy3CEuFPPHU-3D
[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
https://u2182357.ct.sendgrid.net/wf/click?upn=phT9o-2FIE-2FsNYgBy7FoncRJHlffvAv5mRzpSKVBf1eks-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91ClCxQ1Qsn89oEtKqFdiYBtvnoP96JWsBx1dwm70lKh1zzUcqxeAQNaLSoPvQ9dfIrrZnNcRr05ee0t-2FR3FdRd8lxdgqUdATk9ipwA8i7gPy7-2FUUrBB-2BZSCAYtk1f9Dv-2BEHGLuJs4Gjckc0Ep65-2BGe-2B1LT8mFDiq171-2BtGkJjqLJg-3D
}
}
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/
Re: [BackupPC-users] Fwd: Re: backuppc behind nginx which is on another host
it's not that easy
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
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 <mailto:jo...@molnix.com>
To: Mathew Perry <mailto: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;
}
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<mailto: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/
--
Johan Ehnberg
Founder, CEO
Molnix Oy
jo...@molnix.com<mailto:jo...@molnix.com>
+358 50 320 96 88
molnix.com<https://molnix.com>
[cid:part9.BB5D5B34.86CDBD56@molnix.com]
The contents of this e-mail and its attachments are for the use of the intended
recipient only, and are confidential and may contain legally privileged
information. If you are not the intended recipient or have otherwise received
the e-mail in error, please notify the sender by replying to this e-mail
immediately and then delete it immediately from your system. Any dissemination,
distribution, copying or use of this communication without prior and explicit
permission of the sender is strictly prohibited.
Please consider the environment - do not print this e-mail unless you really
need to.
___
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/
