-
Notifications
You must be signed in to change notification settings - Fork 735
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
Using Livekite in the production environment without using a domain #1604
Comments
SSL certificate is must other than localhost if you are using browser. I don't think this restriction from livekit but browser. You can easily assign domain with SSL certificate locally. |
I use it like this: |
wss require ssl enabled. For your case should be ws. |
in our case we have to use ssl certificate with ip and the browser cannot work with http. |
As long as you have the certs figured out, livekit itself does not require any domains. SSL certs are a browser requirement. Are you seeing anywhere that requires you to provide a domain? |
in livekit document: "The SSL certificate must be signed by a trusted certificate authority; self-signed certs do not work here". |
That's stating a browser requirement. Browsers do not generally trust self-signed certs. |
Our project is implemented in the internal environment of the company and we cannot assign a domain to it. How can we use Livekit using IP in the production environment?
The text was updated successfully, but these errors were encountered: