My site is not working after installing TLS

[allsolution]

I configured apache and web site is working fine with 80 port. After installing
TLS: I can't access my website.
My domain is: email.mydomain.net
I ran this command: sudo certbot --apache --agree-tos --redirect --hsts --staple-ocsp --email myemail@email.com -d email.mydomain.net
Then installed successfully.
[sudouser@centos conf.d]# ls
mydomain.conf mydomain.net-le-ssl.conf
1st one is I created 2nd one is created by certbot.

My web server is (include version): Apache 2.4

The operating system my web server runs on is (include version): Centos 8

I can login to a root shell on my machine.

The version of my client: certbot 1.22.0

Should I create new conf file like email.etc.com.conf?

[Bruce5051]

Here is a list of issued certificates crt.sh | email.[redacted]

However this is the certificate the is currently being served

[Bruce5051]

If I accept Firefox's warning I can access the site with https

Where trying with http I see this

http does not seem to redirect to https

https has no redirect

[allsolution]

So it comes to firewall from outside. I didn't know because I am from internet lan with this firewall. So what is the solution for this do you think?

[Osiris]

@allsolution

So what is the solution for this do you think?

Well, if requests for HTTPS aren't getting to your own webserver, but are getting "stuck" at some firewall, then you need to ask your network operator on how to proceed I think. Having a Let's Encrypt certificate sitting on the server somewhere "deep" inside the network without someone being able to access it, is kinda useless unless the HTTPS requests are able to actually get to it

[JimPas]

You may want to add Listen 80 in a line below NameVirtualHost *:80 and add Listen 443on a line after NameVirtualHost *:443. Oh, and for your ServerNameand ServerAlias, add your domain and the www version to those respectively.

Check your redirects in your conf files. Make sure you are redirecting to http to https with the same domain name before you redirect to another domain.

| [redacted] |• ns1.dns.mn / 67m63 | 162.251.82.122
Burlington/Massachusetts/United States (US) - Cloudflare, Inc.|

A check on your apex domain of [redacted] shows a redirect to http://eincenter.police.gov.mn/. BUT! There is a problem with that as well. It times out.

Domainname	Http-Status	redirect	Sec.	G
• http://eincenter.police.gov.mn/
103.17.108.169	-14		10.060	T
Timeout - The operation has timed out
• http://www.eincenter.police.gov.mn/
103.17.108.169	-14		10.040	T
Timeout - The operation has timed out
• https://eincenter.police.gov.mn/
103.17.108.169	-14		10.033	T
Timeout - The operation has timed out
• https://www.eincenter.police.gov.mn/
103.17.108.169	-14		10.030	T
Timeout - The operation has timed out

One good response: https://police.gov.mn does load properly.

1. Check your redirects for all those subdomains on both apex domains, redirecting each subdomain from http to https (do www separately); then

2. you can redirect from one domain to another (https);

3. Check your Cloudflare setup. These connections presently are all timing out. Sometimes it's just a matter of changing a few settings in Cloudflare to get back up and running. Check with their customer support also.