Windows 10, Bash: Ping

After installing Bash on Windows, the first thing I did like most users is to try out ping. Unfortunately it failed having an error.

Google came to the rescue and found a fix for this issue.

Command Prompt had to be run with Administrator Privileges

A success!

Hope this helps whoever stumbles upon this page with the same problem =)


Adding Ubuntu to Windows 10

Recently I heard from a colleague that Windows has added Ubuntu bash to the OS.

Original Guide from:

Lets get started:

1. Verify the OS build by going start menu > System > About

We have to be running a 64-bit version of Windows 10 Anniversary Update or later (build 1607+).

That is checked.

2. Activate Developer Mode

Start Menu > Settings > search Developer mode

Give it a moment, Windows will do some installation.

3. Enable “Windows Subsystem for Linux” – this is already part of the Windows package we have to enable it.

Open Power shell as admin and run the following command:
open start menu > search “power shell” > right click “run as adminstrator”

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

Image shows:

Seems that i have already enabled it previously – thus no it is online and no need to restart.

Next to run Bash

open command prompt and type bash then y

Personally I’m comfortable with Ubuntu so I went ahead with the install, alternatively you can search from the Windows store and download other flavors:

Once installed, you are good to go with Bash! – so I was wrong, long waiting time as usual with Microsoft.

20 mins later still installing – come on Microsoft you can do better.

Argghh all it needed was to press enter, might have been faster.

Alright! all set ready to have a Bash!

Ubuntu: sudo: unable to resolve host : Error

It becomes irritating when cloning a server only to get the hostname error again.

root@server1:~$ sudo apt update
sudo: unable to resolve host server1

This happens because the server is unable to determine the hostname of the server

Resolution includes looking at 2 files.



In /etc/hostname ensure the hostname of your server is updated, matches the current hostname of the server you are using.

sudo nano /etc/hostname

*edit file to hostname


Ctrl + x  and y to save

and in /etc/hosts

sudo nano /etc/hosts

*edit file where server1 is your hostname localhost server1

again to exit, ctrl + x then y

Ubuntu 14.04: NO_PUBKEY : Error

Ubuntu 14.04: Error

The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY

When doing sudo apt update – encountered this error

Get:65 trusty/restricted i386 Packages [13.4 kB]
Get:66 trusty/universe i386 Packages [5866 kB]
Get:67 trusty/multiverse i386 Packages [134 kB]
Get:68 trusty/main Translation-en [762 kB]
Get:69 trusty/multiverse Translation-en [102 kB]
Get:70 trusty/restricted Translation-en [3457 B]
Get:71 trusty/universe Translation-en [4089 kB]
Fetched 34.5 MB in 22s (1566 kB/s)
Reading package lists... Done
W: GPG error: trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4F4EA0AAE5267A6C
W: GPG error: trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C2518248EEA14886

Did a quick search on the web and found a solution

Link Below:

Fix apt-get update “the following signatures couldn’t be verified because the public key is not available”

Solution was to request new keys from the key server

sudo apt-key adv --keyserver --recv-keys 4F4EA0AAE5267A6C C2518248EEA14886

I had 2 missing Keys 4F4EA0AAE5267A6C and C2518248EEA14886

Command to enter would be

sudo apt-key adv –keyserver –recv-keys  [your required key]

Lazy blogger

I’m a totally lazy blogger, takes me ages to update this page. And effectively I have nothing much to blog about.
At current mucking though a Discord Bot in C# – nothing really last too long. Lets see what can be done with this and how long this last.

The setup is ready. – Running Visual Studio Code on my Ubuntu 16.04 Cloud server.  – give me a shout-out if anyone happens to stumble upon this and requires a tutorial or something.

For now i’m getting to fixing up the bot – which now can reply a !hello and !ping =)

Unturned Headless Server with Ubuntu 14.04


This would be my first tutorial of a headless installation, we will be using Steamcmd and Rocket to get the server running.

There are 3 parts to this installation.

1. Install the pre requisites the programs required to run Steam and Rocket.
2. Install steamcmd
3. Install Rocket

1. Install the programs

sudo apt-get install lib32gcc1 zip lib32stdc++6 curl

apt install mono-runtime libmono2.0-cil

If there is an error with mono during running the script, install this instead ( alittle over kill though)

sudo apt-get install mono-complete

2. Now install steamcmd

mkdir ~/Steam && cd ~/Steam
curl -sqL "" | tar zxvf -

3. Final and tricky bit to install Rocket Mod

Steps as follows, got to get the download link or use the below link if it has not expired.
sudo wget 
(download the Linux version of Rocket Mod)

Rename the file to a zip file
sudo mv download.unturned-linux.latest.44691EEF-75EC-45DF-B2FD-50320A289BA5 ./

Extract the content
sudo unzip -d ./

Finally once unpacking go to Script folder and run the file that will download all the relevant files
cd Scripts/
sudo chmod +x *.sh

At this point you would want to create a new steam account to run the server. Different from the account you use to play the game.

Replace USERNAME and PASSWORD with your steam username and password.

Its fairly simple but it took me 3 days to muck around and get the files in the right place for the setup.

once all the files are downloaded.
You are done!

In the Next post i will talk about how to run the Server and how to configure. I’m no expert so feel free to leave comments below. Some sources for this project which I got most of the information from.


Exciting content coming up

I’ve been fussing over unturned headless server for the past 3 days. Finally got it to work and wanted to write about it.

first order of business, getting this blog up running straight. have been plagued with an evening of WordPress 403 Forbidden error. lets give a while to see if the solutions works.

I’ll be back as soon as the solution shows itself to work.