I know what your problem is. You need a Bacularis API instance. Bacularis web connects to a Bacularis API instance, which connects to the bacula director. Right now you only have a Bacularis web instance.
If your bacula instance is entirely bare metal, not in a container, then you probably don't want to use containers to install Bacularis, or at least don't want to use containers for the Bacularis API. I recommend installing Bacularis api + web on bare metal in that case. There is not a container featuring a Bacularis web instance with a Bacularis API instance but NO bacula components. I don't know why this is the case. The various containers that do exist support a number of different circumstances where Bacularis is being used to manage a distributed, modular bacula system. There isn't a single container that only contains the functionality and packages to support Bacularis management of an existing bare metal bacula instance. Robert Gerber 402-237-8692 r...@craeon.net On Tue, Apr 9, 2024, 4:06 PM Thing <thing.th...@gmail.com> wrote: > Hi, > > What am I missing here to connect my bacularis-web container to the > bacula-director pls? > > > https://imgur.com/a/No8S74f > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
