paul
1773ed5f95
Mirror to GitHub / mirror (push) Successful in 26s
Test and Lint / backend-test (push) Successful in 1m11s
continuous-integration/drone/push Build is passing
Test and Lint / frontend-test (push) Successful in 2m28s
Version and Release / version-bump (push) Successful in 32s
Version and Release / trigger-drone (push) Has been skipped
Original: feat: enhance security logging and ensure rate limit blocks are properly tracked - Add comprehensive logging for rate limit blocks with full request details - IP address (with proper proxy detection), user agent, headers, timestamps - Rate limit info (current count, limit, remaining, reset time) - Separate tracking for auth vs general endpoints - Enhance authentication failure logging - JWT validation failures with detailed error info - Admin auth attempts without token - Failed token validation with user context - All events include IP, path, method, user agent - Improve Winston logger configuration for production - Add automatic log rotation (10MB errors, 50MB combined) - Create separate security.log for auth/rate limit events - Ensure logs directory exists automatically - Add structured JSON format for log aggregation - Support container logging with LOG_TO_CONSOLE env var - Create comprehensive documentation - Security logging guide with examples - Monitoring recommendations - Configuration reference - Add test script to verify logging functionality All rate limit settings remain configurable via admin panel: - Window duration, max requests, auth limits - Skip authenticated requests option - Public endpoints only option 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
59 lines
1.5 KiB
Markdown
59 lines
1.5 KiB
Markdown
# Nginx Configuration Fix for Photo Authentication
|
|
|
|
If photos and thumbnails are not loading in gallery view but work in admin, it's likely that the Authorization header is being stripped by nginx or another reverse proxy.
|
|
|
|
## Common Issue
|
|
|
|
The `Authorization` header is often not passed through by default in nginx proxy configurations.
|
|
|
|
## Fix
|
|
|
|
Add these lines to your nginx configuration for the PicPeak location block:
|
|
|
|
```nginx
|
|
location / {
|
|
proxy_pass http://localhost:3001;
|
|
|
|
# Important: Pass the Authorization header
|
|
proxy_pass_header Authorization;
|
|
proxy_set_header Authorization $http_authorization;
|
|
|
|
# Other standard proxy headers
|
|
proxy_set_header Host $host;
|
|
proxy_set_header X-Real-IP $remote_addr;
|
|
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
|
proxy_set_header X-Forwarded-Proto $scheme;
|
|
}
|
|
```
|
|
|
|
## Alternative Fix Using Traefik
|
|
|
|
If using Traefik, ensure headers are passed:
|
|
|
|
```yaml
|
|
services:
|
|
picpeak:
|
|
labels:
|
|
- "traefik.http.middlewares.picpeak-headers.headers.customrequestheaders.Authorization="
|
|
```
|
|
|
|
## Testing
|
|
|
|
1. Check if Authorization header is reaching the backend:
|
|
```bash
|
|
curl -H "Authorization: Bearer YOUR_TOKEN" https://picpeak.yourdomain.com/thumbnails/test.jpg -v
|
|
```
|
|
|
|
2. Check nginx logs to see if the header is present:
|
|
```bash
|
|
tail -f /var/log/nginx/access.log
|
|
```
|
|
|
|
## Docker Compose Fix
|
|
|
|
If using docker-compose with nginx proxy, add:
|
|
|
|
```yaml
|
|
environment:
|
|
- NGINX_PROXY_PASS_HEADER=Authorization
|
|
``` |