[00:07:50]
<rodinux> I think it did not install a new domain, but a new nginx conf in `/etc/nginx/conf.d/sandbox.cryptpad.domain.tld.conf`
[00:09:21]
<rodinux> Ok, so the message said « We have added a sandbox domain: sandbox.cryptpad.domain.tld for you but you still need to configure your DNS and regenerate the Let's Encrypt Certificates for the main domain.
You will need also to restart CryptPad service after this is done. »
[16:51:57]
<Lasse Gismo> Good evening.
[16:52:00]
<Lasse Gismo> Hi Aleks.
Are there already initial insights into my YNH11ToYNH12 restore problem?
What I did:
- prepared new image
- forgot to run a full-upgrade :-(
- created user and domain via web UI
- ran full restore - anded up with "nextcloud not part of the installead apps list" error
- ran "sudo apt update" and "sudo apt full-upgrade
- reboot
- ran apps restore - see image
- got all the last 7 app restore error logs
The list of logs starts with the very first:
https://paste.yunohost.org/raw/ijuzigiquq
https://paste.yunohost.org/raw/ututunobad
https://paste.yunohost.org/raw/ijetazufiw
https://paste.yunohost.org/raw/eyaqucikoj
https://paste.yunohost.org/raw/yadubuqata
https://paste.yunohost.org/raw/orutapuqag
https://paste.yunohost.org/raw/zezokanigu
https://paste.yunohost.org/raw/otupipafop
https://paste.yunohost.org/raw/vanemuwecu
https://paste.yunohost.org/raw/eloroqunej
https://paste.yunohost.org/raw/pazupuhevi
[20:55:22]
<miro5001> > <@botagiuks:tiesiog.lt> I have successfully packaged Jellystat for Yunohost. This is proof that even someone like me who is not a programmer at all, can still package an app to use for themselves, without being a programmer. You just gotta know your way around, know how to google, and how to and where to ask.
Did you add it to the catalog?
[20:57:04]
<Paprika> Not yet. Finished fixing the install/remove/upgrade/restore/etc. scripts today.
After that, tried to install it on a different instance I have, and it kept throwing me "Invalid token", so that needs to be fixed. Might have missed something. Really weird because on the first instance I can install it within seconds and it all works.
[20:57:44]
<Paprika> Not yet. Finished fixing the install/remove/upgrade/restore/etc. scripts today. In fact, I don't think I know how to proceed with adding it to the catalog, since I assume the README needs to be autogenerated, and I edited it by hand.
After that, tried to install it on a different instance I have, and it kept throwing me "Invalid token", so that needs to be fixed. Might have missed something. Really weird because on the first instance I can install it within seconds and it all works.
[20:58:29]
<Paprika> Not yet. Finished fixing the install/remove/upgrade/restore/etc. scripts today. In fact, I don't think I know how to proceed with adding it to the catalog, since I assume the README needs to be autogenerated, and I edited it by hand.
After that, tried to install it on a different instance I have, and it kept throwing me "Invalid token", so that needs to be fixed. Jellyfin logs mention "Invalid token" as well, so on the second instance the API token somehow might be getting lost for some reason.
Might have missed something. Really weird because on the first instance I can install it within seconds and it all works.
[21:00:50]
<miro5001> You can share the logs and your repo in the packaging room
[21:02:12]
<miro5001> It may have to do with selfsigned certificate. I see REJECT_SELF_SIGNED_CERTIFICATES in the env var
[21:06:37]
<miro5001> We have one latex editor in the catalog
[21:07:46]
<miro5001> I am testing fiduswriter which seems lightweight
[21:27:27]
<ben> Hi together, since upgrade from 11 to 12, moving to a new server and abandoning the former main domain I got a problem with SSO for normal users, they can only SSO on the new main domain, while admins can also use SSO on other subdomains.
I explained it more detailed here:
https://forum.yunohost.org/t/sso-portal-issue-after-bookworm-migration/34513/5?u=utzer
Any ideas or tips?
Is there any config or restriction for signing in on any of the portals?
[21:30:12]
<ben> > <@agbv:centonze.noho.st> Alright, thanks ! Just for the records it solved my latest issue in which you cannot put the SSO portal on a subdomain
Can you explain this a bit more in detail? Also see my other message just before.
[21:37:45]
<Paprika> Did so, thanks. I also managed to get it fixed as well after all. Wasn't that much of an issue in fact.