letsdebug
lego
letsdebug | lego | |
---|---|---|
8 | 55 | |
125 | 7,290 | |
0.0% | 1.5% | |
7.8 | 8.9 | |
4 days ago | 14 days ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
letsdebug
-
Need help installing and securing on Ubuntu VPC
{ "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json", "__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section an> "__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.", "settings": { "cert": "mydomain.duckdns.org", "WANonly": true, "_LANonly": true, "_sessionKey": "MyReallySecretPassword1", "port": 443, "aliasPort": 443, "redirPort": 80, "redirAliasPort": 80 }, "domains": { "": { "title": "MyServer", "_title2": "Servername", "_minify": true, "_newAccounts": true, "userNameIsEmail": true } }, "_letsencrypt": { "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.", "email": "[email protected]", "names": "domain.duckdns.org", "skipChallengeVerification": true, "production": false } }
- Let's Debug
-
LetsEncrypt Cert fails w/ “Invalid Domain” - Renewing or Creating
* ports 80/443 test good withcanyouseeme.org and letsdebug.net
-
Meshcentral not connecting
"__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
-
How to pass the real IP to MeshCentral via Nginx Proxy Manager?
"$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshc entral-config-schema.json", "comment1": "This is a simple configuration file, all values and sections that start with underscore () are ignored. Edit a section and remove the _ in f ront of the name. Refer to the user's guide for details.", "comment2": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.", "settings": { "cert": "", "_tlsoffload": "10.0.2.11", "_WANonly": true, "_LANonly": true, "_sessionKey": "MyReallySecretPassword1", "_port": 443, "_aliasPort": 443, "_redirPort": 80, "selfupdate": true, "AgentPong": 350, "_redirAliasPort": 80 }, "domains": { "": { "certurl": "10.0.2.11", "title": "", "title2": "***", "_minify": true, "_newAccounts": true, "_userNameIsEmail": true } }, "_letsencrypt": { "comment_": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.", "email": "[email protected]", "names": "myserver.mydomain.com", "production": false }, "smtp": { "host": "smtp.zoho.eu", "port": 465, "from": "", "user": "", "pass": "***", "tls": true } }
-
Can I get help with HTTPS please!
What does letsdebug show? Go to https://letsdebug.net ? Put in your domain name and hit run test
-
Cloudflare Issues
{ "$schema": "http://info.meshcentral.com/downloads/meshcentral-config-schema.json", "settings": { "cert": "mc.CFdomain.com", "_WANonly": true, "_LANonly": true, "_sessionKey": "MyReallySecretPassword1", "port": 4430, "_aliasPort": 443, "redirPort": 800, "_redirAliasPort": 80, "AgentPong": 300, "TLSOffload": "127.0.0.1,10.11.11.116", "SelfUpdate": false, "AllowFraming": "false", "WebRTC": "false", "trustedproxy": "CloudFlare" }, "domains": { "": { "_title": "MyServer", "_title2": "Servername", "_minify": true, "NewAccounts": "true", "_userNameIsEmail": true, "certUrl": "https://mc.CFdomain.com" } }, "_letsencrypt": { "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before>", "_email": "[email protected]", "_names": "myserver.mydomain.com", "production": false } }
-
Security concerns with the e-Tugra certificate authority
They list no stipulations about prohibited certificate uses[1]. Their restrictions on domain uses seem to be mostly tied to legal requirements (not issuing for sanctioned countries, for example). It's all also pretty transparent, from what I can tell[2][3]. Certainly more so than a normal CA.
[1]: https://letsencrypt.org/documents/isrg-cp-v3.3/#1.4.2-prohib...
[2]: https://letsdebug.net/
[3]: https://github.com/letsdebug/letsdebug
lego
-
Dehydrated: Letsencrypt/acme client implemented as a shell-script
Self contained but hardly a tiny supply chain attack surface: https://github.com/go-acme/lego/blob/master/go.sum
-
Running one’s own root Certificate Authority in 2023
This ACME client looks promising, but I haven’t tried it yet: https://github.com/go-acme/lego
-
I am once again asking that "web" and "fullstack" developers...
My favorite method of obtaining certificates is with lets encrypt and LEGO
-
Where do you get/setup certificates from for your https/ssl?
Caddy where possible, and acme.sh or lego where not.
- Anyone using WireGuard with a domain name? Any ideas to lower the bills?
- Acme.sh runs arbitrary commands from a remote server
-
How do you renew SSL certificates?
Depend on host's capability... - lego - dehydrated - caddy - in case it already works as a web server, it will automatically issue and renew certs
- Automating LE renewals with dns-01?
-
LeGo CertHub v0.9.0 with Docker Support
u/gregtwallace maybe in the short term until you write your own, you could provide a hook into one of the many ACME client implementations which do DNS-01 and support the majority of major DNS provider APIs out of the box? That would make your (really great!) project much more widely usable.
- Searching for a solution to get letsencrypt and traefik working for my local nas
What are some alternatives?
labca - A private Certificate Authority for internal (lab) use, based on the open source ACME Automated Certificate Management Environment implementation from Let's Encrypt (tm).
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
acme.sh - A pure Unix shell script implementing ACME client protocol
MeshCentral_Nginx-Proxy-Manager - Config I use to make MeshCentral work behind Nginx Proxy Manager, with Docker.
acme-dns - Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.
acmetool - :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)
autocert - [mirror] Go supplementary cryptography libraries
certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
ACL - A simple but powerful Access Control List manager
go-acl - Go support for Access Control Lists