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/
