NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Cache Assets takes website offline
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
When using the "cache assets option" with and without the below parameters, my website is taken offline. When the option is disabled, its fine.
proxy_cache CACHE;
proxy_cache_valid 200 48h;
proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504;
proxy_cache_lock on;
expires 1y;
add_header Cache-Control public;
add_header 'Access-Control-Allow-Origin' '*';
add_header X-Cache-Status $upstream_cache_status;
add_header X-Content-Type-Options nosniff;
Software:
Debian 12 64bit
Docker version 28.2.2, build e6534b4
jc21/nginx-proxy-manager:latest
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository file, test, or entry point. Start by reproducing the outage with the listed proxy_cache settings in jc21/nginx-proxy-manager:latest, then inspect the generated Nginx configuration and logs; done means cache assets no longer takes the website offline and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100