<p>I just deleted the original folder and installed from scratch.</p>

CC BY-SA 4.0
2018-08-07T02:54:49.597Z
2018-08-07T02:54:49.597Z
Fontaine
<p>I downloaded the latest github .zip for version 0.6 and unpacked it but when I check the version I am running it returns:</p>

<pre><code>v0.5.2-2016-11-21-1644-g1616fcb
</code></pre>

<p>Any idea what I did incorrectly? What's the proper way to update C-Lighting from the terminal in Ubuntu?</p>

CC BY-SA 4.0
2018-08-01T06:49:02.797Z
When you run it, what command are you using? Did you build and install 0.6 in the same location your path points to?
meshcollider
CC BY-SA 4.0
2018-08-01T09:57:25.573Z
You can see which binary executes by using `which lightningd`. Like @MeshCollider mentions, this is likely due to the old binary being executed instread of the new one
cdecker
CC BY-SA 4.0
2018-08-03T01:56:42.737Z
I am using this command to run it: lightningd/lightningd --network=bitcoin --log-level=debug --ipaddr=$my_ip --alias=someNode. Sorry I am very new to this. All I did was download the latest .zip file from the github and unpacked it in my existing lightning folder that has the previous binary. What should I do differently? TIA
Fontaine
CC BY-SA 4.0
2018-08-05T12:28:12.003Z
Is there a `lightning` in your directory? You might have nested the installations. The simplest way to solve it is to move/remove the origin directory and unzip the release in a new directory.
cdecker
<core-lightning>
What is the proper way to update C-Lightning?
Fontaine
# What is the proper way to update C-Lightning?

(Asked by: username_0 on 2018-08-01)

I downloaded the latest github .zip for version 0.6 and unpacked it but when I check the version I am running it returns:
v0.5.2-2016-11-21-1644-g1616fcb

Any idea what I did incorrectly? What's the proper way to update C-Lighting from the terminal in Ubuntu?

**Tags:** core-lightning

> **Comments:**
> **username_1**: When you run it, what command are you using? Did you build and install 0.6 in the same location your path points to?  
> **username_2**: You can see which binary executes by using `which lightningd`. Like @MeshCollider mentions, this is likely due to the old binary being executed instread of the new one  
> **username_0**: I am using this command to run it: lightningd/lightningd --network=bitcoin --log-level=debug --ipaddr=$my_ip --alias=someNode. Sorry I am very new to this. All I did was download the latest .zip file from the github and unpacked it in my existing lightning folder that has the previous binary. What should I do differently? TIA  
> **username_2**: Is there a `lightning` in your directory? You might have nested the installations. The simplest way to solve it is to move/remove the origin directory and unzip the release in a new directory.  

---

## 1 answers

### Answer by username_0 on 2018-08-07. Score: 0 | Accepted answer

I just deleted the original folder and installed from scratch.


---

