Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
jb-vpn.uk Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
SSH Port Forwarding:Best Practices
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
This document outlines best practices when adding new services to the reverse proxy system. == General Best Practices == === '''Always validate Caddy''' before reloading (<code>caddy validate</code>) when changing public hostnames === == '''Use descriptive subdomain names''' that indicate the service == == '''Document your services''' in [Current Services](current-services.md) == == '''Backup configurations''' before making changes == == '''Monitor logs''' after adding new services == == '''Use HTTPS''' for all public-facing services == == '''Test thoroughly''' before marking service as complete == == Checklist == Use this checklist when adding a new service: * [ ] DNS A record created and propagated * [ ] Service running on Synology NAS * [ ] Service accessible from VPN network * [ ] Nginx configuration file created * [ ] Site enabled (symlink created) * [ ] Nginx configuration tested (<code>nginx -t</code>) * [ ] Nginx reloaded * [ ] HTTP access verified * [ ] SSL certificate obtained * [ ] HTTPS access verified * [ ] Browser testing completed * [ ] Service documented in [Current Services](current-services.md) == Security Considerations == * Always use HTTPS for public-facing services * Keep SSL certificates up to date (automatic renewal via Certbot) * Use strong authentication for services that require it * Monitor access logs for unusual activity == Related Documentation == * [Step-by-Step Process](step-by-step.md) - Setup process * [[Documentation:Index|Troubleshooting]] - Common issues [[Category:Documentation]] [[Category:Documentation/SSH Port Forwarding]]
Summary:
Please note that all contributions to jb-vpn.uk Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Jb-vpn.uk Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
SSH Port Forwarding:Best Practices
Add topic
