-
Hi, by setting
`LETSENCRYPT_DOMAIN=example.com`
the generated certificate will be only usable with the non-www domain. Browsers don't trust the certificate if you open www.example.com. Is there…
-
I've filed an issue with Google (https://issuetracker.google.com/issues/123397631) but lego probably needs a workaround for the problem. The summary is that even once all of a domain's nameservers hav…
-
### What are you trying to do?
I want to selfhost a service like CapRover or Coolify.
Both provide thier own reverse proxy, so I do not want to use the one provies by the trailscale proxy
Both ma…
-
My environment is set up in the following way;
1. Linode VPS - Ubuntu 20.04, Docker and NPM:latest installed, Wireguard peer (10.5.2.1) to local pfSense on LAN, domain name pointed at static Linode…
-
# SecDir review of draft-ietf-dnsop-domain-verification-techniques-05
CC @kaduk
Since the changes from the -01 that I previously reviewed are so substantial,
this is mostly a de novo review. The…
-
I could not get the script to work with **NGINX 1.19.1**
Always received an error like this:
> ### Requesting Let's Encrypt certificate for mydomain.tld ...
> Saving debug log to /var/log/letse…
-
Maybe I'm totally wrong here, but I was expecting a separate front end served by a web server through port 80.
As I mentioned I'm running Saltcorn on Windows 10, installed as described in the manua…
-
When using letsencrypt cert directly, caddy starts on 443, but assets don't load
When disabling ssl, content shows up fine
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
I'm struggling to configure SWAG to use Cloudflare secret with Docker Swarm secrets
…
-
Related to #80 we need a more holistic overview of the health of the ipfs.io infrastucture. We want to visualise how things are running in a way that give a clear overview at the top level, and lets y…