Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to verify issues with Lets Encrypt Auto generation
See original GitHub issueI have ssh access to my server but I don’t know how to verify how or why the autogeneration of my certs have not worked…
I am trying to deploy to two servers simultaneously (which does work) … both have the same sub domain for the auto gen via LetsEncrypt. Is this a problem? Are there some docker commands that I can see what happened with the LetsEncrypt?
Also, it’s not clear in the docs when this actually happens. Does it happen on mup setup or on mup deploy?
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think I know why it’s failing but I’m not sure how to fix it. I am trying to use a Digital Ocean load balancer. The load balancer has the certificate domain a record. So it points to the load balancer ip which is not the same as the two desired backend server ips that are getting set up by mup. Anyone know how to resolve this setup? Do I need to manually generate the cert?
@shadowcodex Thanks for the help! I’ll take a look and see what’s going on.