# Yunohost 11.1 spooky testing

**URL:** https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802
**Category:** Announcements
**Created:** [October 23, 2022, 6:43pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802 "2022-10-23T18:43:30Z")
**Posts on this page:** 20
**Page:** 5

<div class="post-metadata">

### Author: ![tituspijean](https://forum.yunohost.org/user_avatar/forum.yunohost.org/tituspijean/32/3584_2.png) [@tituspijean](https://forum.yunohost.org/u/tituspijean)
#### Post date: [November 26, 2022, 5:53pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/81 "2022-11-26T17:53:02Z")

</div>

If you expected it to make coffee and tuck you in at night, indeed you can be disappointed. Can you enlighten us on what you expected, what you did, and what happens?

---

<div class="post-metadata">

### Author: ![rodinux](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rodinux/32/7029_2.png) [@rodinux](https://forum.yunohost.org/u/rodinux)
#### Post date: [November 26, 2022, 5:59pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/82 "2022-11-26T17:59:25Z")

</div>

Hello,  
before the upgrade to 11.1\* I could hide the webadmin with this setting using:

```auto
sudo yunohost settings set security.webadmin.allowlist -v <IP_ADDRESS> 

yunohost settings set security.webadmin.allowlist.enabled -v True 

```

This commands permit access the webadmin only through the \<IP\_ADDRESS\> selected, other IP show an error 403

Since the upgrade, the webadmin is no more hidden with these settings…

---

<div class="post-metadata">

### Author: ![tituspijean](https://forum.yunohost.org/user_avatar/forum.yunohost.org/tituspijean/32/3584_2.png) [@tituspijean](https://forum.yunohost.org/u/tituspijean)
#### Post date: [November 26, 2022, 6:05pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/83 "2022-11-26T18:05:51Z")

</div>

Thanks. 🙂

By any chance, does it work on the webadmin? It might be related to my issue above.

---

<div class="post-metadata">

### Author: ![rodinux](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rodinux/32/7029_2.png) [@rodinux](https://forum.yunohost.org/u/rodinux)
#### Post date: [November 26, 2022, 8:33pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/84 "2022-11-26T20:33:16Z")

</div>

No, even from the webadmin…

---

<div class="post-metadata">

### Author: ![rodinux](https://forum.yunohost.org/user_avatar/forum.yunohost.org/rodinux/32/7029_2.png) [@rodinux](https://forum.yunohost.org/u/rodinux)
#### Post date: [November 26, 2022, 9:51pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/85 "2022-11-26T21:51:21Z")

</div>

did you try `yunohost settings set security.nginx_redirect_to_https -v 1` ?

or may be better `yunohost settings set nginx_redirect_to_https -v True` or `yunohost settings set security.nginx_redirect_to_https -v True` ??

In my server I can see `nginx_redirect_to_https: True`

Ok, I try but have same issue !!

---

<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: [November 26, 2022, 11:35pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/86 "2022-11-26T23:35:58Z")

</div>

> [@tituspijean](#):
>
> CLI management of the YunoHost settings is broken:  
> […]  
> Looks like the names have changed?

It’s not broken 😉 Just a weird stuff that `yunohost settings list` doesnt like the full setting key but `yunohost settings set` expects the full key …

I fixed the output format of `yunohost settings list` in [settings: fix output format for 'yunohost settings list' · YunoHost/yunohost@70bf38c · GitHub](https://github.com/YunoHost/yunohost/commit/70bf38ce25f0e6e10a52d03b6396f965ea50f665)

---

<div class="post-metadata">

### Author: ![jookk](https://forum.yunohost.org/user_avatar/forum.yunohost.org/jookk/32/6992_2.png) [@jookk](https://forum.yunohost.org/u/jookk)
#### Post date: [November 28, 2022, 5:20am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/87 "2022-11-28T05:20:09Z")

</div>

I used hook for securing web admin to only lan:

> [@Share your "hooks" to apply custom configurations- Partagez vos "hooks" pour appliquer des configurations personnelles](https://forum.yunohost.org/t/share-your-hooks-to-apply-custom-configurations-partagez-vos-hooks-pour-appliquer-des-configurations-personnelles/17235):
>
> gb English version Translate with DeePL A “hook” allows you to apply personal configurations to Yunohost files without the system detecting them as modified. Without a hook, Yunohost does not update these files and this is a real risk in terms of security and system stability. This is especially true with SSH by modifying sshd\_config. The solution without a hook is to run the following command after each update to see if there have been any changes: yunohost tools regen-conf -n -d If there…

---

<div class="post-metadata">

### Author: ![tituspijean](https://forum.yunohost.org/user_avatar/forum.yunohost.org/tituspijean/32/3584_2.png) [@tituspijean](https://forum.yunohost.org/u/tituspijean)
#### Post date: [November 29, 2022, 5:19am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/88 "2022-11-29T05:19:29Z")

</div>

“Ignore diagnosis check” switch for certificate generation works well! 👌

---

<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: [December 2, 2022, 11:46pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/89 "2022-12-02T23:46:10Z")

</div>

👉 YunoHost 11.1.1 has been released and fixes a bunch of issues

**In particular, we recommend people that were on 11.1.0 to run the following to fix the issue with admins aliases:**

```bash
sudo su # To become root if not root already
MAINDOMAIN=$(yunohost domain list --output-as json | jq -r '.main')
yunohost user group add-mailalias admins root@$MAINDOMAIN admin@$MAINDOMAIN admins@$MAINDOMAIN webmaster@$MAINDOMAIN abuse@$MAINDOMAIN postmaster@$MAINDOMAIN
yunohost user group remove-mailalias admins root admin admins abuse webmaster postmaster

```

**NB** : if you ended up on 11.1.0 while still being on stable (11.1.0 was incorectly released as stable during a few hours), you first need to enable testing to get the upgrade to 11.1.1: `curl https://install.yunohost.org/switchtoTesting | bash`

## 📜 Changelog

- **groups: add mail-aliases management** ([#1539](https://github.com/YunoHost/yunohost/pull/1539)) (0f9d9388)
  - Groups can now be used as a minimalist mailing list : you can add group aliases with `yunohost user group add-mailalias <groupname> <whatever@domain.tld>` and mails sent to `whatever@domain.tld` will be dispatched to all members of the group

- apps: Allow apps to be installed on a path sharing a common base, eg /foo and /foo2 ([#1537](https://github.com/YunoHost/yunohost/pull/1537)) (ae594111)
- admins/ldap: re-allow members of the admins group to edit ldap db (4f5cc166)
- nginx: Add 502 custom error page ([#1530](https://github.com/YunoHost/yunohost/pull/1530)) (5063e128)
- misc/nodejs: Upgrade n to version 9.0.1 ([#1528](https://github.com/yunohost/yunohost/pull/1528))
- misc/update: add --allow-releaseinfo-change option to apt update to prevent the classic nightmare when debian changes from stable to oldstable (ac6d6871)
- misc/dns: Add Webgo as Registrar to support it via Lexicon ([#1529](https://github.com/YunoHost/yunohost/pull/1529)) (c50f3771)
- misc/debug: Improve dpkg\_is\_broken instruction to also mention dpkg --audit (a772153b)
- misc/regeconf: fix yunohost hook incorectly tweaking mdns.yml ownership (9bd98162)
- misc/helpers: fix docker-image-extract helper ([#1532](https://github.com/YunoHost/yunohost/pull/1532))
- misc/yunoprompt: don’t display postinstall tip to members of all\_users group (4aaa8896)
- misc/diagnosis: make the dnsrecord diagnoser not complain about the damn 128 vs 0 stuff in CAA records (70a8225b)
- misc/settings: fix output format for ‘yunohost settings list’ (70bf38ce)
- misc/helpers: Better error message when psql is not there for database\_exists ([#992](https://github.com/YunoHost/yunohost/pull/992)) (f49c121b)
- misc/multimedia: fix edgecase where setfacl crashes because of broken symlinks (94f21ea2)
- misc/legacy: auto-patch ‘yunohost user create’ syntax in app scripts to use --fullname instead (d254fb1b)
- misc/webadmin: fix checkbox svg icon colors ([webadmin#489](https://github.com/yunohost/yunohost-admin/pull/489))
- **i18n: Translations updated for Arabic, Basque, Chinese (Simplified), Dutch, French, Galician, German, Spanish, Ukrainian, Italian, Kabyle, Polish**

---

<div class="post-metadata">

### Author: ![jookk](https://forum.yunohost.org/user_avatar/forum.yunohost.org/jookk/32/6992_2.png) [@jookk](https://forum.yunohost.org/u/jookk)
#### Post date: [December 3, 2022, 8:07am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/90 "2022-12-03T08:07:56Z")

</div>

Wau, thans. I really looking forward to it.  
But there at stable is not update available

---

<div class="post-metadata">

### Author: ![Kit](https://forum.yunohost.org/user_avatar/forum.yunohost.org/kit/32/1208_2.png) [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 9:04am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/91 "2022-12-03T09:04:29Z")

</div>

Hello,

I am on a 11.1.0.2 version.

Is there a typo mistake ?

```auto
# # yunohost user group remove-mailalias admins root admin admins abuse webmaster postmaster
usage: yunohost user group {list,create,delete,info,add,remove} ... [-h]
yunohost user group: error: argument {list,create,delete,info,add,remove}: invalid choice: 'remove-mailalias' (choose from 'list', 'create', 'delete', 'info', 'add', 'remove')

```

---

<div class="post-metadata">

### Author: ![Memo](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/m/a5b964/32.png) [@Memo](https://forum.yunohost.org/u/Memo)
#### Post date: [December 3, 2022, 9:19am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/92 "2022-12-03T09:19:23Z")

</div>

Same here 🤔

---

<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: [December 3, 2022, 11:27am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/93 "2022-12-03T11:27:37Z")

</div>

Well yes you have to be on 11.1.1 first to run that command …

---

<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: [December 3, 2022, 11:28am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/94 "2022-12-03T11:28:14Z")

</div>

> [@jookk](#):
>
> But there at stable is not update available

Yes that’s still a testing release, you have to be on testing to receive the upgrade …

---

<div class="post-metadata">

### Author: ![ericg](https://forum.yunohost.org/user_avatar/forum.yunohost.org/ericg/32/1543_2.png) [@ericg](https://forum.yunohost.org/u/ericg)
#### Post date: [December 3, 2022, 11:30am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/95 "2022-12-03T11:30:01Z")

</div>

Being on testing, no problem to update 😇

---

<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: [December 3, 2022, 11:43am UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/96 "2022-12-03T11:43:12Z")

</div>

(I guess the confusion comes from the fact that some folks ended up on 11.1 as stable and never enabled testing 😕 In which case you should run : `curl https://install.yunohost.org/switchtoTesting | bash`)

---

<div class="post-metadata">

### Author: ![Kit](https://forum.yunohost.org/user_avatar/forum.yunohost.org/kit/32/1208_2.png) [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 1:18pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/97 "2022-12-03T13:18:14Z")

</div>

> [@Aleks](#):
>
> `yunohost user group remove-mailalias admins root admin admins abuse webmaster postmaster`

Alright, updated to 11.1.1 with the curl command provided above.

```auto
# yunohost tools versions
yunohost:
  repo: testing
  version: 11.1.1
yunohost-admin:
  repo: testing
  version: 11.1.1
moulinette:
  repo: testing
  version: 11.1.0
ssowat:
  repo: testing
  version: 11.1.0

```

Still have issue processing the removing of the groups : [https://paste.yunohost.org/raw/iperewiruc](https://paste.yunohost.org/raw/iperewiruc)

```auto
# yunohost user group list
groups:
  admins:
    members:
      - admin
      - user1
  all_users:
    members: user1
  visitors:
    members:

```

Well, the group `admins` exists.

Group infos :

```auto
# yunohost user group info admins
mail-aliases:
  - root
  - admin
  - admins
  - webmaster
  - postmaster
  - abuse
members:
  - admin
  - user1
permissions:

```

---

<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: [December 3, 2022, 1:33pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/98 "2022-12-03T13:33:54Z")

</div>

Hmokay, can you try the other way around:

```auto
yunohost user group add-mailalias admins root@$MAINDOMAIN admin@$MAINDOMAIN admins@$MAINDOMAIN webmaster@$MAINDOMAIN abuse@$MAINDOMAIN postmaster@$MAINDOMAIN
yunohost user group remove-mailalias admins root admin admins abuse webmaster postmaster

```

---

<div class="post-metadata">

### Author: ![Kit](https://forum.yunohost.org/user_avatar/forum.yunohost.org/kit/32/1208_2.png) [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 2:04pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/99 "2022-12-03T14:04:18Z")

</div>

Weird, but worked :

```auto
# yunohost user group remove-mailalias admins root admin admins abuse webmaster postmaster
Info: Updating aliases for group 'admins'
Success! Group 'admins' updated
mail-aliases:
  - webmaster@mydomain.tld
  - abuse@mydomain.tld
  - admins@mydomain.tld
  - admin@mydomain.tld
  - postmaster@mydomain.tld
  - root@mydomain.tld
members:
  - admin
  - user1
permissions:

```

Thanks 🙂

---

<div class="post-metadata">

### Author: ![Kit](https://forum.yunohost.org/user_avatar/forum.yunohost.org/kit/32/1208_2.png) [@Kit](https://forum.yunohost.org/u/Kit)
#### Post date: [December 3, 2022, 7:15pm UTC](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802/100 "2022-12-03T19:15:28Z")

</div>

@Aleks : Updated to 11.1.1.2

I still receive those **Undelivered Mail Returned to Sender** mails. Shouldn’t the `mail-aliases` fix it ?

Here is a sample of a mail sent from root to root :

> This is the mail system at host mydomain.tld.
> 
> I’m sorry to have to inform you that your message could not be delivered to one or more recipients. It’s attached below.
> 
> For further assistance, please send mail to postmaster.
> 
> If you do so, please include this problem report. You can delete your own text from the attached returned message.
> 
> The mail system [admin@mydomain.tld](mailto:admin@mydomain.tld) (expanded from [root@mydomain.tld](mailto:root@mydomain.tld)): user unknown
> 
> Reporting-MTA: dns; mydomain.tld  
> X-Postfix-Queue-ID: 1D82933E23F4  
> X-Postfix-Sender: rfc822; root@mydomain.tld  
> Arrival-Date: Sat, 3 Dec 2022 20:05:39 +0100 (CET)
> 
> * * *
> 
> Final-Recipient: rfc822; admin@mydomain.tld  
> Original-Recipient: rfc822;root@mydomain.tld  
> Action: failed  
> Status: 5.1.1  
> Diagnostic-Code: x-unix; user unknown
> 
> * * *
> 
> [original mail]

[Previous page](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802.md?page=4)

[Next page](https://forum.yunohost.org/t/yunohost-11-1-spooky-testing/21802.md?page=6)
