 |
Screenshot from 2015-03-19 16:05:35.png (105,734 bytes) |
|
|
Screenshot from 2015-03-19 16:05:25.png (146,507 bytes) |
|
|
Looks like a misconfiguration, as far as I can see from the screenshots. If you followed the install instruction (https://github.com/bareos/bareos-webui/blob/master/doc/INSTALL.md) and you have just one director with the catalog db running on the same host, your directors.ini should look similar like following. ; ; Section bareos-dir ; [bareos-dir] enabled = "yes" dbdriver = "postgresql" dbaddress = "bareos" dbport = 5432 dbuser = "bareos_webui" dbpassword = "changeme" dbname = "bareos" diraddress = "bareos" dirport = 9101 ; Note: TLS has not been tested and documented, yet. ;tls_verify_peer = false ;server_can_do_tls = false ;server_requires_tls = false ;client_can_do_tls = false ;client_requires_tls = false ;ca_file = "" ;cert_file = "" ;cert_file_passphrase = "" ;allowed_cns = "" Note: If you try to login even though the config test informs you about not being able to connect to the catalog db, you have to logout or close your browser to get rid of the session. Otherwise changes made to your directors.ini during session time are not applied. As there is no logout button if you run into the exception, you may call the needed action to logout via following url or simply close your browser to kill the session. http://<replace-with-your-host>/bareos-webui/auth/logout |
|
|
Thanks, you were right, this was just browser cache... |
- Anonymous
