letsdebug
certmagic
letsdebug | certmagic | |
---|---|---|
8 | 13 | |
125 | 4,827 | |
0.0% | 0.9% | |
7.8 | 8.2 | |
4 days ago | 12 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
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
certmagic
- Show HN: Clace – Platform for secure internal web applications
-
Who is using Go to build web sites and applications?
Now, I serve TLS directly from the application and was able to make it all work with Certmagic.
-
Building web-based SaaS with Go as a solo entrepreneur. What should I be aware of?
For deployment, you may not need a reverse proxy with Nginx or the likes. Certmagic will make HTTPS a breeze. Also makes it possible to handle multi-tenant SaaS domains SSL provisioning. While not the easiest, it was much easier than trying to do it at the reverse proxy and cheaper than doing it with Cloudflare's SaaS service.
-
How do I deploy a Golang REST API on DigitalOcean as you do for production?
If you don't want to move certificate management to a different service, use CertMagic in your app.
-
Hitless TLS Certificate Rotation in Go
With certmagic its done completly automatic using letsencrypt: https://github.com/caddyserver/certmagic
- Show HN: A Full-Stack Web Framework Written in Go
-
caddy v2.5.1 adds support for Authelia and other authentication providers
The project is also a boon for devs. The certmagic library0 makes it trivial to add Let's Encrypt support to any Golang web server code.
-
Show HN: Caddy v2.5.0
Because Lego maintainers wouldn't budge when Caddy needed changes made to increase ACME reliability. Matt wrote his own implementation https://github.com/mholt/acmez and started using that in Caddy soon after. There's a deeper explanation here: https://github.com/caddyserver/certmagic/issues/71
-
Which web framework is more preferred or "industry standard" today?
That said, I would use https://github.com/caddyserver/certmagic to manage you SSL certs.
-
Do you handle TLS/HTTPS termination in go code, or relly on another service (NGINX, Load Balancer, F5, Heroku, PaaS, etc)?
I terminate SSL in GO (less moving parts to manage), and use https://github.com/caddyserver/certmagic to provision and renew my certs.
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).
lego - Let's Encrypt/ACME client and library written in Go
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
MeshCentral_Nginx-Proxy-Manager - Config I use to make MeshCentral work behind Nginx Proxy Manager, with Docker.
go-acl - Go support for Access Control Lists
acmetool - :lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)
go-yara - Go bindings for YARA
passlib - :key: Idiotproof golang password validation library inspired by Python's passlib
certificates - An opinionated helper for generating tls certificates
nacl - Pure Go implementation of the NaCL set of API's