Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi
I have a problem with a virtual ubuntu 14.04 lts server I control via ssh login. I try to install Lets Encrypt certificate, which ends with this msg:
urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Failed to connect to 217.170.205.92:443 for TLS-SNI-01 challenge
Port 443 obviously is not open. How to open it? It seems the answer is ufw, which I had to install, but when enabling it, I am warned that this might interfere with existing ssh connections, which is exactly what I use to communicate.
Now, what do I do then?
I propably don't fully understand the roles of apache, acme and what service or whatever shall listen to the certificate issue's testing.
It seems the answer is ufw, which I had to install, but when enabling it, I am warned that this might interfere with existing ssh connections, which is exactly what I use to communicate.
In addition to opening the port for HTTPS, be sure the port for SSH is open before you enable UFW.
Code:
sudo ufw status verbose
If SSH (22) is not already open, then you need to open it before turning on UFW.
Code:
sudo ufw allow ssh
Otherwise you will be locked out of SSH the moment you turn on UFW.
There is also no reason to install ufw to "open" a port.
Unless you already have a firewall rule rejecting ir dropping such traffic, then the port is already "open"
More likely something using it already (webserver?), so stop that before running the LE client or maybe read the instructions.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.