App won't connect to jitsi server on my PC

In my text msg box on my Android, this is the link for the meeting:

https://tomsmeetings.com/silvercrest

When I tap that link, I get:

this site can’t be reached
tomsmeetings.com refused to connect

My web server is apache running under Debian.

There is nothing in the jitsi, prosody, or apache logs which indicates that the app has tried to reach the server.

I can connect to tomsmeetings.com using Chrome on the PC. There are lots of entries in the logs for this activity.

Check you’ve got your TLS full chain set up correctly - although I’d have thought you’d see an error in apache’s ssl_error.log.

I’ll look again in the Apache logs for error messages.

I ran the script to set up the certifications but got an error. It couldn’t verify my DNS, although when I use the DNS to access my machine, Apache responds with its vanilla greetings page.

Thanks again for your help.

Sounds like it’s not handling the request to /.well-known correctly.

Do you mean that the script has a problem?

I thought jitsi-meet installed nginx, not apache2, but I don’t know for sure.

If Apache is already present – which is the case with most Debian installs - the Jitsi installer will use it. That’s my impression anyway.

What does “well-known” mean?

Hi Neil brown
I have a problem in connection in android with jitsi in local network with self signed certificate?
Can you help us how to connect android with jitsi server?

It’s part of the ACME protocol. One of the ways that Let’s Encrypt attempts to verify that you control the domain in question is by writing a string to the /.well-known directory, and the read it from the LE service (via http or https).

is there a work-around?

Check what your apache config is doing with requests to ./well-known, to make sure they are going somewhere readable (probably /usr/share/jitsi-meet, but I can’t check right now).

OK. Thanks again.

Last night I posted that “when I use the DNS to access my machine, Apache responds with its vanilla greetings page.”

Checking this morning, I find that this is NOT the case. What I actually get is " This site can’t be reached
tomsmeetings.com refused to connect."

You’ve got your A record set to 192.168.0.2. Is that intentional?

that’s the IP address of my laptop, which has the server on it.

that’s the IP address of my laptop, which has the server on it.

Fair enough — just checking it was intentional!

What happens if you go to 192.168.0.2 in your browser? Does that connect?

What happens if you run this:

curl -iv tomsmeetings.com

?

And this (on the laptop):

ifconfig

?

What happens if you go to 192.168.0.2 in your browser? Does that connect?

From laptop, if http, i get apache server page. If https, I get:

This site can’t be reached
192.168.0.2 refused to connect

From Android, I get “can’t be reached” for both http and https.

BTW, on the laptop for https://tomsmeetings.com, I get the blue Jitsi “Start a new meeting” page. For http, I get the apache page.

What happens if you run this:

curl -iv tomsmeetings.com

?

On the laptop, I get the output in the attached file (curl.http.txt). If I do ‘curl -iv https://tomsmeetings.com,’ I get output in curl.https.txt.
I have termux on my Android, but it doesn’t want to install curl. Same for wget.

And this (on the laptop):

ifconfig

?

Also attached.

What time zone are you in?

curl.http.txt (10.7 KB)

curl.https.txt (1.5 KB)

ifconfig.txt (1.3 KB)

Do you prefer command output inline or in attachments?

somehow i didn’t send the response to your questions as a response to you.