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 <michael.st...@member.mensa.org>
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/
