# System does not fully support snapd: cannot mount squashfs image using "squashfs"

**URL:** https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689
**Category:** Help
**Created:** [September 2, 2020, 8:40pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689 "2020-09-02T20:40:48Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 8:40pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/1 "2020-09-02T20:40:48Z")

</div>

What is that? I can’t take it any longer:

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/c/d/cd2654aaad633de067bfaa4e3e5b5ebfac427eb0.png)

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 8:45pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/2 "2020-09-02T20:45:14Z")

</div>

Is that server running on OpenVZ?

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 8:50pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/3 "2020-09-02T20:50:30Z")

</div>

My server now is Ubuntu 20.04. I don’t know about that. What is OpenVZ?

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 8:52pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/4 "2020-09-02T20:52:49Z")

</div>

> [@roguitar88](#):
>
> I don’t know about that. What is OpenVZ?

It is a type of server virtualization.

That's okay, we can find out. What is the output of:

```
sudo systemd-detect-virt

```

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 8:58pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/5 "2020-09-02T20:58:05Z")

</div>

This is the output:

`openvz`

Yep. You’re right. Now what should I do?

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 9:09pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/6 "2020-09-02T21:09:04Z")

</div>

You are basically out of luck.

snaps rely on certain Linux kernel features which are not available under containerized servers like those running under `openvz`.

You can still install Certbot, it just won’t be the fully up-to-date version (but that’s okay).

```
sudo apt install certbot
```

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 9:16pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/7 "2020-09-02T21:16:29Z")

</div>

Ok, I’ve just tried the command above. But what the heck is that?

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/6/7/6750e7016c8d824f36861bfe6254a38400687df1.png)

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 9:19pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/8 "2020-09-02T21:19:44Z")

</div>

Sure, if you’re using Certbot with nginx, then:

```
sudo apt install python3-certbot-nginx
```

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 9:34pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/9 "2020-09-02T21:34:58Z")

</div>

Lol, you’re right, I was skipping a command… But could you tell me what the difference is between the command with snap and the other one without snap? I wonder if now I can install another certificate for my subdomain ([How can I add a certificate for a subdomain?](https://community.letsencrypt.org/t/how-can-i-add-a-certificate-for-a-subdomain/132459)).

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 10:14pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/10 "2020-09-02T22:14:25Z")

</div>

snap or not, Certbot is still the same program.

Based on that thread, if you have some hidden unicode somewhere in your nginx configuration, you need to identify it and get rid of it.

So if the error is `can't decode byte 0xB3`, you can try find it with:

```
sudo grep -RPn "\xB3" /etc/nginx/
```

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 10:23pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/11 "2020-09-02T22:23:29Z")

</div>

I still don’t understand about that so-much debated hidden unicode. This is my current Nginx configuration. At: /etc/nginx/sites-available/default

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 10:25pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/12 "2020-09-02T22:25:20Z")

</div>

So what’s wrong about it? I haven’t seen any special character

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 10:25pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/13 "2020-09-02T22:25:51Z")

</div>

I don’t know. If Certbot is complaining about it, it’s there somewhere. Did my `grep` command show up any results?

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 10:27pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/14 "2020-09-02T22:27:47Z")

</div>

As you can see, I executed your command and… Nothing:

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 10:27pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/15 "2020-09-02T22:27:55Z")

</div>

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/7/d/7dd80925494dd513a34264730ee9ed11d1a89c78.png)

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 10:42pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/16 "2020-09-02T22:42:08Z")

</div>

Do you still get any unicode errors produced if you run:

```
sudo certbot --nginx
```

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 10:51pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/17 "2020-09-02T22:51:28Z")

</div>

Yes, the same old error 🙄

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/f/2/f276877c83c7a087e97a66d0c8312e7e7b7a8b4e.png)

---

<div class="post-metadata">

### Author: ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)
#### Post date: [September 2, 2020, 11:09pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/18 "2020-09-02T23:09:27Z")

</div>

I see. It’s different to the error in your other thread, which was 0xb3.

I want to make it easier to help you track this down, maybe we can go about it in a simpler and faster way.

If you are OK sharing your entire nginx config, can you do:

```
sudo apt -y install netcat
sudo nginx -T | nc termbin.com 9999

```

Otherwise …

```
sudo grep -RPn "\xBD" /etc/nginx/
sudo grep -RPn "[\x80-\xFF]" /etc/nginx/
```

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 11:15pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/19 "2020-09-02T23:15:44Z")

</div>

Ok, I did everything as you requested:

sudo nginx -T | nc [termbin.com](http://termbin.com) 9999

 ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/1/0/108a6e56f2d58e514fefe415ea4ed93b9be1fcd8.png)

I just can’t understand one thing: What the heck is wrong about those lines. There is no special character there. And as for the nginx configuration, I’ve already shared this with you. See above.

---

<div class="post-metadata">

### Author: ![roguitar88](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@roguitar88](https://community.letsencrypt.org/u/roguitar88)
#### Post date: [September 2, 2020, 11:17pm UTC](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689/20 "2020-09-02T23:17:22Z")

</div>

> [@roguitar88](#):
>
> I still don’t understand about that so-much debated hidden unicode. This is my current Nginx configuration. At: /etc/nginx/sites-available/default:

It's all in here... As you can see..

[Next page](https://community.letsencrypt.org/t/system-does-not-fully-support-snapd-cannot-mount-squashfs-image-using-squashfs/132689.md?page=2)
