You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?).
The text was updated successfully, but these errors were encountered:
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.
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?).
The text was updated successfully, but these errors were encountered: