Give it a try and comment your experience no matter what!
Order tension free! We provide a 15-Day Money-Back Guarantee

KVM Server Offers

KVM-1

• 1GB RAM
• 1x vCPU
• 15GB NVMe Space
• 1TB Transfer
• 1x IPv4
• KVM/SolusVM
• $5/month
  [Order Now]

KVM-2

• 1.5GB RAM 3GB RAM
• 1x vCPU 2x vCPU
• 30GB NVMe Space
• 1.5TB Transfer
• 1x IPv4
• KVM/SolusVM
• Coupon: HPYKVM
• $8.5/month $7/month
  [Order Now]

OpenVZ server Offers

SSD-Mini

• 1GB RAM
• 1x vCPU
• 15GB NVMe space
• 750GB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• $3/month
  [Order Now]

SSD-1

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB NVMe space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD
• $4/month
  [Order Now]

SSD-2

• 2GB RAM
• 2GB vSwap
• 4x vCPU
• 40GB NVMe space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD2
• $6/month
  [Order Now]

Looking Glass

For OpenVZ servers: https://lg-pl.happybeehost.com/
Location: Poland
For KVM servers: https://lg-fr.happybeehost.com/
Location: France

Available OS Templates

AlmaLinux 8
CentOS 8
CentOS 7
CentOS 6
Ubuntu 20.04
Ubuntu 18.04
Ubuntu 16.04
Debian 11
Debian 10
Debian 9
Debian 8

15-Day Money-Back Guarantee

If you decide to cancel your account within 15 days of sign up, HappyBee Host will refund you the whole amount. We value customer satisfaction. You just need to open a ticket with our Billing Department and the Cancellation Type should be "Immediate".

We are currently presenting some cool offers on our OpenVZ Virtual servers.

OpenVZ server Offers

SSD-Mini

No Coupon Code Needed!

• 1GB RAM
• 1x vCPU
• 15GB SSD space
• 750GB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• $3/month

[Order Now]

SSD-1

Please use the Coupon Code HPYSSD to get $3 discount on SSD-1 Virtual Server plan for the lifetime.

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD
• $4/month

[Order Now]

SSD-2

Please use the Coupon Code HPYSSD2 to get $5 discount on SSD-2 Virtual Server plan for the lifetime.

• 2GB RAM
• 2GB vSwap
• 4x vCPU
• 40GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD2
• $7/month

[Order Now]

Looking Glass:

https://lg-pl.happybeehost.com/

Available OS Templates:

• CentOS 8
• CentOS 7
• CentOS 6
• Ubuntu 20.04
• Ubuntu 18.04
• Ubuntu 16.04
• Debian 10
• Debian 9
• Debian 8

30-Day Money-Back Guarantee

If you decide to cancel your account within 30 days of sign up, HappyBee Host will refund you the whole amount. We value customer satisfaction. You just need to open a ticket with our Billing Department and the Cancellation Type should be "Immediate".

We are with Hetzner and recently a set of users have started sending spam mails from our VPS Servers. I just wanted to know whether there is an option to get the alert according to a certain threshold without suspending the container in nodewatch?

Or is there any other software that you guys use?

Thanks in advance.

We are currently presenting some cool offers on our OpenVZ and KVM virtual servers.

OpenVZ server Offers

OpenVZ SSD Server Offers

SSD-Mini

Use the Coupon Code SSD50 to get 50% off on all OpenVZ Virtual Server plans for the lifetime.

• 1GB RAM
• 1x vCPU
• 15GB SSD space
• 750GB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: SSD50
• $1.5/month

[Order Now] (You will get this plan for $1/Month if you choose Quaterly, Semi-Annual or Annual billing period)

SSD-1

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: SSD50
• $3.5/month

[Order Now]

SSD-2

• 2GB RAM
• 2GB vSwap
• 4x vCPU
• 40GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: SSD50
• $6/month

[Order Now]

Looking Glass: https://lg-pl.happybeehost.com/

KVM SSD Server Offers

KVM-1

• 1GB RAM
• 1x vCPU
• 15GB SSD Space
• 1TB Transfer
• 1Gbps Uplink
• 1x IPv4
• KVM/SolusVM
• $5/month

[Order Now]

Available OS Templates:

• CentOS 8
• CentOS 7
• CentOS 6
• Ubuntu 20.04
• Ubuntu 18.04
• Ubuntu 16.04
• Debian 10
• Debian 9
• Debian 8

30-Day Money-Back Guarantee

If you decide to cancel your account within 30 days of sign up, HappyBee Host will refund you the whole amount. We value customer satisfaction. You just need to open a ticket with our Billing Department and the Cancellation Type should be "Immediate".

We are currently presenting some cool offers on our Shared hosting managed Virtual servers.

Hosting VPS Offers

We are providing free support (Upto 5 tickets per month) and service monitoring (Apache, MySQL, FTP, Crond, cwpsrv, dovecot and Postfix) for our new clients. All servers are equipped with a Licensed CWP control Panel.

SSD-CP-MINI

No Coupon Code Needed!

• 1GB RAM
• 1GB vSwap
• 1x vCPU
• 15GB SSD Space
• 750GB Transfer
• 1Gbps Uplink
• 1x IPv4
• OpenVZ/SolusVM
• $5/month

[Order Now]

SSD-CP-1

No Coupon Code Needed!

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• $7/month

[Order Now]

OpenVZ SSD Server Offers (Unmanaged)

Unmanaged OpenVZ SSD servers not including free support and service monitoring support.

SSD-Mini

No Coupon Code Needed!

• 1GB RAM
• 1x vCPU
• 15GB SSD space
• 750GB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• $3/month

[Order Now]

SSD-1

Please use the Coupon Code HPYSSD to get $3 discount on SSD-1 Virtual Server plan for the lifetime.

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD
• $4/month

[Order Now]

SSD-2

Please use the Coupon Code HPYSSD2 to get $5 discount on SSD-2 Virtual Server plan for the lifetime.

• 2GB RAM
• 2GB vSwap
• 4x vCPU
• 40GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD2
• $7/month

[Order Now]

KVM SSD Server Offers (Unmanaged)

Unmanaged KVM servers also not offering free support and service monitoring.

KVM-1

• 1GB RAM
• 1x vCPU
• 15GB SSD Space
• 1TB Transfer
• 1Gbps Uplink
• 1x IPv4
• KVM/SolusVM
• $5/month

[Order Now]

Looking Glass:

https://lg-uk.happybeehost.com/

Available OS Templates:

• CentOS 8
• CentOS 7
• CentOS 6
• Ubuntu 18.04
• Ubuntu 16.04
• Ubuntu 14.04
• Debian 10
• Debian 9
• Debian 8

15-Day Money-Back Guarantee

If you decide to cancel your account within 15 days of sign up, HappyBee Host will refund you the whole amount. We value customer satisfaction. You just need to open a ticket with our Billing Department and the Cancellation Type should be "Immediate".

✅NVMe SSD Disks in RAID + ECC RAM
✅Singapore Datacenter
✅1Gbps ports
✅Free Remote Backup
✅VNC access
✅Custom ISO - netboot
✅99.9% uptime
✅Virtualizor control panel
✅24 hour money-back policy

KVM plans - coupon TriptoSG

VPS - KVM1G SG

1GB DDR4 ECC RAM
1vCore @3.7+Ghz
5GB NVMe SSD RAID 1 disk
1 x IPv4
125GB High-speed Bandwidth per month
$1.8 Recurring - Order Now


VPS - KVM2G SG

2GB DDR4 ECC RAM
1vCore @3.7+Ghz
15GB NVMe SSD RAID 1 disk
1 x IPv4
250GB High-speed Bandwidth per month
$3.6 Recurring - Order Now


VPS - KVM4G SG

4GB DDR4 ECC RAM
2vCore @3.7+Ghz
25GB NVMe SSD RAID 1 disk
1 x IPv4
0.5TB High-speed Bandwidth per month, then reduced speeds.
$7.2 Recurring - Order Now


Coupon TriptoSG valid on all plans
See all KVM plans >>> https://my.webhorizon.in/order/main/packages/vps/?group_id=12

OpenVZ plans - coupon TriptoSG

VPS - VZ256 SG

256MB DDR4 ECC RAM
10GB HDD RAID 1 disk
1 vCore @3.5+ Ghz
1 x IPv4 + /112 IPv6
0.25TB High-speed Bandwidth per month, then reduced speeds.
$7.2/YEAR Recurring - Order Now

VPS - VZ1G SG

1GB DDR4 ECC RAM
30GB HDD RAID 1 disk
1 vCore @3.5+ Ghz
1 x IPv4 + /112 IPv6
1TB High-speed Bandwidth per month, then reduced speeds.
$14.4/YEAR Recurring - Order Now


Coupon TriptoSG valid on all plans
See all ovz plans >>> https://my.webhorizon.in/order/main/packages/vps/?group_id=29

Hardware for KVM plans -> Intel® Xeon® E-2276G Processor @ 3.8 Ghz server grade cpu with Intel NVMe SSD drives datacenter grade
Hardware for OVZ plans -> Intel® Xeon® Processor E3-1270 v6 @ 3.8 Ghz server grade cpu with sata3 hdd datacenter grade

Thank you.

I bought a few Virtual Private Servers (VPS) on Black Friday, and have been busy setting them up.
Nowadays, most VPS comes with an IPv6 subnet that contains millions of possible addresses.
Initially, only one IPv6 address is assigned to the server, but the user can assign additional addresses as desired.
Given that I plan to run multiple services within a server, I added a few more IPv6 addresses so that each service can have a unique IPv6 address.

One of my servers is using OpenVZ 7 virtualization technology, in which I installed Debian 10 operating system.
Commonly, OpenVZ 7 uses virtual network device (venet) that does not have a MAC address.
venet devices are not fully IPv6 compliant, but still works if you statically assign IPv6 addresses.
Moreover, every IP address used in a container must be configured from the host node, because venet would drop ip-packets from the container with a source address, and in the container with the destination address, which is not corresponding to an ip-address of the container.
Therefore, I must use the VPS control panel, in this case SolusVM, to assign IPv6 addresses to my server:

In the Add IP section, the IPv6 subnet prefix 2001:db8:f1c1:8454:0964: is already shown.
Notice that I am putting a colon (:) in front of the suffix beef, so that they concatenate to the full address 2001:db8:f1c1:8454:0964::beef.
Forgetting this colon would cause "Invalid Entry" error.

After making this change in the SolusVM control panel, the /etc/network/interface file on my server is updated automatically:

# This configuration file is auto-generated.
# WARNING: Do not edit this file, otherwise your changes will be lost.
# Please edit template /etc/network/interfaces.template instead.
auto lo
iface lo inet loopback
# Auto generated venet0 interfaces
auto venet0
iface venet0 inet static
        address 127.0.0.1
        netmask 255.255.255.255
        broadcast 0.0.0.0
        up route add default dev venet0
iface venet0 inet6 static
        address ::2
        netmask 128
        up ip -6 r a default dev venet0
        up ip addr add 2001:db8:f1c1:8454:0964::2/80 dev venet0
        up ip addr add 2001:db8:f1c1:8454:0964::beef/80 dev venet0
auto venet0:0
iface venet0:0 inet static
        address 10.10.23.159
        netmask 255.255.255.255

I'm also seeing two IPv6 addresses:

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/void
    inet 127.0.0.1/32 scope host venet0
       valid_lft forever preferred_lft forever
    inet 192.0.2.30/32 brd 192.0.2.30 scope global venet0:0
       valid_lft forever preferred_lft forever
    inet6 2001:db8:f1c1:8454:0964::beef/80 scope global
       valid_lft forever preferred_lft forever
    inet6 2001:db8:f1c1:8454:0964::2/80 scope global
       valid_lft forever preferred_lft forever
    inet6 ::2/128 scope global
       valid_lft forever preferred_lft forever

I intend to host my secret beef recipes on its unique IPv6 address 2001:db8:f1c1:8454:0964::beef, and use the other address 2001:db8:f1c1:8454:0964::2 for outbound traffic such as pings and traceroutes.
However, I noticed that the wrong address is being selected for outgoing packets:

$ ping 2001:db8:9f16:8fc7::9

$ sudo tcpdump -n icmp6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens3, link-type EN10MB (Ethernet), capture size 262144 bytes
10:25:18.264905 IP6 2001:db8:f1c1:8454:0964::beef > 2001:db8:9f16:8fc7::9: ICMP6, echo request, seq 1, length 64
10:25:18.265014 IP6 2001:db8:9f16:8fc7::9 > 2001:db8:f1c1:8454:0964::beef: ICMP6, echo reply, seq 1, length 64
10:25:19.264939 IP6 2001:db8:f1c1:8454:0964::beef > 2001:db8:9f16:8fc7::9: ICMP6, echo request, seq 2, length 64
10:25:19.265013 IP6 2001:db8:9f16:8fc7::9 > 2001:db8:f1c1:8454:0964::beef: ICMP6, echo reply, seq 2, length 64

I started searching for a solution, and learned that:

• Default Address Selection for Internet Protocol version 6 (IPv6) is a very complicated topic.

• An application can explicitly specify a source address.
  For example, I can invoke ping -I 2001:db8:f1c1:8454:0964::2 2001:db8:9f16:8fc7::9 to use the desired source address.

• Each local IPv6 address can be either "preferred" or "deprecated".
  If the application does not specify a source address, the system would prefer to use a "preferred" address instead of a "deprecated" address.

As shown in the ip addr output above, currently both addresses are "preferred" on my server.
This means, both addresses are equally possible of being used as the default source address.
If I can make 2001:db8:f1c1:8454:0964::2 "preferred" and all other addresses "deprecated", I would achieve my goal of making 2001:db8:f1c1:8454:0964::2 the default source address for outbound traffic.

How can I set an IPv6 address as "deprecated"?
After some digging, I found that it is controlled by the preferred_lft (preferred lifetime) attribute.
This attribute indicates the remaining time an IP address is to remain "preferred".
Unless it is set to "forever", preferred_lft counts down every second, and the IP address becomes "deprecated" when it reaches zero.
If the IP address was added with preferred_lft set to zero, it would be "deprecated" since the beginning.

The command to change preferred_lft of an existing IPv6 address is:

sudo ip addr change 2001:db8:f1c1:8454:0964::beef/80 dev venet0 preferred_lft 0

This change takes effect immediately, and outgoing packets start using 2001:db8:f1c1:8454:0964::2 as source address, as I wanted.
However, after a reboot, both IPv6 addresses would become "preferred" again.

As we have seen, the /etc/network/interfaces file is adding IPv6 addresses in a post-up command that runs after ifupdown package brings the interface up.
Can we change this command and set preferred_lft to zero?

So I modified the /etc/network/interfaces file, changing that line to:

up ip addr add 2001:db8:f1c1:8454:0964::beef/80 dev venet0 preferred_lft 0

However, modifying /etc/network/interfaces in an OpenVZ 7 container would not work.
Although I can see the modification right away, after a reboot, the file is automatically restored to the default state, reverting any changes.

After poking around for a while, I figured out the solution: create a systemd service to change the preferred_lft attribute.
The following commands will do the magic:

sudo apt install -y jq
sudo mkdir -p /usr/local/bin

sudo tee /usr/local/bin/network-preferredlft.sh > /dev/null <<'EOT'
#!/bin/bash
set -e
set -o pipefail

ip -j addr show dev $IFACE \
  | jq -r '
    .[] | select(.addr_info) | .addr_info[] |
    select(.family=="inet6" and .scope=="global") |
    select(.local | (endswith(":1") or endswith(":2")) | not) |
    "ip addr change "+.local+"/"+(.prefixlen|tostring)+" dev "+env.IFACE+" preferred_lft 0"' \
  | sh
EOT

sudo chmod +x /usr/local/bin/network-preferredlft.sh

sudo tee /etc/systemd/system/network-preferredlft.service > /dev/null <<'EOT'
[Unit]
Description=Change preferred_lft
Documentation=https://yoursunny.com/t/2020/preferred-lft-vz7/
After=network-online.target
Wants=network-online.target

[Service]
Environment="IFACE=venet0"
Type=oneshot
ExecStart=/usr/local/bin/network-preferredlft.sh

[Install]
WantedBy=multi-user.target
EOT

sudo systemctl daemon-reload
sudo systemctl enable network-preferredlft

The script /usr/local/bin/network-preferredlft.sh retrieves a list of IP addresses assigned to the network interface specified by the environment variable $IFACE.
For each global-scope IPv6 address that does not end with :1 or :2, the preferred_lft attribute is changed to zero.

After executing the above command and rebooting, I can see that the IPv6 address 2001:db8:f1c1:8454:0964::beef is correctly marked as "deprecated" and no longer selected as the default source address.
Now I can securely host my secret beef recipes on 2001:db8:f1c1:8454:0964::beef without worrying about others discovering this "deprecated" IPv6 address through my outbound network traffic.

$ ip addr show dev venet0
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
    link/void
    inet 127.0.0.1/32 scope host venet0
       valid_lft forever preferred_lft forever
    inet 192.0.2.30/32 brd 192.0.2.30 scope global venet0:0
       valid_lft forever preferred_lft forever
    inet6 2001:db8:f1c1:8454:0964::beef/80 scope global deprecated
       valid_lft forever preferred_lft 0sec
    inet6 2001:db8:f1c1:8454:0964::2/80 scope global
       valid_lft forever preferred_lft forever
    inet6 ::2/128 scope global
       valid_lft forever preferred_lft forever

$ ping 2001:db8:9f16:8fc7::9

$ sudo tcpdump -n icmp6
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens3, link-type EN10MB (Ethernet), capture size 262144 bytes
11:03:40.185496 IP6 2001:db8:f1c1:8454:0964::2 > 2001:db8:9f16:8fc7::9: ICMP6, echo request, seq 1, length 64
11:03:40.185598 IP6 2001:db8:9f16:8fc7::9 > 2001:db8:f1c1:8454:0964::2: ICMP6, echo reply, seq 1, length 64
11:03:41.187229 IP6 2001:db8:f1c1:8454:0964::2 > 2001:db8:9f16:8fc7::9: ICMP6, echo request, seq 2, length 64
11:03:41.187273 IP6 2001:db8:9f16:8fc7::9 > 2001:db8:f1c1:8454:0964::2: ICMP6, echo reply, seq 2, length 64

This article explained how to change default IPv6 source address selection by marking an IPv6 address "deprecated" via a systemd service that invokes ip addr command after ifupdown brings up the network interface.
The described technique works in OpenVZ 7 and Debian 10, and has been tested in a VPS provided by Gullo's Hosting.
If you are using KVM and Ubuntu 20.04, check out How to Select Default IPv6 Source Address for Outbound Traffic with Netplan.

WireGuard is an exciting, new, extremely simple VPN system that uses state-of-the-art cryptography. Its Linux implementation runs in the kernel, which provides a significant performance boost compared to traditional userspace VPN implementations

The WireGuard kernel module is great, but sometimes you might not be able to install new kernel modules. One example scenario is on a VPS that uses OpenVZ or LXC. For these cases, we can use wireguard-go, a userspace implementation of WireGuard. This is the same implementation used on MacOS, Windows, and the WireGuard mobile apps. This implementation is slower than the kernel module, but still plenty fast.

This post focuses on Debian, however the instructions should mostly work on other Linux distros too.

Install WireGuard Tools

We need to install the WireGuard tools (wg-quick). On Debian, you can run this as root:

echo "deb http://deb.debian.org/debian/ unstable main" > /etc/apt/sources.list.d/unstable.list
printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n' > /etc/apt/preferences.d/limit-unstable
apt update
apt install wireguard-tools --no-install-recommends

(see the WireGuard site for instructions if you're not on Debian)

Install Go

Unfortunately, since wireguard-go is not packaged for Debian, we need to compile it ourselves. To compile it, we first need to install the latest version of the Go programming language (currently version 1.13.4).

cd /tmp
wget https://dl.google.com/go/go1.13.4.linux-amd64.tar.gz
tar zvxf go1.13.4.linux-amd64.tar.gz
sudo mv go /opt/go1.13.4
sudo ln -s /opt/go1.13.4/bin/go /usr/local/bin/go

Now, running go version should show the version number.

Compile wireguard-go

Now that we've got Go, we can download and compile wireguard-go. Download the latest release version:

cd /usr/local/src
wget https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20191012.tar.xz
tar xvf wireguard-go-0.0.20191012.tar.xz
cd wireguard-go-0.0.20191012

If you are on a system with limited RAM (256 MB or lower), which you probably are if you're on this forum, you will need to do a small tweak to the wireguard-go code to make it use less RAM. Open device/queueconstants_default.go and replace this:

MaxSegmentSize             = (1 << 16) - 1 // largest possible UDP datagram
PreallocatedBuffersPerPool = 0 // Disable and allow for infinite memory growth

With these values (taken from device/queueconstants_ios.go):

MaxSegmentSize             = 1700
PreallocatedBuffersPerPool = 1024

This will make it use a fixed amount of RAM (~20 MB max), rather than allowing memory usage to grow infinitely.

Now we can compile it:

make
# "Install" it
sudo cp wireguard-go /usr/local/bin

Running wireguard-go --version should work and show the version number.

If you have multiple VPSes that use the same OS version and architecture (eg. Debian 10, 64-bit), you can compile it on one of them and then just copy the wireguard-go binary to all the others.

Configuration

wg0.conf

You'll need to configure /etc/wireguard/wg0.conf to contain the configuration for your peer. This post won't go into significant detail about this; please refer to another general WireGuard guide (like this one) for more details. The basic jist is that you need to run:

wg genkey | tee privatekey | wg pubkey > publickey

to generate a public/private key pair for each peer, then configure the [Interface] with the private key for the peer, and a [Peer] section for each peer that can connect to it.

Your wg0.conf should end up looking something like:

[Interface] 
Address = 10.123.0.2
PrivateKey = 12345678912345678912345678912345678912345678
ListenPort = 51820

[Peer] 
PublicKey = 987654321987654321987654321987654321987654321
AllowedIPs = 10.123.0.1/32
Endpoint = 198.51.100.1:51820

systemd

We need to modify the systemd unit to pass the WG_I_PREFER_BUGGY_USERSPACE_TO_POLISHED_KMOD flag to wireguard-go, to allow it to run on Linux. Open /lib/systemd/system/wg-quick@.service, find:

Environment=WG_ENDPOINT_RESOLUTION_RETRIES=infinity

and add this line directly below:

Environment=WG_I_PREFER_BUGGY_USERSPACE_TO_POLISHED_KMOD=1

Finally, enable and start the systemd service:

systemctl enable wg-quick@wg0
systemctl start wg-quick@wg0

Enabling the systemd service will connect the VPN on boot, and starting the systemd service will connect it right now.

You're Done

Now, everything should be working! You can check the status of wg-quick by running systemctl status wg-quick@wg0, which should return something like:

● wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0 
   Loaded: loaded (/lib/systemd/system/wg-quick@.service; enabled; vendor preset: enabled) 
   Active: active (exited) since Mon 2019-07-01 06:30:30 UTC; 1 day 22h ago 

Running wg will give you a list of all the peers, and some details about them:

interface: wg0
  public key: 987654321987654321987654321987654321987654321
  private key: (hidden)
  listening port: 38917

peer: 987654321987654321987654321987654321987654321
  endpoint: 198.51.100.1:51820
  allowed ips: 10.123.0.1/32
  latest handshake: 1 day, 22 hours, 59 minutes, 34 seconds ago
  transfer: 2.75 KiB received, 2.83 KiB sent

I believe lxc has very much evolved these years, with few people using it for production, so anything you can say about it, performance , resource-overhead etc.
Maybe providers who do LXC can throw some light

Also, lets add a poll.

For anyone running Debian or Ubuntu in OpenVZ 7 containers, what has your experience been upgrading between OS versions, à la dist-upgrade/do-release-upgrade? Is it safe to assume it works these days, or would you rather reinstall a provided template?

@AnthonySmith At InceptionHosting in particular, is it safe to upgrade my servers without reinstalling?

Thanks.

OpenVZ server Offers

OpenVZ SATA Server Offers

HDD-1

 
No Coupon Code Needed!
 

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB HDD Space
• 1TB Transfer
• 1Gbps Uplink
• 1x IPv4
• OpenVZ/SolusVM
• $3/month

[Order Now]
 

HDD-2

 
No Coupon Code Needed!
 

• 2GB RAM
• 2GB vSwap
• 4x vCPU
• 40GB HDD space
• 2TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• $6/month

[Order Now]
 

OpenVZ SSD Server Offers

SSD-Mini

 
No Coupon Code Needed!
 

• 1GB RAM
• 1x vCPU
• 15GB SSD space
• 750GB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• $2.5/month (If you choose Quarterly, Semi-Annually, Annually billing periods the server will be available at $2/month)

[Order Now]
 

SSD-1

 
Please use the Coupon Code HPYSSD to get $3 discount on SSD-1 Virtual Server plan for the lifetime.
 

• 1GB RAM
• 1GB vSwap
• 4x vCPU
• 30GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD
• $4/month

[Order Now]
 

SSD-2

 
Please use the Coupon Code HPYSSD2 to get $5 discount on SSD-2 Virtual Server plan for the lifetime.
 

• 2GB RAM
• 2GB vSwap
• 4x vCPU
• 40GB SSD space
• 1TB transfer
• 1Gbps uplink
• 1x IPv4
• OpenVZ/SolusVM
• Coupon: HPYSSD2
• $7/month

[Order Now]
 

Looking Glass:

https://lg-uk.happybeehost.com/

Available OS Templates:

• CentOS 8
• CentOS 7
• CentOS 6
• Ubuntu 18.04
• Ubuntu 16.04
• Ubuntu 14.04
• Debian 10
• Debian 9
• Debian 8

30-Day Money-Back Guarantee

If you decide to cancel your account within 30 days of sign up, HappyBee Host will refund you the whole amount. We value customer satisfaction. You just need to open a ticket with our Billing Department and the Cancellation Type should be "Immediate".

After testing a bit these are my initial thought. (I might be wrong.)

Pros:

• Usually cheap(er than KVM)
• Templates, disk usage lower (<400 MB for Debian 10)
• Lower memory usage, more free memory (running the same processes)
• Theoretically it could/should have lower overhead CPU wise? (I haven't experienced/been able to confirm this.)
• For the provider: Easier to monitor/stop/prevent abuse

Cons:

• Less options for OS selection (share Linux kernel, can't install BSD etc.)
• Monitoring by provider easier
• Server can more often be a bit heavier utilized/more crowded (?)
• Can't load kernel specific stuff/modules (due to shared kernel)
• Not everything works (as an example, stick with iptables, not nftables, for the time being)

There might also be other limitations I should have mentioned?

One thing I've noticed, is for disk I/O, I get something like this on my OpenVZ 7 instances:

 Disk Speed:
   1st run    : 232 MB/s
   2nd run    : 684 MB/s
   3rd run    : 774 MB/s

So, 1st run is much slower than the next. I didn't see that as clearly on a KVM node, but I'm not sure if it's really related to KVM vs. OVZ, maybe it has more to do with caching.

I've also noticed on an OpenVZ 7 instance with 2 vCPU that "multi core" CPU benchmark scores were lower than the single core score. But I have no idea of why, so I'll just mention it in case it's relevant.

TL;DR

All in all, if the price is right, OpenVZ 7 might still be a good alternative, if the limitations is something you can live with.

There much I don't know, so there might be vital points I've missed.

but this time on openvz 7 , when i run it , it shows only "segmentation fault"
i tried almost all OS Debian 9, 10, ubuntu 14, 16, 18 ... all shows same error

so i can assume it is related to openvz 7

Please , can some one help me to solve this ?

Is it only me or anyone else having the same issue ?

Thanks

1. KVM provides more isolation & ability to run own kernel but does everyone need own kernel?
2. Security vulnerabilities which got discovered in OpenVZ a few years ago but almost everything we run these days including the processors have vulnerabilities
3. It could also be because IP addresses have become expensive & only those who own large IP space can afford to provide it? Because number of OpenVZ containers running on a node are much more than a KVM node with same hardware
4. LXC has become part of mainline kernel?

Isn't it more difficult to keep abuse under check in bare metal virtualization like KVM whereas in OpenVZ it only takes a script like Nodewatch to do it?

Would do you guys think? Would love to hear from providers & users both

If your host does not have them available yet point them here