[00:46:07]
<rodinux> A zut un chromosome Y...
[02:55:24]
<Jim> Is it possible to set up a vpn and still access my apps remotely? Is there a way to do split tunneling via the Wireguard app?
[05:48:40]
<dragon> when i ping `packages.joinpeertube.org` it returns a different URL `bernice.framasoft.org`
i'm unsure if this is normal behaviour...
[08:12:01]
<Joris> https://aria.im/_bifrost/v1/media/download/Ab-xU-xpevKIekRZsLbYbUy4NbiLONqSG3ty-8eddg3Ml3nPqGTJnWI1ooixCiaP3v7768ct3AA-tHtoc1QBbWJCebK124sgAG1hdHJpeC5vcmcvRldqWXdrYXZIT1djRUxMS09zeFpEdlhQ
[08:12:55]
<Joris> La création de domaine tourne depuis hier soir, comment on Ctrl-C dans un navigateur web ? 😬
[08:14:12]
<Joris> en: my yuno web interface is stuck on a domain creation since 12h, how to I interupt it?
[08:16:59]
<Joris> en: my yuno web interface is stuck on a domain creation since 12h, how do I interupt it?
[08:24:50]
<Chatpitaine Caverne> Joris: It can be a loss of contact between GUI and job on server.
If you have terminal access, you can try to see the log with :
`sudo yunohost log show last`
to be sure the domain creation is finished.
and then do a refresh (F5) on the GUI.
If the log says also "signing certifgicate" then there is a trouble with certificate.
[08:26:18]
<Joris> the last log is not the domain creation but a finished previous action
[08:27:34]
<Joris> I've already closed my browser last evening et relaunched it this morning (with the whole computer in fact), so i'm not sure F5 would do something
[08:31:02]
<Chatpitaine Caverne> And does your new domain exists in :
`sudo yunohost domain list`
[08:32:35]
<Chatpitaine Caverne> If yes :
`sudo yunohost domain info DOMAIN.TLD`
[08:32:59]
<Joris> ho, in fact I've run the command on another server 😅
[08:33:36]
<Joris> so the last log contain "- 2025-12-15 20:39:26,419: INFO - Signing certificate...
"
[08:33:53]
<Joris> so the last log contain "- 2025-12-15 20:39:26,419: INFO - Signing certificate..."
[08:34:20]
<Joris> how do I know if an yunohost operation is running or finished from the CLI?
[08:35:17]
<Chatpitaine Caverne> A linux equivalent to yunohost log show last:
`tail -f /var/log/yunohost/yunohost-api.log`
[08:35:25]
<Joris> The new domain appears on with `domain list`
[08:36:05]
<Joris> can I do a `ps` or something ?
[08:36:30]
<Chatpitaine Caverne> so try to get info on it and see if there is a certificate :
`sudo yunohost domain info DOMAIN.TLD`
[08:38:56]
<Joris> so the domain is selfsigned
[08:39:19]
<Joris> `joris@intra:~$ sudo yunohost domain info lan.intra.lafab.org
apps:
certificate:
ACME_eligible: None
CA_name: intra.lafab.org
CA_type: selfsigned
has_wildcards: True
style: warning
subject: lan.intra.lafab.org
summary: selfsigned
validity: 3649
main: False
registrar: parent_domain
topest_parent: intra.lafab.org
`
[08:39:51]
<Joris> https://aria.im/_bifrost/v1/media/download/AWeoygXvr4--JI_Arj0wpkUa1EiHAFX7BrZvq7rDNL1AUg6clBXLw09QQaJW42b7KVWruTgMGDIyiaywGdH_wrFCebK3c2CwAG1hdHJpeC5vcmcvbHVkY0JVc29SUE5STkVjVEVldlF5UU5z
[08:41:07]
<Chatpitaine Caverne> When you go on GUI. Can you navigate in menu or always locked and back to the domain creation operation ?
[08:41:36]
<Chatpitaine Caverne> Cause if menu available, you can go on domain and ask for a let's encrypt certificate
[08:41:46]
<Joris> no I'm stuck with the action on top on everything
[08:42:23]
<Joris> and the "windows" action come back even if a close/reopen the GUI
[08:42:56]
<Joris> OK, I can do something brutal like rebooting the server
[08:43:22]
<Joris> but I'm curious how to handle this the correct way?
[08:43:35]
<Chatpitaine Caverne> Aarrrffff.
Maybe CTRL + F5 (before brutallity).
[08:44:38]
<Joris> the question is more : how do I kill the yunhost action?
[08:47:01]
<Joris> I have this process running `root 1007884 0.2 0.2 25408 18436 ? S 06:25 0:28 python3 /bin/yunohost domain cert renew --email `
[08:48:46]
<Joris> I'm not sure its related
[08:49:27]
<Joris> no, the GUI is working I guess, that is there a pending action and the GUI show it to me
[08:53:18]
<Chatpitaine Caverne> It looks related to me.
Well, I never met a case like that. And never had to kill the api service...
But cause it's the api queue which is working, you can't use yunohost command using this queue to kill it. So linux way :
`sudo service yunohost-api stop`
and then start again.
But I'd prefer someone yunohost expert confirm.
[08:56:10]
<Joris> We can wait a little bit, I'm also interested to learn more about this
[08:56:27]
<Joris> I found nothing on the forum
[10:03:09]
<captainhonora> Is it possible to have two yunohost instances with free domains while under the same network, or is it limited to one?
[10:03:43]
<captainhonora> ie: I have a server running for my team and now wondering if I could use a raspberry pi for a personal server
[10:05:58]
<Joris> your first server has a public IP, the second need another one
[10:06:16]
<Joris> (for the main normal server behavior)
[10:14:36]
<Joris> I'm trying to rephrase it: there is no problem to have another yunost machine in the same network. You can have as much you want. But in order to be fully functional as a server (and not just a computer with debian and yunohost just laying around in your network), you will need proper network configuration. Usually with a common internet service provider, you have only one public facing IP (internet adresse).
[10:15:27]
<Joris> so the easy way is to "register" your yunohost server to respond to that IP adress
[10:16:25]
<Joris> it's more or less automatic with the free domain
[10:16:40]
<Joris> is it clear?
[10:17:23]
<Joris> I'm trying to rephrase it: there is no problem to have another yunost machine in the same network. You can have as much you want. But in order to be fully functional as a server (and not just a computer with debian and yunohost just laying around in your network), you will need proper network configuration. Usually with a common internet service provider, you have only one public facing IP (internet adress).
[10:17:32]
<Joris> The issue is: public internet acces. How do you make the server accessible from the outside?
[10:18:09]
<Joris> I'm trying to rephrase it: there is no problem to have another yunost machine in the same network. You can have as much you want. But in order to be fully functional as a server (and not just a computer with debian and yunohost just laying around in your network), you will need proper network configuration. Usually with a common internet service provider, you have only one public facing IP (internet address).
[10:19:32]
<Joris> I'm trying to rephrase it: there is no problem to have another yunohost machine in the same network. You can have as much you want. But in order to be fully functional as a server (and not just a computer with debian and yunohost just laying around in your network), you will need proper network configuration. Usually with a common internet service provider, you have only one public facing IP (internet address).
[11:20:31]
<captainhonora> Thanks.
"so the easy way is to "register" your yunohost server to respond to that IP adress (edited)"
How do I differentiate the two later, say in my browser
[11:31:41]
<Joris> You can read this part of the documentation : https://doc.yunohost.org/en/admin/get_started/post_install/port_forwarding
[12:49:35]
<captainhonora> That's not my question tho.
[12:52:18]
<captainhonora> I read it before, the ports are opened. This documentation page does not specify in practical terms how to have multiple yunohost instances on the same wifi or how that interacts with the free domains.
[13:07:56]
<Joris> So very practically when you type your free domain in a web browser let's say "myynh.nohost.me", the DNS system resolve it to the public IP, lets says 12.34.45.68, then the request arrive at your ISP box, that look at its port-forwarding configuration and send to request to the local IP lets says 192.168.1.10 at that your first yunohost server.
No if you have another free domain, let's say "otherynh.nohost.me", it will be resolve to the same public IP adresse, the previous 12.34.45.68, and thus to 192.168.1.10 again. But your second server will have another local IP, for example 192.168.1.20.
So by default, that won't work
[13:10:52]
<Joris> it's possible to work around that, I see two main path
1. use a VPN for the second server (but it's usually not free of charge)
2. using non standard port number (but it's cumbersome)
[13:14:04]
<Joris> there is also local domain (but only reachable in your local network)
[13:22:11]
<captainhonora> Right ok, thanks a lot for explaining!
[13:22:20]
<Joris> to be honest, paying a VPN is the only reasonable way to host to fully functional second server in such a situation (and you probably need a real paid domain also). But it's possible, i'm doing that personally in order to reuse a good fiber connection of somebody else
[13:22:54]
<Joris> you'r welcome
[13:23:34]
<captainhonora> Can you share more info on your VPN setup? not so much the provider but on the side of yunohost on that machine what do you do to make it work.
[13:24:40]
<Joris> Basically you will need to configure https://apps.yunohost.org/app/vpnclient
[13:25:03]
<captainhonora> Ohh thanks I didn't know this existed
[13:25:36]
<captainhonora> Do you still get a nohost.me or ynh.fr domain with this method?
[13:26:05]
<Joris> I'm not sure, I'm not a user of the kind of domain
[13:26:46]
<captainhonora> Thanks again for the help I will try that and report back if I can't figure it out on my own.
[13:27:20]
<Joris> You can look again at this part of the documentation https://doc.yunohost.org/en/admin/get_started/methods#at-home-behind-a-vpn
[13:51:41]
<@err404:matrix.numericore.com> For ipv6, it is easier because we have generaly /64 given by the provider, so it is no necessary to have nat or reverse proxy sni
[13:52:17]
<@err404:matrix.numericore.com> If you want share the same and uniq ipv4 for multiples servers (yunohost or other), you will need a reverse proxy sni (example:haproxy)
[15:57:05]
<Chatpitaine Caverne> Le Pi5 est arrivé. Commandé avec le magnifique mini boitier Pironman 5 Max. C'est du luxe, mais finalement on hérite d'une vraie alim', d'un vrai refroidissement et on prépare l'avenir quand les disques actuels seront morts avec 2 M2-NVME Raid 0/1 disponibles. Et c'est là que le Pi5 était le moins cher en disponible (bon, ça reste cher pour un Pi).
C'est magnifique en tout cas et très fonctionnel.
Par contre, la magie n'opère pas. J'ai tenté à la one again (oups, ça va se voir que je ne suis plus tout jeune) en éteignant l'ancien et en branchant ses disques dessus. Il a bien vu qu'il y avait un système en USB (contrairement au Pi4 qui ne voyait la possibilité de booter en USB que si on le lui disait) mais ce système ne lui plaisait pas du tout. Je pense qu'il doit y avoir des méthodes futées en trafiquant le /boot mais je n'ai pas le niveau.
Je vais donc procéder à la méthode d'installation Debian / Curl Yunohost / Restauration sur nouveau système.
Auparavant, je vais faire une installation/restauration à blanc en guise de répétition générale.
Cela fera une plus longue interruption de service et donc probablement nuitamment (ça me rappellera le boulot, beurk).
Voilà pour l'expérience loupée.
[18:38:10]
<EverlastingOS> Hey guys, did install movim on my yunohost server, it says I need to set up an account as admin.
When tryinh to add the account i get:
[18:39:03]
<EverlastingOS> User x@yunohost.eu not found"
[18:39:36]
<EverlastingOS> cannot I just chose any random email to register as an admin account
[19:51:15]
<Joris> Chatpitaine Caverne: Finally I did a `sudo systemctl restart yunohost-api`
see https://forum.yunohost.org/t/stuck-in-domain-creation-and-certificate/41105/6
[20:41:20]
<trendless> > <EverlastingOS> cannot I just chose any random email to register as an admin account
Is x@yunohost.eu an existing jabber account and have you logged into movim with it?
[20:42:26]
<trendless> > <EverlastingOS> cannot I just chose any random email to register as an admin account
Is x@yunohost.eu an existing jabber account/id and have you logged into movim with it?
[20:47:41]
<EverlastingOS> > > <EverlastingOS> cannot I just chose any random email to register as an admin account
>
> Is x@yunohost.eu an existing jabber account/id and have you logged into movim with it?
no just a radom one i did test with, BUT i did test with a account I can log in with on movim, got same error
[21:34:06]
<trendless> EverlastingOS: Ah ok. So you logged into movim with a jabber account, then ran the command to set that same jabber account as admin and it failed?
[21:34:26]
<trendless> EverlastingOS: Ah ok. So you logged into movim with a jabber account, then ran the command to set that same jabber account as admin and it said it couldn't find it?
[22:13:22]
<homelab-fr> Bonsoir est-ce que quelqu'un sait quand sera t-il possible d'installer Meet (de la Suite) https://github.com/YunoHost-Apps/meet_ynh?tab=readme-ov-file svp ?