Talk:Nginx as reverse proxy with acme (letsencrypt): Difference between revisions

From Alpine Linux
Jump to navigation Jump to search
(Added a call for update)
 
mNo edit summary
Line 7: Line 7:
#acmetool want example.com voidlinux.org
#acmetool want example.com voidlinux.org


(With your domains, d'uh!) is a great way to get going - I found the proxy version worked quite well with just a few adjustments from the guides here. Hopefully someone with experience will fix this up. Alpine/nGinX is a blazing fast way to proxy HTTP/HTTPS to my hodge-podge of servers.
(With your domains, d'uh!) is a great way to get going - I found the proxy version worked quite well with just a few adjustments from the guides here. Hopefully someone with experience will fix this up. Alpine/nGinX is a blazing fast way to proxy HTTP/HTTPS to my hodge-podge of servers.[[User:Marcdraco|Marcdraco]] ([[User talk:Marcdraco|talk]]) 13:27, 24 May 2019 (UTC)

Revision as of 13:27, 24 May 2019

acme-client is no longer in the repos - looks like its been replaced with acmetool. I assume by the same author? I'm nowhere near experienced enough to refactor this page BUT the user guide (hlandau.github.io/acme/userguide) is pretty good, you set it up like so:

  1. acmetool quickstart

and then:

  1. acmetool want example.com voidlinux.org

(With your domains, d'uh!) is a great way to get going - I found the proxy version worked quite well with just a few adjustments from the guides here. Hopefully someone with experience will fix this up. Alpine/nGinX is a blazing fast way to proxy HTTP/HTTPS to my hodge-podge of servers.Marcdraco (talk) 13:27, 24 May 2019 (UTC)