# Launcher behaves strangely with the new update

**URL:** https://meta.discourse.org/t/launcher-behaves-strangely-with-the-new-update/216294
**Category:** Support
**Created:** [January 28, 2022, 9:34am UTC](https://meta.discourse.org/t/launcher-behaves-strangely-with-the-new-update/216294 "2022-01-28T09:34:05Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Wurzelseppi](https://avatars.discourse-cdn.com/v4/letter/w/eada6e/32.png) [@Wurzelseppi](https://meta.discourse.org/u/Wurzelseppi)
#### Post date: [January 28, 2022, 9:34am UTC](https://meta.discourse.org/t/launcher-behaves-strangely-with-the-new-update/216294/1 "2022-01-28T09:34:05Z")

</div>

Hi,

I updated one of my boards this morning, I strangely there are a few things that were not happening before:

```plaintext
fatal: unable to access 'https://github.com/discourse/discourse_docker.git/': SSL certificate problem: unable to get local issuer certificate
error: Could not fetch origin

```

It´s running on a aws EC2 instance and it get´s updated regulary. After I got this error I ran update-ca, but it didn´t solve the problem

> INFO – : \> cd /var/www/discourse && [! -d ‘node\_modules’] || su discourse -c ‘yarn install --production && yarn cache clean’  
> warning Resolution field “lodash@4.17.21” is incompatible with requested version “lodash@4.17.15”

Just an info, but can that fall on my feets in the future ?

> remove regular file ‘cids/app\_bootstrap.cid

I have to answer this at the end with an interactive “y”  
Didn´t have to do that before.

I guess nothing of this is dramatic, but I just wanted to be sure.

Cheers,

Julian

---

<div class="post-metadata">

### Author: ![dan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dan/32/101549_2.png) [@dan](https://meta.discourse.org/u/dan)
#### Post date: [January 28, 2022, 8:44pm UTC](https://meta.discourse.org/t/launcher-behaves-strangely-with-the-new-update/216294/2 "2022-01-28T20:44:06Z")

</div>

What Linux distribution do you use?

The first problem can be caused by a git misconfiguration. Look at git’s `http.sslBackend`.

Is your `rm` aliased to `rm -i`? That is often the cause for the last annoyance.

> [@Wurzelseppi](#):
>
> I guess nothing of this is dramatic, but I just wanted to be sure.

None of these issues are fatal aside from the first issue which if I understand correctly, stops you from updating your Discourse instance. The other two are related to local configuration.

---

<div class="post-metadata">

### Author: ![Wurzelseppi](https://avatars.discourse-cdn.com/v4/letter/w/eada6e/32.png) [@Wurzelseppi](https://meta.discourse.org/u/Wurzelseppi)
#### Post date: [February 1, 2022, 6:58am UTC](https://meta.discourse.org/t/launcher-behaves-strangely-with-the-new-update/216294/3 "2022-02-01T06:58:20Z")

</div>

One of the most powerful features of discourse is the awesome support you get 🙂

Many thanks and have a great day!

Cheers!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [March 3, 2022, 6:58am UTC](https://meta.discourse.org/t/launcher-behaves-strangely-with-the-new-update/216294/4 "2022-03-03T06:58:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
