Same here. Even though the server is online, I get a disconnection error.
I ran the upgrade on a test system, with the same symptom.
Is that to be expected to happen, and if so, is there any adverse effect when running the command by default after the upgrade?
Besides that, the upgrade on this admittedly quite empty server ran flawless.

Is that to be expected to happen, and if so, is there any adverse effect when running the command by default after the upgrade?
Itās just a bug that we need to address, we just need to run that command automatically somehow (though not just why itās needed in the first place, will dig in later)
12.1.1 was released which includes a fix for the lack of automatic app_ssowatconf (so it shouldnt be required anymore to run it manually) and adjustments for upnp stuff
I tried to install vpnclient and i have:
# yunohost app install vpnclient
==========
Please note that this application only interfaces with **dedicated, public IP VPNs accepting inbound traffic**,
preferably with an associated `.cube` (or `.ovpn/.conf`) configuration file.
**Do not** expect that any VPN you randomly bought on the Internet can be used!
Checkout the [list of known compatible providers](https://yunohost.org/providers/vpn) for more info.
After installation, you will be able to configure the application from YunoHost's webadmin in Applications > VPNclient > Configuration
==========
WARNING: You should check the app notifications above before continuing, there might be important stuff to know. [Pres
s enter to continue]:
Traceback (most recent call last):
File "/usr/bin/yunohost", line 108, in <module>
main()
File "/usr/bin/yunohost", line 97, in main
yunohost.cli(
File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 41, in cli
ret = moulinette.cli(
^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/__init__.py", line 140, in cli
).run(args, output_as=output_as, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/interfaces/cli.py", line 521, in run
ret = self.actionsmap.process(args, timeout=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 579, in process
return func(**arguments)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/log.py", line 536, in func_wrapper
result = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 1202, in app_install
_validate_webpath_requirement(parsedargs, path_requirement)
File "/usr/lib/python3/dist-packages/yunohost/app.py", line 3319, in _validate_webpath_requirement
raise Exception
Exception
I also have this
(Previous bug should be fixed in 12.1.2)
Always on mobile (I didnāt make tests on desktop), when I launch an update then open another tab, on the first tab the update progress get stuck at the backup step and the second tab doesnāt show the progress like in the previous version of testing. I checked the in the second tab the logs and the update was finished but the pop-up was still held in backup in the first tab
In the app view :
We used to have āopen appā and āuninstallā under the app name.
Now the āuninstallā is at the bottom in the āOperationsā section.
I know this is the right thing but it was more convenient when it was up.
Another thing : there is a save button at the end of the Operations section. Donāt know what is it for.
Also, the app description can be in a spoiler, since we already know what we have installed
I have a serious problem since the last update.
- All my user permissions were gone.
- After re-assigning the permissions only some of the apps appear on the portal, most not.
- When providing the full URL
https://my.domain/myapp
of a not displayed app the browser opens the portal URLhttps://my.domain/yunohost/sso/
instead. - On the web-admin the apps which appear on the portal and those which do donāt have different configurations dialogues. See below.
sudo yunohost app ssowatconf
didnāt help.
Non-Working Configurations dialogue (without link):
Working Configurations dialogue (with link)
Versions
yunohost:
repo: testing
version: 12.1.2
yunohost-admin:
repo: testing
version: 12.1.1
yunohost-portal:
repo: stable
version: 12.0.8
moulinette:
repo: testing
version: 12.1.0
ssowat:
repo: stable
version: 12.0.3
Is this a production server?
āPrivate Production Serverā, but on ātestingā since many month.
Maybe this helps to tackle: nftables service is configured (somehow) so that it isntāt started on system boot. Starting the service later doesnāt help with the problem.
Forcing the upgrade of the missing apps, seems to solve the issue.
Migration 33 fails with error. It seems it is resulting from the entry of the app āTerraforming Marsā. Log: https://paste.yunohost.org/raw/segupezowi
Hmokay but it sounds like this is an attempt to re-run a failed migration ā¦ do you have the very first attempt at running migration 33, which should be automatically triggered at the time you upgraded to 12.1 ?
Are the the yunohost log share 2025...
outputs are in some logs. Otherwise unfortunately not. But the error was the same as far as I see it.
Yes possibly you can find it from the CLI using ls /var/log/yunohost/operations/2025*migrations*.log
Or from the webadmin in Tools > Logs, it should be part of the āsuboperationsā of the upgrade to 12.1

ls /var/log/yunohost/operations/2025migrations.log
I have found the log from the first try: hastebin
Cheers ! Hmkay so thatās the same error ā¦ weāll need to keep an eye on this, iām not sure why it would say that the label attribute doesnāt exist ā¦ and why it works for other people
Anyway, thatās definitely why all your user permissions were gone and why you had to re-set them manually ā¦ Considering you already did all of this, I would say you can safely skip the migration