đŸ‘Ÿ YunoHost 12.1 testing

Hello everyone :blossom: :herb: !

We just released a new testing version for YunoHost! :tada: This version includes some important changes, and we would be more than happy to receive feedback before releasing it as a stable version!

  • :scroll: A new mechanism (so-called ‘SSE’) to retrieve the status and stream logs of the current action ongoing on the server, whether it got started from another webadmin, the command line or a cron (automatic task). In particular, this should improve situations where some actions are taking a long time, or you closed your browser tab for some reason, or another admin started an operation, or there’s a long automatic backup ongoing : previously it was pretty confusing and hard to know why the webadmin was kind of locked, but now it should automatically catch up and display what’s going on! :wink:

  • :art: The app list and app info pages of the webadmin were improved to include the app’s logo. The app’s logo are also now customizable, along with the label and description used in the portal. Accesses can now be edited directly from the app’s info page, as well as upgrading the app.

  • :zap: Tweaks to improve the performance of LDAP operations, which should be pretty significant for instances handling more than ~100ish users. (Typically user creation could start to become extremely long)

  • :building_construction: A full rework of our firewall code which was pretty outdated and confusing. The new code is based on nftables which is the modern way of managing network rules.

  • :cookie: Switching to ‘Lax’ for the SameSite parameter of portal cookies 
 this is pretty technical but this should fix a few issues with authentication not working properly or situations where the portal doesn’t understand you’re already logged in.

  • :floppy_disk: Some first bits for a new section for storage management. For now it only lists disk and their info, and is only available in CLI, but more to come on this later!

How to participate to the beta-testing :construction_worker_woman: :construction_worker_man:

:warning: DO NOT do this on a critical production server! :warning:

From the command line, you can launch the following command to switch to testing:

curl https://install.yunohost.org/switchtoTesting | bash

(If you are familiar with bash scripting, you might want to read what this script does before blindly running the command)

You should then be running YunoHost 12.1.x.

What to test? :space_invader: :telescope:

  • Upgrade and report any oddness found in your regular usage of YunoHost
  • The new status/log mechanism is still not entirely dry and probably has a few rough corners. It helps if you can trigger ~long operations such as installing apps, upgrading them, creating backups, etc 
 especially if you can try those by triggering them from the command line with a webadmin on the side, or with two webadmin tabs side-by-side and checking if everything is consistent.
  • Trying and reviewing the new interface in the app info page related to tile customization and permission as well as operations (upgrade, change url, 
)
  • If you are using the VPNclient and/or Hotspot app, we’re interested to know if they are still running fine even after rebooting
  • Validating that the new cookie policy does fix situations where the portal doesn’t understand you’re already logged in .. though those scenarios are pretty hard to describe in just a few lines, but hopefully the people who experienced the issue will know what to do :sweat_smile:
19 Likes

I got this error :

DĂ©paquetage de dnsmasq (2.90-4~deb12u1) sur (2.89-1) ...
Paramétrage de dnsmasq (2.90-4~deb12u1) ...

Fichier de configuration « /etc/default/dnsmasq »
==> Modifié (par vous ou par un script) depuis l'instal
lation.
==> Le distributeur du paquet a fourni une version mise
Ă  jour.
Que voulez-vous faire ? Vos options sont les suivante
s :
Y ou I  : installer la version du responsable du paq
uet
N ou O  : garder votre version actuellement installé
e
D  : afficher les différences entre les version
s
Z  : suspendre ce processus pour examiner la si
tuation
L'action par défaut garde votre version actuelle.
*** dnsmasq (Y/I/N/O/D/Z) [défaut=N] ? dpkg: erreur de t
raitement du paquet dnsmasq (--configure) :
fin de fichier sur l'entrée standard à l'invite de conf
iguration
Des erreurs ont été rencontrées pendant l'exécution :
dnsmasq
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@local:~#

On a virtualbox vm (used in testing packages). It isn’t accessible from outside the lan.
(sorry for the extra new lines, it’s from connectbot on android).

Edit :
I ran sudo apt install --fix-broken and responded with the default options then rerun the script. It took about 10 minutes.

What I’ve noticed so far :

  • in app info page, the change url shouldn’t be shown for apps that require a dedicated domain.
  • the new log behavior is great, especially on mobile when switching between apps, you sometimes get the page refreshed. This prevents other operations on other tabs or browsers.
  • I tried updating joomla while having two tabs on mobile (opera). The progress pop-up was stuck on “Backup script completed for joomla. (YunoHost will then actually copy those files to the archive).” I waited then refreshed one of the tabs, checked the logs to find that the update was finished successfully. I switched to the other tab, it was stuck on the same state. Note that cache was enabled in Web-admin settings.
  • the new app page is great, may be changing the “YunoHost integration” with badges.

That’s great

1 Like

That doesn’t sound related to YunoHost, it’s about dnsmasq and I don’t know what command you ran exactly, it sounds like it was in non-interactive mode

I ran

curl https://install.yunohost.org/switchtoTesting | bash

As indicated above. I should have run it on pc so I could report the whole output. Probably it is related to the fact that I am using it for testing packages and something may have broken dnsmasq.

Meh idk it just sounds like it upgraded dnsmasq as well because it wasnt up to date on your system and then it needed to ask interactively what version of the conf to ask, but since that wasnt interactive it failed

tl;dr just run a regular upgrade before switching to testing

1 Like

You’re right, it’s been a while since I updated it, it was off. I checked the logs, the last actions were 2 months ago.

I tried updating lychee from the app page. The pop-up gets also stuck until I refresh the page.
Here, it sometimes loses connection, thought the server is in lan :

Here, I waited a long time, while it didn’t progress, so I refreshed the page :

Then tried updating from “system update”. The pre-update backup text log gets cleared and the process continues correctly :

1 Like

in the webadmin → applications, All app addresses have a double //at the end.

over all, It’s nice to have these customisation options, but I find the app page confusing in its organisation


  • The app uninstaller red button should be on top imo (as it was before)
  • The field nouveau domain and nouveau chemin should be pre-populated with the current settings.
  • The buttons could be better aligned with the fields

Aligning the plus button could be a plus (and using add permission instead of an icon)

Little glitch on the port panel

We could have the app logo in here


1 Like

Congrats for this huge update!
Little (cosmetic?) issue: whenever I enable/disable UPNP in the firewall, this errror is shown:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/moulinette/interfaces/api.py", line 430, in process
    ret = self.actionsmap.process(arguments, timeout=30, route=_route)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 579, in process
    return func(**arguments)
           ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/yunohost/firewall.py", line 512, in firewall_upnp
    if upnp.refresh(firewall):
       ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/yunohost/firewall.py", line 276, in refresh
    status = status and self.open_port(protocol, port, info["comment"])
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/yunohost/firewall.py", line 228, in open_port
    assert self.upnpc is not None
           ^^^^^^^^^^^^^^^^^^^^^^
AssertionError

After refreshing the page the upnp is effectively enabled/disabled (I’ve not yet tried if it works effectively)

1 Like

Hi all! Even though I was on the stable branch, the update appeared anyways and I now find myself on testing. All my apps are unreachable! (see for example https://tommi.space/).

I don’t know what to do! Can you help me fix this? Otherwise, how can I downgrade back to stable?

Can you try sudo yunohost app ssowatconf ?

2 Likes

Thanks for the prompt reply, @Aleks!

sudo yunohost app ssowatconf returns nothing.

Yes it’s expected to return nothing but did it improve the situation ?

Ooooh, OK! Problem solved. Thank you so much, @Aleks! I was about to panic.

Is it possible to tell YunoHost to get back to the stable branch? (I am puzzled on why it automatically switched to testing in the first place :thinking:)

Yeah maybe that’s because you enabled testing for the 11.0 when it was in beta or something 
 (The diagnosis also warns that you are on testing supposedly, but it’s also easy to miss it)

Anyway you can try running curl https://install.yunohost.org/switchtoStable | bash and confirming that cat /etc/apt/sources.list.d/yunohost.list only shows “stable” at the end and no mention of “testing”

1 Like

Ah, I see! This is the first testing since 11→12. I silenced the testing warning in the diagnosis and forgot about it.

If I run curl https://install.yunohost.org/switchtoStable | bash, am I rolling back to the latest stable, or am I telling YunoHost to update to the newest stable as soon as a new update is available?

Ah yeah there’s no rolling back, indeed it just tells YunoHost to only fetch update from the stable channel 
 which uuuuh now that you’re on 12.1, means you won’t get the fixes from the iterations we’ll do on the testing during the coming weeks :sweat_smile:

Except one minor problem fixed by this, my update went smoothly. Logs are here, FYI. Thanks to all the YunoHost team :two_hearts:

2 Likes

Got it, no problem. I will switch to stable once 12.1 gets out of testing.

Thanks again, have a great weekend!

1 Like