If you're using Apache HTTPd it's pretty straightforward. A rough outline 
for RHEL 9, assuming you already have Bareos Web UI working via HTTP:

   1. Install mod_ssl and dependencies
   dnf install mod_ssl
   2. Configure firewall
   firewall-cmd --zone=public --add-service=https
   firewall-cmd --zone=public --add-service=https --permanent
   3. Place a certificate and key in /etc/pki/tls
   4. Edit /etc/httpd/conf.d/ssl.conf
   ServerName name.on.your.cert.example.com
   SSLCertificateFile /etc/pki/tls/certs/name.on.your.cert.example.com.crt
   SSLCertificateKeyFile /etc/pki/tls/private/
   name.on.your.cert.example.com.key
   SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
   5. Restart HTTPd
   systemctl restart httpd

Josh
On Thursday, February 15, 2024 at 4:37:47 AM UTC-5 Bruno Friedmann 
(bruno-at-bareos) wrote:

> Hello Markus,
>
> I hope you noticed in Bareos documentation, that connection between 
> php-fpm (webui) and the director had to be unencrypted (due to missing 
> tls-psk support in upstream php-curl module).
>
> But to have https and as such tls connection between your browser and the 
> webui you will have to find how to activate ssl/tls module for your 
> favorite httpd server on your distribution.
> Globally it means activate the encryption module on the webserver and 
> install a certificate.
>
> Hope this will drive you to a solution.
> Le mardi 13 février 2024 à 14:28:00 UTC+1, Markus Dubois a écrit :
>
>> Hi,
>>
>> i've enabled TLS between dir-sd-client. I've also configured the web-ui 
>> according to the docs (directors.ini)
>> tls between sd-dir-client is working,
>> but i've been struggling to get the web ui response to https, it is still 
>> http
>> any hints? 
>>
>> best regards
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/af16123b-a01b-426b-9c6d-ecfc9642e931n%40googlegroups.com.

Reply via email to