[10:55:26]
<naitx> Hi, I'm trying to set up KOReader with `Readeck 0.22.3` on `YunoHost 12.1`, but Basic authentication with username + API token keeps returning 401.
´´´
\< x-sso-wat: You've just been SSOed
...
\< HTTP/2 401
...
- Basic authentication problem, ignoring.
\< www-authenticate: Basic realm="Readeck Authentication"
\< www-authenticate: Bearer realm="Bearer token"
```
However, Bearer token authentication (`curl -v -H "Authorization: Bearer <API_TOKEN>" https://sub.domain.tld/opds`) works fine.
Since KOReader only supports username and password fields, it can't send a Bearer token. Has anyone successfully configured this, or is there a known issue with Basic auth on Readeck?
```
[10:55:32]
<naitx> Hi, I'm trying to set up KOReader with `Readeck 0.22.3` on `YunoHost 12.1`, but Basic authentication with username + API token keeps returning 401.´´´
\< x-sso-wat: You've just been SSOed
...
\< HTTP/2 401
...
- Basic authentication problem, ignoring.
\< www-authenticate: Basic realm="Readeck Authentication"
\< www-authenticate: Bearer realm="Bearer token"
```
However, Bearer token authentication (`curl -v -H "Authorization: Bearer <API_TOKEN>" https://sub.domain.tld/opds`) works fine.
Since KOReader only supports username and password fields, it can't send a Bearer token. Has anyone successfully configured this, or is there a known issue with Basic auth on Readeck?
```
[10:55:50]
<naitx> Hi, I'm trying to set up KOReader with `Readeck 0.22.3` on `YunoHost 12.1`, but Basic authentication with username + API token keeps returning 401.
´´´
\< x-sso-wat: You've just been SSOed
...
\< HTTP/2 401
...
- Basic authentication problem, ignoring.
\< www-authenticate: Basic realm="Readeck Authentication"
\< www-authenticate: Bearer realm="Bearer token"```
However, Bearer token authentication (`curl -v -H "Authorization: Bearer <API_TOKEN>" https://sub.domain.tld/opds`) works fine.
Since KOReader only supports username and password fields, it can't send a Bearer token. Has anyone successfully configured this, or is there a known issue with Basic auth on Readeck?
```
[11:01:14]
<naitx> Hi, I'm trying to set up KOReader with `Readeck 0.22.3` on `YunoHost 12.1`, but Basic authentication with username + API token keeps returning 401.
```
< x-sso-wat: You've just been SSOed
...
< HTTP/2 401
...
* Basic authentication problem, ignoring.
< www-authenticate: Basic realm="Readeck Authentication"
< www-authenticate: Bearer realm="Bearer token"
```
However, Bearer token authentication (`curl -v -H "Authorization: Bearer <API_TOKEN>" https://sub.domain.tld/opds`) works fine.
Since KOReader only supports username and password fields, it can't send a Bearer token. Has anyone successfully configured this, or is there a known issue with Basic auth on Readeck?
[11:02:24]
<Luc (he/him)> Hello there! I have a reality check question: I have a self hosted YNH instance. For something completely unrelated, I need a server to run a small task every 4 hours. So I am wondering if it is a good idea to make it run on the YNH server.
it should be isolated, so I was thinking of hosting the project on Codeberg, then using a Forgejo action with a runner running in podman. But that would mean installing Forgejo runner and podman on my YNH server. Do you think it is a super stupid idea, or not? will it be aproblem to create a user for the Forgejo runner?
[11:05:28]
<Salamandar> > it should be isolated
What do you mean by that ?
You could use a systemd timer / service, run it in a namespace (provided by systemd), it would be as isolated (if not more) as with forgejo. Or make the systemd service run your task in a container with podman.
[11:49:12]
<Luc (he/him)> well, just so that if it fails it doens't have any influence on the YNH system
[11:58:25]
<Salamandar> Oh, well, it depends how it could fail (could it crash the whole system?) but i guess there's not much risk
[12:44:01]
<Luc (he/him)> ok, thanks!
[13:12:32]
<hercut> Hello tous le monde
[13:12:33]
<hercut> Je ne connaissais pas OIDC, je voulais commencer a m'intéresser au vpn et plus exactement a Tailscale, avez vous des astuces ou préconisation avant toute chose ?
[13:12:58]
<hercut> Ah oui je regarde ca car tituspijean m'avez parlé d'utiliser du vpn pour configurer yunohost pour eviter des soucis en ca de reinstall ou ouverture de port
[13:19:53]
<hercut> il y a Pocket-ID, mais le message d'avertissement de yuh fait le boulot et donc j'hesite a l'installer
[14:03:14]
<niklas> Can someone help? I tried to upgrade Grist and it failed: https://paste.yunohost.org/raw/hunebanuzu
the restore went through, but the app doesn't start anymore. (Error: `env: ‘node’: Permission denied`)
[14:03:26]
<tituspijean> The error is around `buildtools/build.sh: line 30: 3752534 Killed`: *killed* means the server ran out of memory and stopped the process
[14:05:40]
<tituspijean> for this, try a forced-upgrade, it's most likely a files permission issue.
[14:05:47]
<niklas> Thanks, I could add some swap space and try again right?
[14:06:06]
<tituspijean> @hercut:matrix.org: j'ai une terrible mémoire, peux-tu recontextualiser ce que tu veux faire ? (là ça part dans tous les sens entre OIDC [qui sert juste à l'auth sur Headscale/Tailscale avec Dex], un VPN qui servirait à l'ouverture de port (😵))
[14:07:20]
<hercut> Ahah, Oui, j'ai un peu balancé mes idées, elle a va vite
[14:10:19]
<hercut> En fait, j'ai commencé à me renseigner sur Tailscale, Et pour pouvoir créer un compte, il demande une authentification par Oidc. C'est pour cela que je suis allé voir sur yuh si c'était possible. et je me suis souvenu d'un échange que nous avions eu sur les VPN et donc je me suis dit Pourquoi pas utiliser tailscale sur yuh
[14:34:22]
<niklas> update went through with some swap. Thanks!
[14:37:26]
<tituspijean> la version FOSS de Tailscale c'est Headscale, que tu peux auto-héberger sur YunoHost. Tu devras quand même ouvrir le port 443 au minimum pour que les clients communiquent avec Headscale. Ensuite il faut installer le client Tailscale sur le serveur pour qu'il se connecte à son propre VPN. J'ai écrit un tutoriel sur le forum (cherche "intranet" comme mot clé).
[14:56:09]
<pti-jean> Je viens de mettre à jour Roundcoub... et suite à cela je ne vois plus mes mails! Vous avez une idée ?
[15:01:09]
<pti-jean> Solution:
https://github.com/YunoHost-Apps/roundcube_ynh/issues/278
[15:01:50]
<hercut> je regarde, merci
[15:02:07]
<pti-jean> https://forum.yunohost.org/t/pb-apres-maj-roundcube-mails-vides/42755
[15:05:27]
<hercut> headscale, c'est tailscale auto hebergé c'est ca ?