I’m not sure I understand the problem. You can do any number of URL based redirects to whatever ports you wish.
Why isn’t a forward to apache sufficient for your needs? Lets Encrypt just needs a file in that folder, correct? Another option is to run a local webserver (nginx, etc) on the pound server, on a separate port (i.e. 81), and redirect .well-known URLS to that server. (So you can run the perl script, or whatever) ------ Joe On 12/5/17, 4:14 PM, "Alan" <[email protected]> wrote: Hi, I've posted my question on https://serverfault.com/questions/886583/how-to-configure-pound-proxy-to-pass-requests-to-well-known-directory, however it seems not many people are well familiar with Pound, so I've found out I needed to subscribe to this mailing list to get support. We have Apache running behind Pound and so we are having troubles with Let's Encrypt requests and renewals, and need to pass requests to the .well-known directory and its sub-directories directly to Apache port. Could anyone explain how to do this on Pound? Thanks! -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
