1
Allow /send/ to be exposed on a separate port while keeping Vaultwarden internal
Source: dani-garcia/vaultwarden#6345 · opened by @ishak2001
It would be useful to have the ability to serve the Vaultwarden Send feature (/send/) on a different port or endpoint, while keeping the main Vaultwarden server internal or accessible only via VPN, without requiring an additional subdomain or separate domain.
Use case:
• The main Vaultwarden instance remains internal for security reasons.
• Only the /send/ functionality should be publicly accessible over HTTPS.
• The goal is to maintain a single unified domain ( for both internal access and the public Send feature.
• Currently, exposing /send/ separately is not straightforward, as it uses the same domain and port as the main server.
This feature would allow organizations to securely share passwords via the Send feature without exposing the entire Vaultwarden instance to the internet, while keeping a clean, unified domain setup.
Use case:
• The main Vaultwarden instance remains internal for security reasons.
• Only the /send/ functionality should be publicly accessible over HTTPS.
• The goal is to maintain a single unified domain ( for both internal access and the public Send feature.
• Currently, exposing /send/ separately is not straightforward, as it uses the same domain and port as the main server.
This feature would allow organizations to securely share passwords via the Send feature without exposing the entire Vaultwarden instance to the internet, while keeping a clean, unified domain setup.
No pledges yet. Be the first to back this.
No comments yet.