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
TLS is too hard to setup currently and the docs are broken.
Plan
Faktory will look for /etc/faktory/conf.d/private.key and /etc/faktory/conf.d/public.crt and, if found, activate TLS. Users should create soft links from wherever TLS certs are stored into Faktory's config directory.
Certificates should be reloaded upon HUP and the server socket reopened so new connections will use the new TLS certs. Existing connections will continue to run with their existing TLS session. As workers are restarted, those old connections will go away.
The text was updated successfully, but these errors were encountered:
Keep in mind if this doesn't work for you, there's a million other ways to add TLS "in front of" Faktory. HAProxy, stunnel, or any number of other proxies can provide public TLS and forward unencrypted traffic to Faktory privately.
TLS is too hard to setup currently and the docs are broken.
Plan
/etc/faktory/conf.d/private.key
and/etc/faktory/conf.d/public.crt
and, if found, activate TLS. Users should create soft links from wherever TLS certs are stored into Faktory's config directory.The text was updated successfully, but these errors were encountered: