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 <michael.st...@member.mensa.org> 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 <michael.st...@member.mensa.org> 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 <mamema2...@hotmail.com> 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 <michael.st...@member.mensa.org> 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-2Fj_Q2BGfwJU8u9mDfqnb474-2Bm-2BL0ENYR9YjE6KbossIoX5BsgParPAIJc-2BXhN4yHBTvu6JLHaVGCKCmPYj3IK7btkGDkp27mahUcX-2BRaMthIGgy8PRNsCSgcly3na4haimU6ZCkHFX-2Bi-2B1Dl-2B5XHPs5PHJf7zQDpQNFS35-2Bc9fnLPM7Z9Xj9NaHVNqdovQabtXa09aCraGaqeWZ0WrL1CjtVuo2kZRFgKdtKYviPFifr-2Fo-3D> (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://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
