Wednesday, February 12, 2025
support@conference.yunohost.org
February
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
   
             

[00:14:04] <tripop> Oui ça je l'ai fais aussi, on verra 🤞
[02:58:35] <sem> I ended up using certbot (snap) to get a wildcard certificate, and used a symlink from /etc/letsencrypt/live/y.example.com/privkey.pem to /etc/yunohost/certs/y.example.com/key.pem
[02:59:18] <sem> and also /etc/letsencrypt/live/y.example.com/fullchain.pem to /etc/yunohost/certs/y.example.com/crt.pem
[02:59:33] <sem> I am hopeful that when certbot automatically renews these certs, it will not break anything.
[03:02:02] <sem> trying to follow https://doc.yunohost.org/en/certificate_custom
[03:51:52] <sem> can yunohost use systemd for systemd-resolved? I am trying to get tailscale to interoperate with dnsmasq
[04:00:49] <sem> The reason I am thinking this is a problem is because when I go to y.example.com, I get a connection error, even though I have a DNS entry in my router to point to the correct IP address of yunohost
[04:01:27] <sem> but I can go to y.example.com.mynetworksettings.com; and this goes through to yunohost for some reason
[04:02:08] <sem> I expect that y.example.com should go to yunohost because I have a DNS entry in my router for nc.example.com pointing to a different machine with nextcloud, and that one works correctly
[04:02:22] <sem> so there's something I don't understand
[04:12:15] <sem> Do I have to put 127.0.0.1 y.example.com into /etc/hosts ?
[04:24:33] <sem> Or is it 127.0.1.1 y.example.com ?
[05:02:50] <sem> finally figured it out
[05:03:04] <sem> i had to put the DNS entry into pi-hole, not into the router......