Open jearton opened 2 years ago
I found a solution through reading the source code. Just add the root location directive block in the proxy advanced configuration, then the root location of reverse proxy will not be generated. The relevant source code is as follows:
https://github.com/NginxProxyManager/nginx-proxy-manager/blob/develop/backend/internal/nginx.js#L220
To complete the response here :
you can create a dummy nginx conf like this :
And then add an advanced configuration like this
root /downloads;
location / {
autoindex on;
autoindex_exact_size on;
autoindex_format html;
autoindex_localtime on;
}
⚠️ the path has to be mounted in you docker / docker-compose file.
I have a question.
What does http://localhost:11111/ mean?
root /deploy; location / { autoindex on; autoindex_exact_size on; autoindex_format html; autoindex_localtime on; }
Should the root location here be aligned with the docker-compose file location?
I'm asking because I'm currently encountering a 404 not-found error.
I have a question.
What does http://localhost:11111/ mean?
root /deploy; location / { autoindex on; autoindex_exact_size on; autoindex_format html; autoindex_localtime on; }
Should the root location here be aligned with the docker-compose file location?
I'm asking because I'm currently encountering a 404 not-found error.
the guy had mention,⚠️ the path has to be mounted in you docker / docker-compose file.
i think you might don't know how to do,so i give a example,if your html files location in /srv
then ,you should edit your docker-compose.yml like this:
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
- /srv:/srv
then 404 will disappear
Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Describe alternatives you've considered
Use native nginx.
Additional context