Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
DNS security and domain hijacking Question Question
Webserver TCP port 53 is open or closed? Question Question

Question

Address Bar Shows Padlock with Red Line . . Used LetsEncrypt

Posted May 26, 2020 626 views
SecurityDNS

I (think I) installed SSL using LetsEncrypt 72 hours ago, & still have a padlock with a red line through it, which appears in firefox, chrome, safari, & brave browsers.

EricNyc.Rocks, a wordpress website, seems to function properly. But there’s no www – not sure if that matters. & there’s no http or https.

I linked to digitalocean nameservers at namecheap.com. At digitalocean, I linked the different ways to type my domain to the droplet’s IP address. & I linked the nameservers to the IP address.

The SSL checker at SSLshopper says . .

www.ericnyc.rocks resolves to 159.89.224.251

Server Type: Apache/2.4.29 (Ubuntu)

No SSL certificates were found on www.ericnyc.rocks. Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server’s firewall.

It’s that last paragraph I don’t understand. Any help much appreciated.
Thanks, Eric

Add a comment
ericlindellnyc
By:
ericlindellnyc

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
DNS security and domain hijacking Question Question
Webserver TCP port 53 is open or closed? Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
KFSys May 26, 2020

Hi @ericlindellnyc,

It seems like nothing is listening on your port 443. Port 443 is the one that handles https requests. I can see you are using Apache as well, so you’ll need to create a host configuration for your domain http://ericnyc.rocks/ which listens to port 443 and loads the certificates.

If you are unsure how you can achieve that, don’t worry DigitalOcean has a really good guide on this one:

https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-18-04

In this tutorial, you will use Certbot to obtain a free SSL certificate for Apache on Ubuntu 18.04 and set up your certificate to renew automatically.

This tutorial will use a separate Apache virtual host file instead of the default configuration file

Regards,
KDSys

How To Secure Apache with Let's Encrypt on Ubuntu 18.04
by Kathleen Juell
by Erika Heidi
Let's Encrypt is a Certificate Authority (CA) that provides an easy way to obtain and install free TLS/SSL certificates, thereby enabling encrypted HTTPS on web servers. In this tutorial, you will use Certbot to obtain a free SSL certificate for Apache on Ubuntu 18.04 and set up your certificate to renew automatically.
Reply Report
  • ericlindellnyc May 28, 2020

    KDSys, Thanks for feedback.
    I followed instructions . .
    How To Secure Apache with Let’s Encrypt on Ubuntu 18.04

    Instructions linked to . .
    “Initial server setup with ubuntu 18.04.”

    I got to “Step5. Enabling External Access for Your Regular User”

    Those instructions linked to . .
    How to Set Up SSH Keys on Ubuntu 18.04.
    I followed instructions, & set . .

    PasswordAuthentication no (SAVED/CLOSED FILE)

    To implement changes, we must restart sshd service:
    sudo systemctl restart ssh

    Test SSH service functioning correctly before closing session:
    ssh username@remote_host

    ** THEN I GET THIS ERROR **
    Permission Denied (PublicKey)

    Confused. Suggestions appreciated.
    Eric

    Reply Report
    • KFSys June 1, 2020

      Hi @ericlindellnyc,

      In this case I believe you can skip the Initial Server setup and most importantly the part where you add a new user and add to it an SSH key. You can continue directly with the tutorial itself about Let’s Encrypt and how to configure it on your server.

      Reply Report

Related

Looking for something else?

Ask a new question Search for more help