Err_cert_common_name_invalid

Server
21

No, that's an Apache rewrite rule. Use it in your port 80 vHost.

%{SERVER_NAME} and %{REQUEST_URI} are replaced by the current values.

1 Like
22

If I have never wrote instructions inside Apache before, should I find a GUI like Cpanel to address this, or is there a tutorial on the conventions for finding the correct file, amending it excatly, and saving? Digital Ocean has a console where I can sign in at the server root level with all authority, and Ubuntu, Apache, and Wordpress are loaded as their “one click Wordpress install”.
With a GUI looking into the Apache config file I would look to delete any redirects that had the IP address in them, so far no one has told me they need to be there, so I would clean them out.

23

I don't think such GUIs exist. There are enough Apache documentations you can use.

https://httpd.apache.org/docs/2.4/ssl/ssl_howto.html

24

Hey mate, I run Harbinger-News.com which I am still in the setup stage with development of the web interface but when I first transferred over from a free domain to the paid one I had very similar issues with routing and DNS. I currently use a COMODO SSL solution because of the customer support they offer and the ability to relatively cheaply upgrade to a EV cert after 12 months. The best thing you can do is completely remove all of your DNS and routing entries and write them yourself from scratch using a reference guide and online information. That way you will have a great understanding about how the DNS system works under a posix architecture. I did this myself and found it to be extremely helpful when I setup my email server and SSL secured SSHD and IRCD servers, as one of them is situated in a server farm and the other is in my house

1 Like
25

Hi @HarbingerNewsAU

it's a general problem.

There are

  • dns problems and wrong dns settings (port forwarding)
  • problems with a local router or firewall
  • problems with an server-integrated firewall
  • wrong or untypical webserver configurations (different vHosts with the same ServerName)
  • wrong redirects (missing /, redirect to www.example.com.well-known)
  • using Cloudflare or other systems without a working certificate
  • using a wrong configured local proxy server
  • mix of ACME-client-installation and ACME-client-usage
  • ...

so the creation of a certificate doesn't work.

If there is a DNS-problem, it doesn't help to check the webserver :wink:

One or more of these problems can block the validation of a new certificate.

So using a paid certificate doesn't need such a validation, typical, it's a link in a mail.

26

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.