Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS Support #128

Open
MattKitmanLabs opened this issue Jul 15, 2024 · 3 comments
Open

TLS Support #128

MattKitmanLabs opened this issue Jul 15, 2024 · 3 comments
Labels
invalid This doesn't seem right

Comments

@MattKitmanLabs
Copy link

I'm having trouble getting the liveness probe to use HTTPS, any guides?

@andrcuns
Copy link
Collaborator

There is no TLS support with default server. You would have to set up a custom server and configure it to use https.

@lucastosetto
Copy link
Collaborator

@MattKitmanLabs Could you give some details about your use case, please? From what I have in mind I really don't believe this feature is needed for the purpose this gem is intended to be used.

@lucastosetto lucastosetto added the invalid This doesn't seem right label Oct 3, 2024
@MattKitmanLabs
Copy link
Author

Hi @lucastosetto,

We work in the public sector DoD IL5, all connections including pings to liveliness endpoints must be secured over TLS.

I managed to get this to work with Puma, by setting get env vars as follows:

SIDEKIQ_ALIVE_HOST: ssl://0.0.0.0?key=/mnt/secrets/certs/tls.key&cert=/mnt/secrets/certs/tls.crt
SIDEKIQ_ALIVE_SERVER: puma

But I tried to clean up our puma.rb config file by creating one for DoD use and one for commercial, but I can't seem to pass any configs to puma like -C config/puma_gov.rb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants