Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
There's no reason to expect it would. You told certbot to obtain a cert, not to configure your web server (whatever it is--which isn't Ubuntu) to use that cert to serve HTTPS. You'll need to do that.
This option does exactly that, as Dan already said: you only get the cert. The rest (i.e.: actually installing/using the cert) is up to the user.
By the way:
Is there a specific reason why you're using the standalone authenticator when you have a perfectly fine webserver Apache running on that host, apparently? Which was probably also the correct answer to the "My webserver is" question. "Ubuntu" was the answer to the "operating system" question
Usually the --apache authenticator works just fine which is also an installer plugin, if you want to let Certbot do all the work.. No need for the --standalone, which is quite a hassle if you already have a webserver running.
To be honest, it sounds like you have been following some guide in a misguided manner, not actually knowing what you're doing. (And I don't mean this in a mean way [it's Christmas after all], just being honest here, trying to understand the "how" and "why" of your actions..)
@MikeMcQ That's the .in TLD, the .com TLD seems to be served by ns{1,2}.dns-parking.com. and is hosted on an IP address from MS.
@rajagopal Also, please don't forcibly "renew & replace" (the option you chose) the certificate if the certificate itself is perfectly fine. There is absolutely no need to re-issue a certificate if issuance was not the problem to begin with.
Good point. But, they described the .in domain as being Azure as well as showing the same Ubuntu info in that other thread. Still think it's worth keeping in mind their various efforts.
Tough to be secure without HTTPS (i.e. Port 443) accessible.
Port 443 is closed
$ nmap -Pn -p80,443 reactler.com
Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-26 08:28 PST
Nmap scan report for reactler.com (4.186.62.206)
Host is up (0.21s latency).
PORT STATE SERVICE
80/tcp open http
443/tcp closed https
Nmap done: 1 IP address (1 host up) scanned in 0.43 seconds
Assuming that the issue here is for web server, I still I see Port 443 closed thus access for HTTPS is not possible on the default port.
$ nmap -Pn -p80,443 reactler.com
Starting Nmap 7.93 ( https://nmap.org ) at 2024-12-26 20:02 PST
Nmap scan report for reactler.com (4.186.62.206)
Host is up (0.21s latency).
PORT STATE SERVICE
80/tcp open http
443/tcp closed https
Nmap done: 1 IP address (1 host up) scanned in 0.39 seconds
All routers and firewalls between the server in question and the public internet need to Allow access through.
Here details on Apache can be found in documentation and forums:
