Explore >> Select a destination
|
You are here 
|
avelino.run | ||
| | | | |
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 upstre... | |
| | | | |
lewisdale.dev
|
|
| | | | | Getting the project deployed via Gitea actions | |
| | | | |
nikdoof.com
|
|
| | | | | After a short, frustrating time, i've finally got the Deluge (archive.org) WebUI to proxy through Nginx without any errors. The revelation came when digging through the Deluge forums I found a little nugget of information (archive.org) which solved it all, a small header call X-Deluge-Base that when passed will prefix any media calls made in the page with that text. So instead of setting up weird aliases and fiddling around with Nginx's options to get it to work I could just specify that and use a very b... | |
| | | | |
blog.wensheng.org
|
|
| | | I used to use Godaddy and Startcom SSL. Now I just use Namecheap's Comodo PositiveSSL. It's inexpensive - $9/per year, and the installatio... | ||
