root@server:~# sudo dpkg --list | grep "yunohost\|moulinette"
hi moulinette 11.3.0 all prototype interfaces with ease in Python
hi yunohost 11.3.0.2 all manageable and configured self-hosting server
hi yunohost-admin 11.3.0 all web administration interface for yunohost
I did both sudo apt update && sudo apt upgrade as well as sudo apt full-upgrade. However, my admin user, genderneutralnoun, canāt sudo anymore; it tells me the user isnāt in the sudoers file. Luckily I already have root SSH local network access enabled for situations such as these. Additionally, apt list --upgradeable shows four packages in need of updating; moulinette, ssowat, yunohost-admin, and yunohost. Unfortunately apt upgrade results in them being kept back.
alrighty then letās try to upgrade them explicitly with install (yes install to tell it to upgrade ā¦ i know) : apt install moulinette yunohost yunohost-admin)
Iām guessing they are still marked as āholdā because thatās how the migration goes under the hood so you may need to first run : apt-mark unhold moulinette yunohost yunohost-admin
Well, I had a post typed out, but then my router decided to freak outā¦ Suffice to say, I needed to add ssowat to that list of packages in the apt install command. Everything installed great with that, but Iām still getting a 500 error on my serverās address. Progress, though! apt update shows all packages are up to date now. Any advice?
Rebooted. I didnāt think to do it immediately because thereās an issue where it wonāt actually reboot and so I have to unplug it and replug it physically, which is difficult since Iām disabled and a flight of stairs is between me and the serverās physical location. Anyway, rebooting worked. My admin user can even sudo again! Thanks so much guys.
Hello,
Just did succesfull migration on 1 of my servers. Extended thanks to the team .
I did not test yunohost 12 before the big official migration and Iāve found allready 1 (or maybe 2 different but very similar bugs):
When trying to update the system form the web admin, the green button does nothing. (there is allready a package to update despite the migration being 15min min old).
When tyring to save a change of configuration in an app, the save button does nothing (I tryied to chnage nextcloud from a path to a subdomain without effect)
As someone who switched to ātestingā for the 12.0 beta testing but would rather now go back to the stable channel, what would be the recommended procedure?
I have found the page https://install.yunohost.org/switchtoStable and it looks like thatās the recommended way to do it. Maybe something to add to the official procedure.
Itās not realted to the bug I was mentioning (buttons not working in web interface). Iāve upgrade through CLI libconfiginifile-perl. which log I cannot share via yunopaste cause the button is not working neither
Edit : Iām dumb, there was a blocked popup, hereās the upgrade lib log, but again not related to the initial issue IMHO
I migrated succesfully without errors.
But if I try to visit a subdomain āsub.foo.tldā, which is my standard domain I will be redirected to āfoo.tldā with the portal. But the portal should be on āsub.foo.tldā.
This happens only for three of my six sudomains. Any hint how to solve this?
Okay. But that would mean that I can not host a normal website anymore, because the portal will always show up?
So I canĀ“t move the portal to something like āportal.foo.tldā?
There is no āmoving the portalā, but if you want an application to open when you go to foo.tld, you can either install an application at that address, or use the āDefault appā setting in the domainās menu.
(@abc that thread was posted and answered before the release of YunoHost 12, so maybe its advice does not fit anymore )
I understand. But itĀ“s sad that I canĀ“t move the portal to the domain that IĀ“d like to. It was possible with yunohost 11 when I set a subdomain as main domain and the portal showed up on this domain. Maybe itĀ“s a future improvement for yunohost 12.
INFO - Could not complete the operation āDelete permission āxmppāā.
Error running script /usr/lib/python3/dist-packages/yunohost/migrations/0028_delete_legacy_xmpp_permission.py caused migration to fail.
Removed these lines from that script to force continue, which worked.
if āxmpp.mainā in user_permission_list()[āpermissionsā]:
permission_delete(āxmpp.mainā, force=True)