By default, TunnelHound stores all data on an integrated PostgreSQL database. We strongly suggest that you keep backups of this database in case of server failure. This helps protect against data loss, which could render your entire network unserviceable.
More specifically, the database contains the server’s private keys, which are required for the server to be able to send data back to clients and complete the handshake process. If these data are lost, no client will be able to connect to your network, and there is no way to re-create it.
After setting up TunnelHound, you may be itching to get your first clients connected. Follow the instructions in the Getting Started page below, to set up your first network.
TunnelHound allows your users to manage their own VPN connections, if you’ve granted them that permission. Please direct users to the following manual if they need help interacting with the TunnelHound appliance.
You can allow your organization to login to TunnelHound via a SAML 2.0 SSO service, if you have an appropriate license. For help setting up SAML SSO, see the document below.
Running TunnelHound successfully on a cloud system may require some additional steps. Firstly, you’ll need to ensure that your cloud network environment is set up so you can access TunnelHound. For best results in cloud environments, see our Cloud Setup page.
The TunnelHound interface provides you with a simple interface for configuring your entire WireGuard ® VPN. Refer to the page below for instructions on how to use the Admin UI to set up your first VPN.
Table of contents
- Database Backup
- Managing SSL certificates
- Using Let's Encrypt Certificates
- Custom SSL certificates
- Single sign-on(SAML) setup
- User Administration
- Endpoint Administration
- Device Administration
- Routing Basics
- Key Rotation
- Appliance Settings