|
You are here |
nikdoof.com | ||
| | | | |
rajkumaar.co.in
|
|
| | | | | It was during COVID-19 that I thought of buying a Raspberry Pi 4, purely out of boredom. | |
| | | | |
thomasvilhena.com
|
|
| | | | | [AI summary] This blog post explains how to set up an Nginx reverse proxy with Docker and Certbot for SSL certificate management, focusing on configuration files and services for load balancing and secure communication. | |
| | | | |
lewisdale.dev
|
|
| | | | | Getting the project deployed via Gitea actions | |
| | | | |
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. | ||