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
{{ message }}
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
Hi there, I have successfully deployed the Jambonz with kubernetes helm charts on GKE Cluster (chart version 0.1.33). I'm trying to follow the instructions on github to configure jambonz to use sip over websockets.
Here is my Issuer:
huyquangng258@cloudshell:~$ kubectl get issuers -n jambonz -owide
NAME READY STATUS AGE
ca-issuer True Signing CA verified 4h29m
,and my Certificate:
huyquangng258@cloudshell:~$ kubectl get certs -n jambonz -owide
NAME READY SECRET ISSUER STATUS AGE
drachtio-certificate True jambonz-secrets ca-issuer Certificate is up to date and has not expired 5h3m
When I want to use my cert and set the config sbc.sip.ssl.enabled to true, The problem I'm having here is SIP pod is always in CrashLoopBackOff state:
@huyhuy8122001 same issue on my k3s
i m requesting certs from LetsEncrypt, so for me solution
DRACHTIO_TLS_CHAIN_FILE env variable equal to /etc/ssl/tls.crt
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there, I have successfully deployed the Jambonz with kubernetes helm charts on GKE Cluster (chart version 0.1.33). I'm trying to follow the instructions on github to configure jambonz to use sip over websockets.
Here is my Issuer:
,and my Certificate:
When I want to use my cert and set the config
sbc.sip.ssl.enabled
totrue
, The problem I'm having here is SIP pod is always in CrashLoopBackOff state:Logs for SIP pod:
Pod Describe here:
Am I missing any steps here?
The text was updated successfully, but these errors were encountered: