2nd Let's Encrypt Address Broke Apache

[Garm]

Problem Description
I was tinkering with my config options trying to solve a different problem and screwed up apache. I had a working web address and when I attempted to add a second address that was listed under Let’s Encrypt it disrupted Apache’s config file.

Steps to Reproduce

1. Login to Freedombox.
2. Go to Let’s Encrypt.
3. Attempt to add second web address.

Expected Results
I expected for certification to go through.

Actual results
I am unable to access my server except through SSH and physically being at the server.

Screenshot

Information

• FreedomBox version: (Latest Version as of 8/1/21) 20.4
• Hardware: Macmini I7
• How did you install FreedomBox?: USB loaded with Image from freedombox.org.

[jvalleroy]

I notice your domain has capital letters. It is probably the same as this issue:

[SOLVED] Cannot access plinth due to capitalized alphabets in domain names

Hi, I’ve tried adding a let’s encrypt certificate to my domain and now I cannot access plinth anymore from browser, I get “can’t establish a connection to the server” or “This site can’t be reached ERR_ADDRESS_UNREACHABLE”. I’m still able to connect via ssh(I use the same ip as the web interface), and to use the openvpn server with a domain gnu-dip MyIp.sds-ip.de on the freedombox. I installed Matrix and then tried to add let’s encrypt via the link in the setup information. After clicking on l…

[Garm]

Yes. That solved the issue. Thank you. I knew there had to be a way to do it.

[NickA]

Would the issue need to be reopened?

letsencrypt: Issue with capital letter in domain name (#1964) · Issues ·...

[jvalleroy]

No, there is no point to re-open that issue. It is fixed on the master branch, and in experimental. However, the fix did not make it into bullseye, due to freeze.

If we think it could be fixed in a later update to bullseye, then we could open a Debian bug for the affected version in bullseye.