# The problem is updated in yunohost?

**URL:** https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291
**Category:** Support
**Tags:** french
**Created:** [August 8, 2017, 3:33pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291 "2017-08-08T15:33:54Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![rodriguem7800](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rodriguem7800/32/722_2.png) [@rodriguem7800](https://forum.yunohost.org/u/rodriguem7800)
#### Post date: [August 8, 2017, 3:33pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/1 "2017-08-08T15:33:54Z")

</div>

hello  
i am updated for this problem in debian 8.9 server with yunohost

[quote]  
W: Erreur de GPG : [http://repo.yunohost.org](http://repo.yunohost.org) jessie InRelease : Les signatures suivantes n’ont pas pu être vérifiées car la clé publique n’est pas disponible : NO\_PUBKEY 360AAF3259A3E6FF

[quote]

you are ideale ?  
thank you

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [August 8, 2017, 4:08pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/2 "2017-08-08T16:08:33Z")

</div>

Hi there,

it’s a ~known issue that some people encounter on their server … We’re not sure exactly why at the moment (because everything looks alright when we try to investigate it, so it’s not clear what’s wrong…)

If you trust your machine, your network and the Yunohost team though, you can bypass the issue by running `apt-get update --allow-unauthenticated` … Sorry not to be able to propose a better fix 😕

---

<div class="post-metadata">

### Author: ![rodriguem7800](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rodriguem7800/32/722_2.png) [@rodriguem7800](https://forum.yunohost.org/u/rodriguem7800)
#### Post date: [August 8, 2017, 4:24pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/3 "2017-08-08T16:24:34Z")

</div>

hi captainsqrt2 : i says but refused access

---

<div class="post-metadata">

### Author: ![rodriguem7800](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rodriguem7800/32/722_2.png) [@rodriguem7800](https://forum.yunohost.org/u/rodriguem7800)
#### Post date: [August 9, 2017, 3:46pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/4 "2017-08-09T15:46:42Z")

</div>

up up up!

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [August 9, 2017, 3:50pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/5 "2017-08-09T15:50:16Z")

</div>

Can you please show the command you typed exactly, and the full log you get ?

---

<div class="post-metadata">

### Author: ![ppr](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/p/8c91f0/32.png) [@ppr](https://forum.yunohost.org/u/ppr)
#### Post date: [August 9, 2017, 8:14pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/6 "2017-08-09T20:14:39Z")

</div>

Good evening @rodriguem7800 @CaptainSqrt2 ,

@rodriguem7800, if your YunoHost instance is installed on a Raspberry Pi, have a look here … the topic is in french, but it could helps you …

> [@W: Erreur de GPG : http://httpredir.debian.org jessie-backports](https://forum.yunohost.org/t/w-erreur-de-gpg-http-httpredir-debian-org-jessie-backports/1779):
>
> Bonjour, J’ai cette erreur depuis plusieurs jours lors de l’update && upgrade : W: Erreur de GPG : [http://httpredir.debian.org](http://httpredir.debian.org) jessie-backports InRelease : Les signatures suivantes n’ont pas pu être vérifiées car la clé publique n’est pas disponible : NO\_PUBKEY 8B48AD6246925553 NO\_PUBKEY 7638D0442B90D010 W: Duplicate sources.list entry [http://httpredir.debian.org/debian/](http://httpredir.debian.org/debian/) jessie-backports/main armhf Packages (/var/lib/apt/lists/httpredir.debian.org\_debian\_dists\_jessie-backports\_main\_binary-ar…

> [@W: Erreur de GPG : http://httpredir.debian.org jessie-backports](https://forum.yunohost.org/t/w-erreur-de-gpg-http-httpredir-debian-org-jessie-backports/1779/2):
>
> Je vois la mention “Backport”. Tu as modifié le fichier sources.list à la main non? La ligne semble dupliquer vu le 2ème message.
> 
> Pour le 1er, je cite [http://www.commentcamarche.net/faq/4445-debian-apt-get-no-pubkey-gpg-error](http://www.commentcamarche.net/faq/4445-debian-apt-get-no-pubkey-gpg-error)
> 
> Il s’agit d’une nouvelle fonctionnalité du système d’apt-get permettant  
> de garantir l’authenticité des serveurs de mise à jour Debian.  
> Pour y remédier, il suffit de saisir les deux commandes suivantes,  
> en prenant soin de remplacer le numéro de la clé par celui affiché dans  
> le message d’erreur :  
> gpg --keyserver pgpkeys.mit.edu --recv-key 010908312D230C5F  
> gpg -a --export 010908312D230C5F | sudo apt-key add -
> 
> Donc dans ton cas il faudrait faire
> 
> gpg --keyserver pgpkeys.mit.edu --recv-key 8B48AD6246925553  
> gpg -a --export 8B48AD6246925553 | sudo apt-key add -  
> gpg --keyserver pgpkeys.mit.edu --recv-key 7638D0442B90D010  
> gpg -a --export 7638D0442B90D010| sudo apt-key add -

[http://www.commentcamarche.net/faq/4445-debian-apt-get-no-pubkey-gpg-error](http://www.commentcamarche.net/faq/4445-debian-apt-get-no-pubkey-gpg-error)

ppr

---

<div class="post-metadata">

### Author: ![Aleks](https://forum.yunohost.org/user_avatar/forum.yunohost.org/aleks/32/1704_2.png) [@Aleks](https://forum.yunohost.org/u/Aleks)
#### Post date: [January 18, 2023, 8:14pm UTC](https://forum.yunohost.org/t/the-problem-is-updated-in-yunohost/3291/7 "2023-01-18T20:14:39Z")

</div>


