...
We also strongly suggest securing the SSH access to your server (switching from root password to SSH public key authentication, or at the very least switching out the default ssh port and using a strong password).
| Note |
|---|
| Please note that we do not provide support for Wireguard beyond ensuring that the pre-installed software works "out of the box". For any questions regarding more advanced configuration of Wireguard, please refer to their documentation: Official, Unofficial (but more detailed). Do note that manually editing Wireguard configuration files might break some WGdashboard functionality. If you are looking to deploy complex routing rules, which require manual configuration, it might be better to choose one of our regular OS template and install/configure everything by hand. |
| Note |
|---|
...
| Important |
...
| ! Wireguard by default routes ALL traffic from the peer. Thus make sure that the connected peers do not emit malicious traffic, which violates our Terms of Service (spam, cyberattacks (bruteforce, network scanning), etc). You, as the owner of the server, are solely responsible for the traffic emitting from your server, and we will suspend your server if you violate our Terms. Ensure that none of the client (peer) devices that will be connected to your server are infected with malware prior to routing their traffic via your Wireguard server. |
| CSS Stylesheet |
|---|
.home-banner {
background: #459df0;
color: #fff;
font-size: 20px;
padding: 20px;
}
.home-banner h2 {
color: #fff;
}
.title-box {
border: 1px none #459df0;
padding: 10px;
}
.title-box > h2 {
background: #459df0;
bottom: 10px;
color: #fff;
margin-left: -10px;
margin-right: -10px;
padding: 2px 10px;
position: relative;
} |
...