Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use Network Path for 'Website Root Directory' #476

Open
bt-dd opened this issue Nov 19, 2019 · 1 comment
Open

Unable to use Network Path for 'Website Root Directory' #476

bt-dd opened this issue Nov 19, 2019 · 1 comment

Comments

@bt-dd
Copy link

bt-dd commented Nov 19, 2019

We have a number of servers behind a load balancer, to pass the HTTP/File challenge, we would like to use a shared network location. This way whichever server is hit, the file will be present.

However, when using a network drive (either directly or mapped), get the following error -

The website root path for <site-name> could not be determined. Request cannot continue.

Ideally this setting would support network locations (maybe with credential support as well?).

@webprofusion-chrisc
Copy link
Contributor

Sorry for the very delayed reply, I didn't notice this (and other) issues being created.

When the service performs the validation challenge responses it does so as Local System, I think that's not going to work by default as you have no network user to authenticate as.

The next major version has some Centralised Certificate Store features planned (which include impersonation for network access), this may also be a solution for this configuration.

As an alternative, your load balancer would ideally route /.well-known/acme-challenge requests to a single server, then you also have the ability to use the built-in http challenge server the app provides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants