|
You are here |
thomascfoulds.com | ||
| | | | |
lewisdale.dev
|
|
| | | | | Getting the project deployed via Gitea actions | |
| | | | |
www.christopherburg.com
|
|
| | | | | [AI summary] The author details their transition from a complex Nginx configuration to the much simpler Caddy reverse proxy for their self-hosted network. | |
| | | | |
techblog.jeppson.org
|
|
| | | | | Nginx proxy manager is a really convenient UI wrapped around nginx. It covers the most common use cases very well. If you have more advanced needs, then it requires some custom configuration. In my case, I wanted to load balance my Proxmox servers. This is how you do that, as per https://nginxproxymanager.com/advanced-config/#custom-nginx-configurations and https://www.reddit.com/r/selfhosted/comments/1fp5mxz/nginx_proxy_manager_fails_when_adding_load/ In ... Continue reading Load balancing behind Nginx Proxy Manager | |
| | | | |
joshuarogers.net
|
|
| | | Just over a year ago we went over how to setup a reverse proxy that would require our users to authenticate. In our original proxy article, we generated some NGinx configuration that looked a bit like... location / { proxy_pass http://jira; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } And it worked. And everyone was happy. Until the day the request came in that NGinx should add a fixed set of credentials to all upstream web requests. | ||