What is the least disruptive way to force www?

My domain is: https://www.pghlug.com

My web server is (include version): apache2 (2.4.25-3+deb9u3)

The operating system my web server runs on is (include version): Debian 9

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): GNU Bourne Again SHell bash (4.4-5)

I want to force www for Search Engine Optimization. The Default Let’s Encrypt Apache Configuration isn’t doing it for me. I would like to fix it without risking breaking Let’s Encrypt on the next cert update. What is the least disruptive way to force www?


For your concern, you can try using this third-party client called ACME.sh which support DNS-01 Verification with Godaddy. https://github.com/Neilpang/acme.sh

If you choose DNS-01 method, that’s the best way to verify without interfere with your server(Only your dns)


What do you mean by “force www”? Do you mean that you want requests for https://pghlug.com redirected to https://www.pghlug.com? If that’s what you’re wanting to do, then you’re right that the default LE Apache config doesn’t do that–it isn’t designed to. You’ll need to include that redirect in your server configuration. If you implement it with a 301 redirect, it shouldn’t cause any problems with cert renewal, as the LE servers will follow redirects.

What about OP’s question suggested that either DNS validation or Godaddy were in play?

Thank you @danb35. I will do that.

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