ZAP-Hosting Lifetime Servers - Discussion, Updates
This should be a discussion Thread concerning ZAP-Hosting's Lifetime Servers/Offers
ZAP-Hosting (German company, founded in 2010), after providing Lifetime Minecraft Servers for many years have recently extended their product line to include:
- Lifetime "vServer" (LXC); from 79€ for 2vCores, 8GB RAM, 25GB, 500 Mbit/s, 1 IPv4
- Lifetime "Rootserver" (KVM); from 154.80€, 4vCores, 8GB RAM, 60GB SSD NAS, 500 Mbit/s, 1Ipv4, Intel Xeon E5-2650v2/Intel Xeon E5-2667v2
- Lifetime Dedicated Servers; from 572.80€ for 1x Intel Xeon E5-2603v2, 4 Cores, 1,8 Ghz base clock, 64GB RAM, 500GB SSD, 1 IPv4
- Lifetime Webhosting; from 46.80€ for 5GB, 40 e-Mail accounts, 40 MySQL databases, they use Plesk.
You will find that the products first display the monthly price, but in the box to the right where the price total is displayed there is an option where you can click "OR xx€ lifetime".)
According to the ZAP-Hosting website, there are currently 4043+ active Lifetime Servers , and about 32863 active servers in total. This suggests that while lifetime deals are often considered to be a rip-off and not sustainable, even after deducting 5000-lifetime servers, there would still be about 27000 active servers that are paid through subscriptions/prepaid contracts, suggesting that ZAP-Hosting has enough revenue to sustain their lifetime offers and/or doesn't just vanish overnight.
The total assets were counted as 1.926.615€ in 2021 according to data from Northdata (link above).
The catch (MUST READ!):
ZAP-Hosting, in the light of extending their lifetime server product line, seems to have updated their Terms of Service now requiring ALL their customers who purchased any kind of lifetime product (Minecraft Server/Webspace/vServer/Rootserver/Dedicated Server and future offerings) to log into their ZAP-Hosting Dashboard AND open up the respective product's control panel (e.g. if you have a vps with them, open the vps control panel; if you have a Minecraft Server..) once every 3 months to avoid suspension due to inactivity. If you service/product has been suspended due to inactivity you will apparently receive an email stating that you have 4 weeks to contact them, before your service/product gets cancelled permanently and any right to refund is waived.
ToS excerpt regarding lifetime products (April 9th, 2023):
§ 10 Lifetime products
(1) Products designated as lifetime products are paid for once instead of recurring.
(2) The term Lifetime/infinite/lifelong describes the lifelong right to use the product until it becomes inactive.
(3)** The case of inactivity occurs if the named lifetime product is not accessed by the customer in the customer web interface within 3 months. ZAP-Hosting then reserves the right to switch off and block the product.
If the customer does not contact us for a further 4 weeks after the blocking (grace period), the product will be permanently deleted and the entitlement to lifelong use will be cancelled.** The customer expressly waives the right to a refund of the purchase price.
After contacting us within the grace or blocking period, the inactivity case will be lifted for the time being and the product will be fully usable again.
(4) Lifetime products cannot be paid for with ZAP credits (ZAP Coins) or ZAP coin voucher codes.
I confirmed via Ticket that you DO NOT get a warning before the service gets suspended and was advised by the support staff to add a reminder on my phone (e.g. Google Calendar) to remember to log into the Dashboard and open up the product page. The support staff, however, indicated that during time of suspension, the data would not be removed from the service, albeit they stated that it's always good to have backups in the same sentence. I suggested they contact their customers 1-2 weeks PRIOR to suspension in order to avoid production service suddenly getting suspended and apparently my suggestion was forwarded to whomever (likely /dev/null ).
I also confirmed via ticket that the new change with the inactivity clause affects ALL lifetime products and ALL customers, no matter when the product was purchased.
This means that anyone who purchased a Minecraft lifetime server from any of these Threads ( Thread LES, Thread 1 LET, Thread 2 LET) is affected by this and should log into the dashboard and open up their Minecraft server page asap to avoid any suspension for inactivity and/or possible deletion.
Ironically, @Neoon mentioned in one of the threads that ZAP Hosting had such an inactivity clause in the past, but at the time of ordering the Minecraft Servers back then this clause had been removed and only came back to light with the extension of the lifetime product line, it seems.
This part about the inactivity clause sounds tedious and annoying, but I'm sure some people might still be tempted and bite. I am/was tempted myself but holding back due to the annoying clause about inactivity.
I am a lifetime hoarder at heart and I can live with Ivacy VPN requesting me to contact them once every 5 years to extend the offer, but logging into the Dashboard once every 3 months is really annoying.
The company has been around for 13 years now and it's likely not going anywhere so fast. It has, however, also never been known to have a stellar reputation in the german gamserver market in terms of performance and customer reviews.
Installing newer Debian/Ubuntu versions (Debian 11/12, Ubuntu 20/22) on Rootservers:
As ZAP doesn't provide these images natively in the Webinterface for Rootservers atm (only for LXC),
you can try @rootnet guide for netboot to install any os, which works great:
Could you please make a thread on how you install it? You did it from the netboot, right? Maybe a step by step instructions on how to install the OS if the host doesn't support CDROMs?
Thanks @Ympker for the shout.
Disclaimer: I made this guide in a hurry. The wordings may not be accurate with what you would be seeing on your screen while accessing zap dashboard or netboot.xyz menu. @Ympker has already tried this guide so I'll let him jump in and mention if there's any corrections needed or any additions/removal required.
Here you go mate
First thing first, make a note of your IP details, you'll need this later in netboot.xyz couple of times.
IP: 111.222.333.444 (your server's IPv4)
subnet: 255.255.255.0 (with zap-hosting it's always this for linux and windows rootserver)
gateway: 111.222.333.1 (The gateway is always the IPv4 address with a 1 at the end)
Step 1: install grub-imageboot
If grub is not already installed in your machine, you can do it so by
apt install grub-imageboot
Step 2: adding netboot.xyz in grub menu
Step 3: Access your server via VNC
In your Zap dashboard, go to your rootserver and click VNC-Console under tools. Click on 'start vnc tunnel' and then open the vnc webclient.
Step 4: Accessing netboot.xyz
reboot your server by sending ctrl+alt+del command in your VNC browser tab. As soon as it reboots, you will see Proxmox boot screen. And soon after that you'll see the grub menu (blue screen). Once you see blue screen/grub menu, use your arrow buttons and select netboot.xyz. The option should show as 'bootable iso image: netboot.xyz' or something similar.
Step 5: setting up network interface in netboot.xyz
Once you select netboot.xyz in step 4, let it do its thing. It'll take few seconds and then you'll be greeted with few questions to configure your network interface. Type in these;
- Set network interface number: 0
- IP: 111.222.333.444 (your server's IPv4)
- Subnet: 255.255.255.0
- Gateway: 111.222.333.1
- DNS: 188.8.131.52 or 184.108.40.206 (whatever you prefer)
and press enter. You should now be greeted with netboot.xyz menu.
Step 6: From here, I believe you are already familiar with how to use netboot.xyz. If not, here's how I do it. I'll post steps for ubuntu 22.04 installation
go to 'linux network installs'. Select Ubuntu and then 22.04 and then select install.
netboot.xyz will do it's thing to prepare the installation. It's going to take its time. Don't be alarmed if the text shows "done" multiple times and there's no activity after that. Netboot is still doing its thing in the backend. Eventually (after 1-2 mins), netboot will say "unable to find a medium with live file system. And it will ask you few questions. Input these answers
- attempt interactive netboot from a URL? yes
- static or dhcp ip config? static
- IP: 111.222.333.444 (your server's IPv4)
- Subnet: 255.255.255.0
- Gateway: 111.222.333.1
- DNS: 220.127.116.11 (if you want to add more than 1 nameserver, you can do so here. Just leave a space between each entry, for example 18.104.22.168 22.214.171.124 126.96.36.199)
- vlan id: leave it blank
- url: the default url configured in netboot is for the previous version. It does not work. so type in https://releases.ubuntu.com/jammy/ubnutu-22.04.2-live-server-amd64.iso (or you can use any ubuntu mirrors or your own link to the ubuntu ISO. If Ubuntu releases a newer version by the time you read this, make sure you adjust the URL accordingly.)
- http_proxy: leave it blank
It will start downloading the ISO and then greet you with the Ubuntu live installer screen. From here, simply follow the on screen prompts to install the ubuntu server. Make sure you select 'install ssh server' when it asks in the installation steps.
Steps for installing Debian should be the same, but much more simpler. With debian installation, you won't have to enter an url for ISO download. The only place where debian installer will fail is on the network config page. By default debian installer tries DHCP. It will say network config failed. All you have to do is select 'static network' on that screen, enter the IP details you noted down earlier and then carry on with the remaining on-screen prompts.