I think I've managed to make all must stuff pretty complicated! I own my own domain, and use subdomains to access several of my home services via SWAG reverse proxy. It was working fine, I went to add one more, ha.mydomain.com. I added the ",homeassistant" to SWAG SUBDOMAINS, added the /mnt/user/appdata/swag/nginx/proxy-confs/homeassistant.subdomain.conf

 

I think I've just made this all way too complicated! I initially registered my domains at godaddy. Since then, I've changed both the primary and secondary DNS entries at godaddy to point to hostgator, and have been using hostgator for all the DNS management, and actual hosting of some stuff.

 

I'm looking for suggestions on streamlining this whole process so it isn't such a boondoggle everytime I want to add or remove a little subdomain.

 

Here are the errors I'm looking at in the SWAG log. That Type is saying dns, but I selected http for VALIDATION.

 

 

Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created
Using Let's Encrypt as the cert provider
SUBDOMAINS entered, processing
Sub-domains processed are: nextcloud.mydomain.com,photos.mydomain.com,bitwarden.mydomain.com,homeassistant.mydomain.com
E-mail address entered: [email protected]
http validation is selected
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Account registered.
Requesting a certificate for nextcloud.mydomain.com and 3 more domains

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
  Domain: bitwarden.mydomain.com
  Type:   dns
  Detail: DNS problem: SERVFAIL looking up A for bitwarden.mydomain.com - the domain's nameservers may be malfunctioning; no valid AAAA records found for bitwarden.mydomain.com

  Domain: homeassistant.mydomain.com
  Type:   dns
  Detail: DNS problem: SERVFAIL looking up A for homeassistant.mydomain.com - the domain's nameservers may be malfunctioning; no valid AAAA records found for homeassistant.mydomain.com

  Domain: photos.mydomain.com
  Type:   dns
  Detail: DNS problem: query timed out looking up A for photos.mydomain.com; no valid AAAA records found for photos.mydomain.com

  Domain: nextcloud.mydomain.com
  Type:   dns
  Detail: During secondary validation: DNS problem: SERVFAIL looking up A for nextcloud.mydomain.com - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for nextcloud.mydomain.com - the domain's nameservers may be malfunctioning

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

 

I use cloudflare free account for all dns and would recommend it.  It has a ton of videos on youtube.  I was using SWAG but switched to Nginx Proxy Manager for simplicity.  I also bought domain at Godaddy and changed the nameservers to cloudflare.  If i add a docker I can add a CNAME on cloudflare and cert on NPM in 5 minutes.

Thank you @Gragorg Something about when I enabled the homeassistant.proxy.conf and added the ",homeassistant" to the SWAG app config, it really just screwed things up. I removed it, bang working again.

I've also had a suspicion that those old Spaceinvader Lets Encrypt videos were getting a bit dated; and there is better software out there. One of these days I'll get it all transferred over!

At least it's all back up at the moment.