search

jitsi / docker-jitsi-meet

Jitsi Meet on Docker
https://hub.docker.com/u/jitsi/
Apache License 2.0
3k stars 1.34k forks source link

HTTPS Not Sure and unsafe issue with URL #1806

Open linkzeeshan opened 2 months ago

linkzeeshan commented 2 months ago

Can you guide me how can I resolve https not secure issue. SSL is registered on my domain. but still not secure issue is coming.

I purchased VM on Azure and domain purchase to another platform.

saghul commented 2 months ago

What public URL are you using?

linkzeeshan commented 2 months ago

Public URL currently I am using domain name like PUBLIC_URL = https://(domain name)

saghul commented 2 months ago

Test your domain here: https://whatsmychaincert.com/

linkzeeshan commented 2 months ago

Please check screenshot.

meet2.medchois.com is self-signed. It doesn't have a chain certificate and will never be trusted by clients.

image

damencho commented 2 months ago

Have you enable the 3 let's encrypt settings? https://github.com/jitsi/docker-jitsi-meet/blob/731d6d13b88b9c74877312f2f0d0250e9894de18/env.example#L60

linkzeeshan commented 2 months ago

damencho I checked this #ENABLE_LETSENCRYPT=1 It was commented.

I uncommented now page is not loading please check below screenshot image

saghul commented 2 months ago

Check the web container logs.

damencho commented 2 months ago

damencho I checked this #ENABLE_LETSENCRYPT=1 It was commented.

You also need the following two, the domain and email.

linkzeeshan commented 2 months ago

saghul damencho All done but still same issue is coming

let me try to explain you what I am doing

1- site is working once I set below configuration

PUBLIC_URL = https://IP-address ENABLE_LETSENCRYPT, domain and email. all option are commented

2- site not working once I enable below following options
ENABLE_LETSENCRYPT = 1 LETSENCRYPT_DOMAIN=domain name LETSENCRYPT_EMAIL= email

damencho commented 2 months ago

PUBLIC_URL = https://IP-address This should be https://domain name.

You should have a valid DNS for that domain name in order Let's Encrypt to reach your server and allow you to have valid certificates, it also needs port 80 to be accessible on your deployment. As Saul said you can see more information on what went wrong with the certificates in the logs of the container.

linkzeeshan commented 2 months ago

Thanks. saghul damencho I assigned PUBLIC_URL Value is my domain name https://domain/

Please check below log SC.

image

linkzeeshan commented 2 months ago

image

saghul commented 2 months ago

Is the domain DNS pointing at the correct IP address and are ports 80 and 443 forwarded to the docker host?

linkzeeshan commented 2 months ago

saghul Yes! both are activated

saghul commented 2 months ago

Please share the full .env file.

linkzeeshan commented 2 months ago

saghul Please find attached screens shot image

saghul commented 2 months ago

Is your public URL correct in your file?

On a previous screenshot I noticed you are running Docker as root. Don't, use a regular user please.

Even if LE fails, are you able to access the site over plain http?

linkzeeshan commented 2 months ago

No! It's not working with plain http as well.

PUBLIC_URL = htpps://meet2.medchois.com

damencho commented 2 months ago

Are you sure the ports are forwarded correctly and the traffic from the public IP reaches the running docker?

linkzeeshan commented 1 month ago

Yes! I have already opened the inbound connection, and the site is functioning properly once I set the value of PUBLIC_URL as the VM IP and commented out the other keys listed below:

ENABLE_LETSENCRYPT = 1 LETSENCRYPT_DOMAIN = domain name LETSENCRYPT_EMAIL = email

I also completed the DNS configuration for the domain name.

saghul commented 1 month ago

Hum, so it only fails when you enable let's encrypt?

Try this: put the domain in there and leave let's encrypt disabled. Does the site work, albeit with the cert error?

linkzeeshan commented 1 month ago

Yes saghul, the application functioning correctly with the configuration set as follows:

PUBLIC_URL = https://VM IP ENABLE_LETSENCRYPT = disabled

However, I encountered an issue when enabling LETSENCRYPT and changing the PUBLIC_URL to https://domain/. The application is not working in this configuration.

saghul commented 1 month ago

That's not what I asked. Try this:

PUBLIC_URL = https://domain ENABLE_LETSENCRYPT = disabled

I suspect your domain is not pointing to the right IP.

linkzeeshan commented 1 month ago

@saghul Domain is pointing my VM public IP address.

damencho commented 1 month ago

@saghul Domain is pointing my VM public IP address.

And that same IP address that you see when you do ping domain and when you put it in PUBLIC_URL = https://vm_IP it works?

linkzeeshan commented 1 month ago

Yes!

damencho commented 1 month ago

So then the ports are not forwarded from the public IP to the vm.