Explore >> Select a destination
|
You are here 
|
techblog.jeppson.org | ||
| | | | |
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... | |
| | | | |
holzer.online
|
|
| | | | | Thoughts on topics like software engineering, web development, blogging and the web in general | |
| | | | |
lewisdale.dev
|
|
| | | | | Getting the project deployed via Gitea actions | |
| | | | |
golb.hplar.ch
|
|
| | | [AI summary] The user has followed a comprehensive guide to secure and configure their VPS server. They have successfully set up SSH with key-based authentication, disabled root login, configured a firewall, and set up a non-root user for system management. The guide also covers changing the SSH port, disabling SSH protocol 1, and setting up SSH agent for passwordless login. The user is now ready to deploy additional services and applications on their secure server. | ||
