# LXConsole v0.6.1 Web Console for Incus/LXD

**URL:** https://discussion.scottibyte.com/t/lxconsole-v0-6-1-web-console-for-incus-lxd/513
**Category:** Uncategorized
**Created:** [December 21, 2024, 1:00am UTC](https://discussion.scottibyte.com/t/lxconsole-v0-6-1-web-console-for-incus-lxd/513 "2024-12-21T01:00:50Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![scott](https://discussion.scottibyte.com/letter_avatar_proxy/v4/letter/s/3e96dc/32.png) [@scott](https://discussion.scottibyte.com/u/scott)
#### Post date: [December 21, 2024, 1:00am UTC](https://discussion.scottibyte.com/t/lxconsole-v0-6-1-web-console-for-incus-lxd/513/1 "2024-12-21T01:00:50Z")

</div>

LXConsole v0.6.1 was just released. It is mainly a maintenance release, but offers a couple notable additions. If you are new to LXConsole, you will want to watch [LXConsole Web Interface for Incus](https://www.youtube.com/watch?v=3b0GDMb-vKg).

The release notes for LXConsole are [here](https://github.com/PenningLabs/lxconsole/releases).

To upgrade your LXConsole, connect to the server/container on which it is installed. In my case:

```auto
ssh lxconsole

```

If you followed my installation guide, you will want to move into the folder where LXConsole is installed.

```auto
cd lxconsole

```

Pull the new container:

```auto
docker compose pull

```

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/4/4cf20a7df2ba38977b3594c50456ca3baa670254.jpeg)

Rather than simply launching the new container, I stopped and deleted the old container to cleanup the server and avoid old versions from lingering. First, see the currently running docker:

```auto
docker ps

```

![image](https://discussion.scottibyte.com/uploads/default/optimized/2X/b/ba34968785715808fe64a3193781ae8458c2c1a9_2_690x44.jpeg)

Next, stop the container using either its name or the container ID:

```auto
docker stop lxconsole-lxconsole-1

```

![image](https://discussion.scottibyte.com/uploads/default/original/2X/6/6f98d2e50cf9d583954bbbad00e6baf942e2f939.png)

Delete the container since the old one is no longer needed:

```auto
docker rm lxconsole-lxconsole-1

```

![image](https://discussion.scottibyte.com/uploads/default/original/2X/e/ed8729fd15bec05a6cab4068ff3779f48c813ca5.png)

Restart the new application.

```auto
docker compose up -d

```

![image](https://discussion.scottibyte.com/uploads/default/original/2X/c/c4f58b867bd2098a2d2fae53d4c94d74f8add555.png)

In v0.6.1, if you decide to enable mutifactor authentication (2fa TOTP), you will now see the encryption key as an option rather than just the QR Code. To access the Multifactor Authenitcation option, click on your username in the upper right hand corner of the web interface and select the “account” option. This new capability to access the 2fa key is helpful for recording 2fa authorization keys in programs like Bitwarden.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/d/d484151576f715ea2934d8701b7ad37223cc93c4.jpeg)

I don’t personally enable 2fa TOTP for my primary LXConsole installation because it is only available inside my private LAN and so I use a VPN to access it if I am external to the network. If you are managing a business or you decide to offer your LXConsole on the web, it is advisable to enable 2fa.

The “Backup” option in LXConsole is the GUI equivalent of the “incus export” or “lxc export” commands to perform a standalone backup that can be imported into a another server or which can be restored in the event of a catastrophic loss.

The difference is that the “incus export” or “lxc export” commands create the backup file and export it outside of the server data structures in one operation. In contrast, the LXConsole Backup command performs only the backup. LXConsole provides an additional option to export a completed backup to a file.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/3/3e12b45938a2991728a704f3a734d830eb9425fb.jpeg)

By default, LXConsole uses gzip compression to perform backups. Gzip works great, but can be very slow on larger containers. Incus containers support LZ4 compression which is considerably faster and more efficient. I asked Matthew Penning to add an option to the compression drop down in the backup instance menu to incude LZ4 as an option. This is new to LXConsole 0.6.1.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/8/8eb82a94e97cba3ee2c35557384c79308f4265b5.png)

Before you can perform a backup using lz4 compression, you must have installed it on your incus server. Go to your incus server and install lz4 from the terminal prompt:

```auto
sudo apt install lz4

```

With lz4 installed, I can go back to LXConsole and initiate a backup using lz4 compression.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/a/a0f47564c59e56779e984e21c274f028fe08f508.jpeg)

On average, I have found that a backup using lz4 is 5-10 times faster than a backup using gzip compression.

When your backup has been completed, it will show “completed”, but it still needs to be exported to a file that you will want to store externally to your server.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/b/b42bde03a466459c4319d706516dbc913dd8e637.jpeg)

Click on the icon of the document with the arrow to the right of the backup you just completed under the actions column and that will initiate the export.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/e/ec83992840025475b3828e2e31cbd273f5e3a982.jpeg)

This will pop up an acknowledgment window.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/b/bdae61a863285ead1108993246ffb9d14ac92dd2.png)

After a minute or so, you will see that your backup has been exported to the folder you specified in the docker-compose file.

 ![image](https://discussion.scottibyte.com/uploads/default/original/2X/5/5b2414ad84aa277fa30d253f93d57aade9341b2d.jpeg)

Please support Matthew Penning at Penning Labs for the hard work that he continues to provide on this excellent open source project.