[00:04:15]
<ljf> AUthorized users are those in this groups `ssh.main sftp.main ssh.app sftp.app admins root`
[00:05:18]
<ljf> You can list who is in each groups with `getent group admins` (here the example is with `admins` group)
[05:54:21]
<selfhoster1312> ha thanks i always forget about getent for nss / dynamic stuff :-)
[05:58:56]
<selfhoster1312> looks like SSH does not see the user's groups: https://paste.yunohost.org/iditoxibiq.apache but the user is in the ssh.main group:
> # getent group ssh.main
> ssh.main:*:5003:sal,mediatek
[05:59:38]
<selfhoster1312> (tbh i can live with that, only root SSH allowed, i just need to make a PR to enable public key login for root on WAN)
[06:00:49]
<selfhoster1312> but that but has been here as long as i can remember, which is why i previously added manually the users in an `AllowUsers` directive
[17:27:56]
<DrPi> A priori, pas de problème de ce coté là. Ma machine est équipée d'un SSD qui n'a que 18 mois d'ancienneté. Mais oui, je sais, on n'est pas à l'abris d'une défaillance.
Une idée pour corriger le problème de démarrage du service ?
[19:50:37]
<prob> Good evening, for about 1-2 days I have been struggling with my DNS/IP setup. I am constantly getting my old IPv4 and 6. When checking ns0, ns1 and ns2 I noticed that ns2.yunohost.org still has my old IPs from 2 days(?) ago. This seemingly led to my subdomains getting new IPs while my main-domain is stuck at my old IP. I also can no longer access my server via Internet (web&ssh). Can anyone help me please? 🙏
[20:08:51]
<doesnm> https://aria.im/_bifrost/v1/media/download/ARxqExuKogJkJMh_7ayLz1H4EMaa4TC-Dmp9N9pb76Oxs7XD0PNbLK9dlmxkSeXRV9Wlw-_28YzNIqCBT2Ljk3BCeg31W3swAGRvZXNubWxhYi54eXovNUY4VVd6Y2ptNzJKVnJuT1ZkVUdzb3g4RTE2c0lZSGg
[20:08:57]
<m606> hello, so you use a ynh.fr / nohost.me domain? what is the context of your server (VPS, machine you have physical access to, ...)? can't you access webadmin via `https://YOUR_CURRENT_SERVER_IP`?
[20:15:24]
<prob> @m606
I use nohost.me, local machine. Locally I can access my server via it's local IP, outside my LAN I can not access it anymore, simply because name resolution fails because all of my used DNS (cloud9, mullvad, adguard) receive my old IP.
[20:46:55]
<m606> i'm referring to this section: https://doc.yunohost.org/en/admin/get_started/post_install/port_forwarding
[20:49:03]
<m606> i get your point about the name resolution issue related to your nohost.me domain. But can you access your server from outside the LAN via IP somehow? I guess that this other point would relate to your router config?
[20:50:54]
<prob> m606: Yes I can, I can ssh into it correctly from outside my LAN by using public IP. I should mention that my setup worked for months at this point, port forwarding works as well except the usual mail suspect, which is of no concern for me.
[20:52:21]
<prob> of course it only works with the correct IP, not the one propagated falsly to some DNS
[21:04:14]
<m606> can you make sure no DNS resolves your domain name correctly ? https://dnschecker.org/#A/
[21:13:19]
<prob> *some* have the correct entry, but it is going back and forth. i assume it is because ns0 and ns2 are correct, only ns1 has my old IPs. i monitored that the whole day, earlier there were 18 correct resolutions, now there are only 12 (default settings, matching the first octet of my ipv4)
[21:14:01]
<prob> https://share.conversations.im/prob/message/nlIUiqP3Ye4sC6Tq/OwUdlpBaQ_mouxIF_w1kxw.jpg
[21:15:36]
<prob> others resolve it as well, but to a wrong IP. thus they lead somewhere but not to me 😂
[22:03:58]
<m606> ok I guess we need a YNH infra admin to look the entry for your domain