On 31-07-2024 12:21, Marcin Haba wrote:
On Wed, 31 Jul 2024 at 11:36, Kees Bakker via Bacula-users
<bacula-users@lists.sourceforge.net> wrote:
Hi,
It seems that Bacularis has port 9097 hardcoded somewhere.
I've setup Apache to do Bacularis. But not with the supplied
example of using port 9097. I'm just using port 433 with a proper
SSL certificate.
Bacula Dir/SD/FD were already running on this system, installed
with Ubuntu apt.
The configuration went well, I think. (I don't want Bacularis to
mess with editing the Dir/SD/FD configuration. Only that part was: no)
As soon as the initial setup finished the Dashboard came up.
However, it keeps popping up
Error code: 100
Message: Problem with connection to remote host. cURL error 7:
Failed to connect to localhost port 9097 after 0 ms:
Connection refused.
Huh? Where is that 9097 coming from? Nowhere in the settings there
is an item for this.
Hello Kees,
This port setting was in advanced options of the initial wizard. Once
the wizard is finished, this port is used on the web interface side in
API host config.
[Main menu] => [Page: Security] => [Tab: API hosts] => [Edit: 'Main'
host].
You can update it there.
For the configuration part, Bacularis has an option to use Bacula
configs in read-only mode for all or for selected Bacula resources and
Bacula components. If you are interested in, you can see it on this
video guide:
https://www.youtube.com/watch?v=ZuTsuGMEms8
Hi Marcin,
Thank you for the reply.
Indeed that seems to work. I had already found
/etc/bacularis/Web/hosts.conf which I manually changed. In my case the
host had to be the FQDN, not localhost.
So, that's working now.
--
Kees
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
