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
Server won't boot Question Question
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question

Question

"This site can’t be reached" after setting up a certificate

Posted December 4, 2019 2.6k views
ApacheSecurityDNS

My website, dwfcc.com, which was working fine, but I wanted to set up a certificate for security.

However, once I added a certificate (using the “Add Certificate” button) trying to access the site in a browser gives a “This site can’t be reached” error.

Everything seems to be working fine internally. I can ping the site, and access it through SSH or SFTP. It’s just the browser that isn’t working. What happened and how do I fix it?

Add a comment
dnadel95
By:
dnadel95

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
Server won't boot Question Question
Problem installing wordpress on subdomain (nginx / ubuntu) Question Question
Add a comment
1 comment
  • dnadel95 December 4, 2019
    Reply Report

    Also, I suddenly can’t restart Apache2. Trying returns the following:

     * Restarting web server apache2                                                                                        [Wed Dec 04 16:34:15.531703 2019] [alias:warn] [pid 5862] AH00671: The Alias directive in /etc/phpmyadmin/apache.conf at line 3 will probably never match because it overlaps an earlier Alias.
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs
Action 'start' failed.
The Apache error log may have more information.

    I have tried killing the LISTEN processes, but they just come back. There is also only one copy of “Listen 80”.

    While it is possible to remove the problematic line in apache.conf, I don’t understand why it is suddenly an issue - it never was before.

    There are no error logs for this, presumably because it is unable to open logs.

    edited by MattIPv4

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
bobbyiliev December 5, 2019

Hello,

I would recommend following these steps on how to troubleshoot common Apache problems:

https://www.digitalocean.com/community/questions/how-to-troubleshoot-common-apache-issues-on-linux-server

Then feel free to share the output of the commands here so that I could try to advise you further.

Regards,
Bobby

Reply Report
  • dnadel95 December 5, 2019

    I had tried reloading from last week’s backup before you answered this, but that seems to have just made it worse.

    systemctl wasn’t working at first, so I reinstalled it.

    Trying to check if Apache2 is running:

    apache2.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

    It seems that many things on the server simply stopped working, or were deleted, or something.

    I tried reinstalling Apache2. Although it looks like it was installed correctly, the above error still happened when I tried to check it.

    Reply Report
    • bobbyiliev December 12, 2019

      Hello,

      This sounds like an issue with systemctl, have you tried running a daemon reload:

      systemctl --user daemon-reload

      Let me know how it goes!
      Regards,
      Bobby

      Reply Report

Related

Looking for something else?

Ask a new question Search for more help