Wednesday, July 12, 2023
support@conference.yunohost.org
July
Mon Tue Wed Thu Fri Sat Sun
          1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
           

[00:26:26] <Aaron Bailey> Hi all — new here. I’ve successfully got Yunohost installed on a server and have installed a few apps and they’re working great. However I have two issues I feel like are beginner questions:

1. How can I access where the apps are installed via command line? I’m able to ssh to my server (using admin) but I’m not finding where the apps are installed. (For example, I want to move some files over to my Ghost install.)
2. I’ve installed the Matrix app. How do I configure Matrix and create users? (I've also installed Element and that's working great but I don't see how to configure my own Synapse server.)

Thank you in advance!
[00:33:50] <Aleks (he/him/il/lui)> the apps are installed in /var/www/$appname usually, though the exact answer may vary depending on what exactly you're trying to access, e.g. some apps "large" data (aka filestore) are sometimes in /home/yunohost.app/$appname
[00:34:40] <Aleks (he/him/il/lui)> not sure what you mean by the matrix app ... If you mean you installed Synapse, then my guess is that Synapse users are the YunoHost users, so creating a matrix user means adding a yunohost account
[00:35:20] <Aleks (he/him/il/lui)> if you mean more general admin stuff regarding synapse, i think there's a synapse-admin app which contains some sort of admin UI but I don't know much about it
[00:40:16] <Aaron Bailey> > <@Alekswag:matrix.org> the apps are installed in /var/www/$appname usually, though the exact answer may vary depending on what exactly you're trying to access, e.g. some apps "large" data (aka filestore) are sometimes in /home/yunohost.app/$appname

many thanks... this is helpful. Yes, I did mean the Synapse app (not Matrix). I'll check if there's a synapse-admin app. Thanks!
[00:41:09] <Aleks (he/him/il/lui)> some "technical" or "non-webapp", like maybe synapse, may be installed in /opt/ though
[00:41:27] <Aleks (he/him/il/lui)> hopefully oneday™ we'll move all this to a consistent `/apps/`
[02:19:48] <erinaceus> Does someone else get a cURL error ("error 60: SSL certificate problem: unable to get local issuer certificate") when trying to update or install Nextcloud apps? Similar issues come up in several Yunohost and Nextcloud forum threads, but with no apparent solution... 🤔
[02:21:26] <Aleks (he/him/il/lui)> no logs, can't help
[02:28:43] <erinaceus> > no logs, can't help
This is what the log record after trying to update the tasks app, but the same thing happens with any other existing Nextcloud app or when trying to install a new one:

Error: GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: unable to get local issuer certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://github.com/nextcloud/tasks/releases/download/v0.15.0/tasks.tar.gz at <<closure>>

0. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 158
GuzzleHttp\Handler\CurlFactory::createRejection("*** sensitive parameters replaced ***")
1. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php line 110
GuzzleHttp\Handler\CurlFactory::finishError()
2. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Handler/CurlHandler.php line 47
GuzzleHttp\Handler\CurlFactory::finish()
3. /var/www/nextcloud/lib/private/Http/Client/DnsPinMiddleware.php line 150
GuzzleHttp\Handler\CurlHandler->__invoke()
4. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php line 35
OC\Http\Client\DnsPinMiddleware->OC\Http\Client\{closure}("*** sensitive parameters replaced ***")
5. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 31
GuzzleHttp\PrepareBodyMiddleware->__invoke()
6. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/RedirectMiddleware.php line 71
GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***")
7. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Middleware.php line 63
GuzzleHttp\RedirectMiddleware->__invoke()
8. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php line 75
GuzzleHttp\Middleware::GuzzleHttp\{closure}("*** sensitive parameters replaced ***")
9. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php line 331
GuzzleHttp\HandlerStack->__invoke()
10. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php line 168
GuzzleHttp\Client->transfer()
11. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php line 187
GuzzleHttp\Client->requestAsync("*** sensitive parameters replaced ***")
12. /var/www/nextcloud/lib/private/Http/Client/Client.php line 226
GuzzleHttp\Client->request()
13. /var/www/nextcloud/lib/private/Installer.php line 295
OC\Http\Client\Client->get()
14. /var/www/nextcloud/lib/private/Installer.php line 193
OC\Installer->downloadApp()
15. /var/www/nextcloud/core/Command/App/Update.php line 107
OC\Installer->updateAppstoreApp("*** sensitive parameters replaced ***")
16. /var/www/nextcloud/3rdparty/symfony/console/Command/Command.php line 255
OC\Core\Command\App\Update->execute()
17. /var/www/nextcloud/3rdparty/symfony/console/Application.php line 1009
Symfony\Component\Console\Command\Command->run()
18. /var/www/nextcloud/3rdparty/symfony/console/Application.php line 273
Symfony\Component\Console\Application->doRunCommand()
19. /var/www/nextcloud/3rdparty/symfony/console/Application.php line 149
Symfony\Component\Console\Application->doRun()
20. /var/www/nextcloud/lib/private/Console/Application.php line 211
Symfony\Component\Console\Application->run()
21. /var/www/nextcloud/console.php line 100
OC\Console\Application->run()
22. /var/www/nextcloud/occ line 11
require_once("/var/www/nextcloud/console.php")
[02:35:52] <Aleks (he/him/il/lui)> and where is this log snippet even coming from ...
[02:36:54] <Aleks (he/him/il/lui)> also what kind of hardware are you running ...
[02:37:05] <Aleks (he/him/il/lui)> did you happen to do anything special before this started happening ...
[02:38:07] <erinaceus> > and where is this log snippet even coming from ...
settings/admin/logging on the Nextcloud admin panel. I get the same error whenever I try to update/install a Nextcloud app.
[02:42:24] <erinaceus> > also what kind of hardware are you running ...
Liva minicomputer with an Intel processor (Pentium Silver N5030 CPU @ 1.10GHz)
[02:44:31] <erinaceus> > did you happen to do anything special before this started happening ...
Not really. I believe it started around the time I upgraded to the current Yunohost release (I used to be able to update and install Nextcloud apps earlier), but I didn't notice right away, only when I tried to install a new Nextcloud app a few months ago.
[02:45:48] <erinaceus> Otherwise Nextcloud runs just fine, apart from a problem with modification dates when syncing with the desktop client, which seems to be a common issue.
[02:45:53] <Aleks (he/him/il/lui)> theeen let's check that `dpkg --list | grep ca-cert` does return version `20210119`
[02:46:58] <erinaceus> Yep
[02:47:07] <erinaceus> 20210119
[02:48:03] <Aleks (he/him/il/lui)> @_@
[02:48:35] <Aleks (he/him/il/lui)> what if you run `curl https://ip.yunohost.org`, do you see your IP displayed (no need to share the IP, just trying to cross check the curl behavior)
[02:49:33] <erinaceus> Yes, I see my own IP
[02:50:30] <Aleks (he/him/il/lui)> hmmm and could it be that maybe you are running your yunohost instance with a self-signed certificate instead of a Lets encrypt cert
[02:54:45] <erinaceus> According to the yunohost admin panel both the domain where I run yunohost and the subdomain where Nextcloud is installed have valid Let's encrypt certs... 🤔️
[02:58:01] <Aleks (he/him/il/lui)> hmkay 🤔
[02:59:44] <erinaceus> Weird, right? At this point I'm wondering whether I should just reinstall Nextcloud, but I don't know if it's worth the trouble. At least it works, but it would be nice to be able to install new apps again.
[08:08:34] <pepecyb> Hello, I am relatively new to YunoHost (since 30.05.2023). It runs on a vServer.

Currently I only have two services running: Hubzilla and Mastodon.

Until 30.06. I had installed Hubzilla " by foot" (from the Git repo). As usual, I updated Hubzilla via SSH with /uels/udall.

Hubzilla v. 8.4 is currently running on YunoHost. v. 8.6 was released yesterday. Does anyone here have experience with Hubzilla under YunoHost? How long does it usually take until a new version is available in the update function of the administration interface?

With Mastodon, I have already carried out two updates that were available in the administration interface extremely quickly after release.
[09:35:05] <lapineige> > <@pepecyb:matrix.org> Hello, I am relatively new to YunoHost (since 30.05.2023). It runs on a vServer.
>
> Currently I only have two services running: Hubzilla and Mastodon.
>
> Until 30.06. I had installed Hubzilla " by foot" (from the Git repo). As usual, I updated Hubzilla via SSH with /uels/udall.
>
> Hubzilla v. 8.4 is currently running on YunoHost. v. 8.6 was released yesterday. Does anyone here have experience with Hubzilla under YunoHost? How long does it usually take until a new version is available in the update function of the administration interface?
>
> With Mastodon, I have already carried out two updates that were available in the administration interface extremely quickly after release.

It all depends on how many people are available to put some energy on make the update (its complexity depends on the changes...) and test it
[09:54:28] <pepecyb> I know that. ;-)

I was hoping for other users' experiences of how long it takes on average.

Is it actually a problem (not only with Hubzilla) if you update yourself using the software's update function, which is partly available (i.e. in my specific example, an update via SSH with Hubzilla's update script)?
[10:10:07] <lapineige> The thing is you can never predict it, unless it's already in the making
[10:10:56] <lapineige> From what I saw in various app, if it's not already made and currently tested, it can take anything between 1 day to months...
[10:11:25] <lapineige> (And it's not publicly in the making right now from what I can see)
[10:15:16] <pepecyb> Well, I have patience. ;-)

But again to my follow-up question:

I could(!) update Hubzilla via Hubzilla's own update script. No problem via ssh. I just don't know if that would somehow "damage" the administration by YunoHost.

Are there any experiences (also regarding other apps with their own update functionality)?
[10:44:07] <lapineige> I would rather suggest to submit a pull request for the upgrade :)
If you're lucky it's a normal update and you only have yo provide the URL and sha256sum for the source file.
I see there is a bot configured, I guess it should push such an update within 24h
[10:44:44] <lapineige> Hence automated testing will be made, and it's a lot more secure this way than upgrading manually out of Yunohost process
[10:51:11] <pepecyb> Okay, thanks.
[16:20:40] <pepecyb> BTW:

The update is already there. Seems to go quite quickly at Hubzilla, too.

"Hubzilla (hubzilla) from 8.4.2~ynh1 to 8.6~ynh1"
[17:30:35] <lapineige> Good news 🙂
[17:37:31] <josh> Hi all
[17:38:00] <josh> Any place to make a small one time donation to YunoHost (specifically to those who develop it).
[17:40:31] <tituspijean> https://donate.yunohost.org ❤️
[17:41:29] <josh> > https://donate.yunohost.org ❤️
Ty :) <3
[17:42:35] <tituspijean> You can click on "/ month" and select "one time" ;)
[17:43:01] <josh> I'll process it in the morning tomorrow, I see it's in EURO currency or USD neither of these is my native for my bank so they might flag as fraud.. do you have a BTC address?
[17:44:17] <josh> I'd also like to get involved a little with the project
[17:44:26] <josh> I don't currently have a Github though lol
[19:12:45] <narf_narf[m]> Je sais pas si vous êtes au courant mais plusieurs pages du site web ne fonctionnent pas
[19:12:48] <narf_narf[m]> Notamment: https://yunohost.org/apps
[19:28:15] <Aleks (he/him/il/lui)> Chez moi ça marche, que veux tu dire par ne fonctionne pas ...
[19:40:05] <narf_narf[m]> Ça semble réparé en effet
[19:40:29] <narf_narf[m]> Ça affichait un long message d'erreur qui semblait dire que le serveur manquait d'espace disque