You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this in my logs, like its attempting to load the TLS certs despite them not being defined
[2024-05-08 20:19:28.246] ERROR[18]: io_tls.c:922 tls_ctx_create: Could not load certificate file : error:80000002:system library::No such file or directory
tls.conf
; tls.conf
[tls] ; Configures the TLS certificate used by any BBS modules that use TLS
; If you use Let's Encrypt with certbot, run "certbot certificates" to show which domains use which certs
; This section configures the default certificate, used prior to receiving any Server Name Indication.
; These arguments are MANDATORY if you wish to enable any TLS servers.
; If no Server Name Indication is provided by the client, this is the certificate that will be used.
rootcerts=/etc/ssl/certs/ca-certificates.crt ; Root certs file used for verifying TLS certificates.
; (should work for Debian-based distros; change accordingly if needed).
;cert=/etc/letsencrypt/live/example.com/fullchain.pem ; TLS certificate
;key=/etc/letsencrypt/live/example.com/privkey.pem ; TLS private key
[sni] ; Optional: Server Name Indication is used to support TLS on multiple hostnames.
; If you are supporting multiple hostnames, add pairs of hostnames here with format hostname=cert:privkey, e.g.
; example.com=/etc/letsencrypt/live/example.com/fullchain.pem:/etc/letsencrypt/live/example.com/privkey.com
; If no match exists for a provided SNI, the default certificate will be used.
The text was updated successfully, but these errors were encountered:
I noticed this in my logs, like its attempting to load the TLS certs despite them not being defined
tls.conf
The text was updated successfully, but these errors were encountered: