Hi, I have this running at home. I can not check now, nearly midnight for me, but from my memory, letsencrypt just need to be able to read the .well_known from the website address, not from the server really porting apache.
I think that what I did, was to create a rule saying that all request to .well_known directory was redirected to the pound server itself... I am not perfectly sure of the way I achieved this, but if this information can help you... Let's share... If you can wait one or two days, I could check tomorrow on my server... But I clearly remember that I created a local directory (on pound server) to make It work. Best regards, Christian COMMARMOND (From Paris, France) Le 5 déc. 2017 22:11, "Alan" <[email protected]> a écrit : > Hi, > > I've posted my question on > https://serverfault.com/questions/886583/how-to-configure- > pound-proxy-to-pass-requests-to-well-known-director > <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. >
