[09:07:36]
<rainer.szs> Hello, I'm having issues logging in owncloud. I input the correct credentials but I got this error instead: "Password
Unexpected HTTP response: 500. Please check your connection and try again."
The log of the service is:
```
Mar 15 09:47:36 systemd[1]: Started owncloud.service - ownCloud: Infinite Scale server.
Mar 15 09:47:46 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:47:46+01:00","message":"failed to authenticate the request"}
Mar 15 09:48:09 ocis[3892]: {"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:35846","time":"2026-03-15T09:48:09+01:00","message":"invalid credentials"}
Mar 15 09:48:09 ocis[3892]: {"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2026-03-15T09:48:09+01:00","message":"identifier failed to logon with backend"}
Mar 15 09:48:20 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:48:20+01:00","message":"failed to authenticate the request"}
Mar 15 09:48:37 ocis[3892]: {"level":"error","service":"storage-system","pkg":"rgrpc","traceid":"-","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"-"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2026-03-15T09:48:37+01:00","message":"failed to list storage spaces"}
Mar 15 09:49:02 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:49:02+01:00","message":"failed to authenticate the request"}
Mar 15 09:49:37 ocis[3892]: {"level":"error","service":"storage-system","pkg":"rgrpc","traceid":"-","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"-"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2026-03-15T09:49:37+01:00","message":"failed to list storage spaces"}
Mar 15 09:49:40 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:49:40+01:00","message":"failed to authenticate the request"}
Mar 15 09:50:22 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:50:22+01:00","message":"failed to authenticate the request"}
Mar 15 09:50:37 ocis[3892]: {"level":"error","service":"storage-system","pkg":"rgrpc","traceid":"-","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"-"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2026-03-15T09:50:37+01:00","message":"failed to list storage spaces"}
Mar 15 09:51:01 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:51:01+01:00","message":"failed to authenticate the request"}
Mar 15 09:51:37 ocis[3892]: {"level":"error","service":"storage-system","pkg":"rgrpc","traceid":"-","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"-"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2026-03-15T09:51:37+01:00","message":"failed to list storage spaces"}
Mar 15 09:51:40 ocis[3892]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T09:51:40+01:00","message":"failed to authenticate the request"}
```
According to the [same issue on github](https://github.com/YunoHost-Apps/owncloud_ynh/issues/68) I deleted ldap.crt and ldap.key, so they got generated again but nothing changed and I still get the same error
[09:09:02]
<rainer.szs> https://aria.im/_bifrost/v1/media/download/AVs7KzWjtLmYtPbqMRgyrNQrTcZCw2PVfv4b30BSC48Qu-pshq1ZuzRU5UPoLkas1nvJY25yRc13M5kSXMIDVFZCec9efqfgAG1hdHJpeC5vcmcveUJKd0lraWJRb1pNSUhHcHpZeUJmd1Zl
[09:11:18]
<DJ Chase (fae/faer)> do you have prometheus node exporter or that machine as well by chance?
[09:23:53]
<rainer.szs> I'm sorry I don't know, how can I check?
[09:24:09]
<rainer.szs> I never installed it manually so unless it's preinstalled, no I don't
[09:44:43]
<DJ Chase (fae/faer)> you don't then
[14:00:24]
<rainer.szs> anyone?
[14:38:12]
<DJ Chase (fae/faer)> (i don't know i used my one idea)
[14:55:00]
<DJ Chase (fae/faer)> i actually had the same issue but i also had a lot of other issues going on so i'm addressing this one later™️
[14:56:13]
<m606> hello, did you actually have originally the same exact error message as in the github issue you linked to ? in particular `remote error: tls: bad certificate` ?
[15:00:39]
<m606> and can you confirm that files are actually regenerated in `/home/yunohost.app/owncloud/idm/` ?
[15:01:19]
<m606> (`ldap.crt` and `ldap.key`)
[15:06:11]
<rainer.szs> What happened specifically is that before this error, I got this one instead
[15:06:24]
<rainer.szs> https://aria.im/_bifrost/v1/media/download/AeuxNkXFeBJlxCRyr4HsP5QLHrxf3S83Ovx1V-lDtYcEUZxGVQ1Xxzvo39Trq0xPcsFEUFCKi3hlmgiXCKR6hNBCec9y8X7QAG1hdHJpeC5vcmcvam1OZHVYRmRTaGNDU1dxa29DRUdEWHBh
[15:08:52]
<m606> do you have the logs for the service of this earlier state ?
also it's not a new install, right ? you had already logged in before ?
[15:09:38]
<rainer.szs> (I don't have the service log for it anymore) this error occured once two months ago, so to avoid it I reinstalled owncloud and logged in again
Now, today I encountered this error again because I didn't log in a month, so I tried to reinstall owncloud. Now that I reinstalled it, I got the "Unexptected http response error", and in the service log I can read:
```
Mar 15 16:07:52 ocis[6186]: {"level":"error","service":"storage-system","pkg":"rgrpc","traceid":"-","error":"error: not found: space jsoncs3-public-share-manager-metadata not found","status":{"code":6,"message":"not found when listing spaces","trace":"-"},"filters":[{"type":2,"Term":{"Id":{"opaque_id":"jsoncs3-public-share-manager-metadata!jsoncs3-public-share-manager-metadata"}}}],"time":"2026-03-15T16:07:52+01:00","message":"failed to list storage spaces"}
Mar 15 16:08:17 ocis[6186]: {"level":"error","service":"idm","bind_dn":"uid=idp,ou=sysusers,o=libregraph-idm","op":"bind","remote_addr":"127.0.0.1:43694","time":"2026-03-15T16:08:17+01:00","message":"invalid credentials"}
Mar 15 16:08:17 ocis[6186]: {"level":"error","service":"idp","error":"ldap identifier backend logon connect error: LDAP Result Code 49 \"Invalid Credentials\": ","time":"2026-03-15T16:08:17+01:00","message":"identifier failed to logon with backend"}
```
[15:10:55]
<rainer.szs> I'll delete them again and check
[15:11:33]
<m606> no i meant are those files there? you issue does not seem to be the same as in that github issue
[15:11:51]
<m606> but if you deleted the files, we need to make sure some new ones are there
[15:12:42]
<rainer.szs> https://aria.im/_bifrost/v1/media/download/AYGv7KKwQy3oqkq7-UEqbTavXgyC_qqwvQkXEbHr4Amv3YWuIeQRghibZ8afU5v3KWpgDcuBR5HdPNVEhD1DrztCec9zTdDgAG1hdHJpeC5vcmcvc1JmY2tjRXhsSnlSdHhQSVhJa21CaUFa
[15:13:56]
<rainer.szs> I still have and old backup of owncloud, I could test that too
[15:14:14]
<rainer.szs> To resolve this instead
[15:15:28]
<m606> was it the app admin account which returned that error? or a user account?
[15:16:04]
<rainer.szs> I tried to log as admin, other users can't access to owncloud
[15:16:12]
<m606> i mean the old error
[15:16:45]
<rainer.szs> I locked access to owncloud to visitors and some other users I created
[15:17:52]
<m606> locked? do you mean that YNH SSO permissions are only given to admin and a few other accounts?
[15:18:36]
<rainer.szs> it means that other users cannot see the owncloud tile in the app panel menu
[15:19:23]
<rainer.szs> "Group/users allowed to access: rainer"
[15:20:09]
<rainer.szs> So I don't know if some owncloud accounts have been created for other accounts but as inaccessible, or the admin account is the only one that has been created
[15:20:16]
<rainer.szs> for owncloud
[15:22:02]
<m606> do you currently have actual personal data in that owncloud instance?
[15:23:11]
<m606> or could you remove it without loss?
[15:23:29]
<rainer.szs> Do you mean data that i don't want to share with anyone or any type of data?
[15:23:40]
<m606> no i mean documents
[15:24:18]
<m606> or is it at the moment a fresh install with nothing important in it ?
[15:25:30]
<rainer.szs> i think it still has old data since I haven't purged them, but I can delete them from this instance if needed since I have old yunohost owncloud backups
[15:26:13]
<rainer.szs> and they're not extremely important
[15:27:34]
<m606> hmm bascially as you seem to have uninstalled/reinstalled a few times to try and solve issues, i wonder whether there could be something in your app config located `$data_dir` which could somehow create a conflict
[15:29:34]
<m606> maybe using SSH command `sudo yunohost app remove owncloud --purge` (removes the $data_dir) and then reinstall the app would help, but you would loose all current existing data and config in your owncloud instance. so up to your decision.
[15:30:09]
<m606> also that would not be solving the issue, more of a radical workaround
[15:30:17]
<rainer.szs> could i restore data with a yunohost backup once reinstalled?
[15:30:20]
<rainer.szs> yeah pretty much
[15:30:25]
<m606> check your backup first
[15:30:30]
<rainer.szs> ok
[15:30:37]
<m606> is the data folder in it ?
[15:30:56]
<m606> well you can also backup the data folder now
[15:31:25]
<m606> got to go, i'll be back later
[15:31:44]
<rainer.szs> alright, thank you for helping
[15:37:48]
<rainer.szs> https://aria.im/_bifrost/v1/media/download/ARl-VkNjymXrIBLrbrf5auDU_lSqWeBv-xE-qqmbVYvAsqQum_byaaC5pZvTAoikWi0hCIOjL1yKGAtq-C0BVBdCec90vXpAAG1hdHJpeC5vcmcveE5KbG5QeFNLUHdSbWZVa3dKb250bGZa
[15:38:54]
<rainer.szs> I created a link to owncloud so that the data could get moved to a different partition with the old installation, is that the reason the new installation is conflicting with the old one?
[15:40:37]
<rainer.szs> i did it by following the documentation: https://doc.yunohost.org/en/admin/tutorials/moving_app_folder/
[15:41:09]
<rainer.szs> The same error occurs after purging all data from the web admin panel. This is a fresh install
[15:42:47]
<rainer.szs> I created a link to owncloud in february (by following the documentation: https://doc.yunohost.org/en/admin/tutorials/moving\_app\_folder/) so that the data could get moved to a different partition with the old installation, is that the reason the new installation is conflicting with the old one?
[16:44:29]
<rainer.szs> I'm even more confused
[16:44:33]
<rainer.szs> Ok so, in both cases I restore it from an old backuo OR with a fresh install the service log shows:
`Mar 15 16:55:20 ocis[11433]: {"level":"error","service":"proxy","error":"failed to verify access token: oidc: failed to decode provider discovery object: expected Content-Type = application/json, got \"text/html\": <nil>","authenticator":"oidc","path":"/ocs/v2.php/cloud/capabilities","user_agent":"Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0","client.address":"(public ip)","network.peer.address":"","network.peer.port":"","time":"2026-03-15T16:55:20+01:00","message":"failed to authenticate the request"}`
[16:44:41]
<rainer.szs> This is the error I got this morning that made me reinstall owncloud in the first place 👆️
[16:48:52]
<m606> when you SSH on the instance, what returns `curl --silent -u owncloud:owncloud 'http://localhost/ocs/v2.php/cloud/capabilities'`?
[16:48:53]
<m606> when you SSH on the instance, what returns `curl -u owncloud:owncloud 'http://localhost/ocs/v2.php/cloud/capabilities'`?
[17:40:11]
<rainer.szs> ```
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
```
[17:41:32]
<rainer.szs> (Not prioritary right now but coincidentally, the same type of error happens while trying to linking jellyfin with finamp on android, i don't know what's causing this)
[17:41:59]
<rainer.szs> https://aria.im/_bifrost/v1/media/download/AbKmAEiwOufiWNIfq8V9bPg1NvSZ6HP46DWexQFEyeEjH561BTbc38-zJZ1VZsVjOz-K3BlrfmDk-yu-VWlvUQxCec972I_gAG1hdHJpeC5vcmcvR0h3aVlhbXBHWFhkeWFrY1BhWHJKQ3ND
[17:54:29]
<orhtej2> > <@rainer.szs:matrix.org> ```
> <html>
> <head><title>302 Found</title></head>
> <body>
> <center><h1>302 Found</h1></center>
> <hr><center>nginx</center>
> </body>
> </html>
> ```
>
`curl -L`, same rest of params
[18:07:23]
<orhtej2> > <@rainer.szs:matrix.org> `curl -L owncloud:owncloud 'http://localhost/ocs/v2.php/cloud/capabilities'`
>
>
> ```
> curl: (3) URL using bad/illegal format or missing URL
> curl: (60) SSL certificate problem: unable to get local issuer certificate
> More details here: https://curl.se/docs/sslcerts.html
>
> curl failed to verify the legitimacy of the server and therefore could not
> establish a secure connection to it. To learn more about this situation and
> how to fix it, please visit the web page mentioned above.
> ```
>
Just add -L, leave -u as it was
[18:15:30]
<orhtej2> -L means follow redirects, 302 is not the final result of this call
[18:15:41]
<rainer.szs> `curl -L owncloud:owncloud 'http://localhost/ocs/v2.php/cloud/capabilities'`
```
curl: (3) URL using bad/illegal format or missing URL
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
[18:16:59]
<rainer.szs> ```
curl: (3) URL using bad/illegal format or missing URL
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
```
but it's the same as before
[18:17:00]
<rainer.szs> Or it shows like this
```
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
if -L and -u are inverted
[18:17:00]
<rainer.szs> When asking for "host password of user -L" does it refer to my yunohost password or owncloud password?
[18:17:22]
<m606> YNH
[18:17:31]
<m606> and if you curl to https instead of http, same issue ?
[18:17:39]
<rainer.szs> I'll check
[18:19:29]
<rainer.szs> same as this
[18:42:12]
<m606> so you used `curl -L -u owncloud:owncloud 'https://localhost/ocs/v2.php/cloud/capabilities'`, right ?
[18:46:42]
<rainer.szs> yes
[18:48:01]
<orhtej2> ok, this is a problem, you've been redirected to YNH SSO page
[18:48:07]
<rainer.szs> yes
[18:48:07]
<m606> but you still have the "bad URL" thing?
[18:48:08]
<orhtej2> so the URL does not exist basically
[18:48:14]
<m606> and then `curl -u owncloud:owncloud -L 'https://localhost/ocs/v2.php/cloud/capabilities'` is different?
[18:48:15]
<orhtej2> or is behind SSO
[18:50:26]
<rainer.szs> wait
[18:50:33]
<rainer.szs> I misread, it shows like this
```
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
[18:50:37]
<rainer.szs> without (3) URL using bad/illegal etc etc
[18:50:41]
<m606> and the order of parameters doesn't change anything?
[18:50:42]
<rainer.szs> curl -u -L owncloud:owncloud 'https://localhost/ocs/v2.php/cloud/capabilities'
outputs:
```
Enter host password for user '-L':
curl: (3) URL using bad/illegal format or missing URL
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
while curl -L -u owncloud:owncloud 'https://localhost/ocs/v2.php/cloud/capabilities'
outputs:
```
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
```
[18:50:44]
<m606> ok, so we keep the second one, and let's try and bypass certificate - `curl -Lk -u owncloud:owncloud 'https://localhost/ocs/v2.php/cloud/capabilities'`
[18:50:53]
<rainer.szs> 😐️
[18:50:54]
<rainer.szs> Did I mess something up?
[18:50:54]
<rainer.szs> I think I messed with the permissions and that's the reason it redirects to the SSO
[18:50:55]
<m606> i can't test the app myself, so at the moment I don't know if it an issue on your instance or in the package
[18:50:56]
<orhtej2> `/ocs/v2.php/cloud/capabilities` <- where did you get this path from?
[18:50:56]
<m606> but yes SSO is related to permission
[18:50:57]
<m606> @orhtej2:circledsquareroot.ovh the error logs above
[18:50:58]
<orhtej2> is owncloud running on dedicated domain?
[18:50:58]
<rainer.szs> omg *facepalm* i'm sorry 😭
[18:50:59]
<rainer.szs> No, it's a .nohost,me domain
[18:50:59]
<m606> @orhtej2:circledsquareroot.ovh e.g. the linked one here
[18:51:00]
<rainer.szs> it's owncloud.(domain).nohost.me
[18:51:01]
<orhtej2> yes but is it installed on `root.tld` on `root.tld/whatever`?
[18:51:02]
<rainer.szs> one moment please
[18:51:03]
<orhtej2> ok, so whole domain
[18:51:05]
<orhtej2> they won't be able to log in but will be able to see the login form without logging in
[18:51:05]
<rainer.szs> i'll restore the old premissions
[18:51:05]
<rainer.szs> yes
[18:51:05]
<orhtej2> can you (temporarily) give permission to visitors for owncloud?
[18:51:06]
<rainer.szs> and just hide the tile to access
[18:51:07]
<rainer.szs> No it was a permission problem, I can log now
[18:51:07]
<rainer.szs> I can't be this dumb
[18:51:07]
<otm33> I didn't read the whole thread but could it be related to protect_against_basic_auth_spoofing param ?
[18:51:08]
<m606> so you are fine with granting perm to visitors?
[18:52:31]
<rainer.szs> I don't want other people to log into my owncloud session
[18:55:00]
<rainer.szs> is there a way to restore all the default permissions?
[18:55:53]
<m606> well they shouldn't be allowed - then you rely on owncloud's own login system.
However you could still put login page behind YNH SSO, but I believe you have to leave the API exposed to visitors as suggests the default permissions: https://github.com/YunoHost-Apps/owncloud_ynh/blob/master/manifest.toml#L81-L88
[19:27:41]
<orhtej2> > <@m606:matrix.org> well they shouldn't be allowed - then you rely on owncloud's own login system.
> However you could still put login page behind YNH SSO, but I believe you have to leave the API exposed to visitors as suggests the default permissions: https://github.com/YunoHost-Apps/owncloud_ynh/blob/master/manifest.toml#L81-L88
Thingcis api url is wrong there
[19:55:06]
<m606> good point, what should we change it to ? `/ocs`or `/ocs/v2.php` ?
https://doc.owncloud.com/server/next/developer_manual/core/apis/
[19:56:03]
<m606> dunno if v1.php is actually used
[19:59:49]
<orhtej2> > <@m606:matrix.org> good point, what should we change it to ? `/ocs`or `/ocs/v2.php` ?
> https://doc.owncloud.com/server/next/developer_manual/core/apis/
I think ocs is fine
[20:17:18]
<orhtej2> owncloud should now work on testing branch, ty @otm33
[21:42:20]
<otm33> Thanks to m606 I guess you mean ;) The credit doesn’t belong to me
[22:50:35]
<orhtej2> one day I'll learn to read and it'll be glorious :P
[23:43:41]
<lps> I'm having issues completing a migration, any suggestions would be greatly appreciated https://paste.yunohost.org/raw/farewikopo
[23:55:45]
<rodinux> can you try `yunohost tools regen-conf apt -n -d` ?