[01:27:33]
<ulrich> > <@ulrich:nope.chat> sent an image.
Anyone?
[01:47:12]
<kirk> This happened to me sort of and I was able to get root access via `su` instead of `sudo su`
[03:01:54]
<satadaes> how can I make emails without them being yunohost accounts? I have multiple sites that need "invoices@site.tld" or "staff@site.tld" on the same yunohost server aliases arent a very good solution as some services/products don't support aliases in replies, I could thesauraus different names for the same kind of action or add site.invoices@site.tld or something like that but that also seems messy, is there a way to make email accounts that are not yunohost accounts
[03:02:05]
<satadaes> using the domains on yunohost
[03:02:44]
<satadaes> so that the emails can be the same name although different domains
[07:14:01]
<Guillaume Bouzige> I am gonna try that https://forum.yunohost.org/t/what-to-do-if-admin-cannot-sudo/21107 first otherwise I will have to try to reinstall everything fresh and transfer all apps data from previous sd-card.
[07:23:53]
<@chrichri:ween.de> > <@ulrich:nope.chat> Do I really have to use commet.chat.website.com/commet? Can I not remove either the subdomain or the / so that it's not redundant? Why do I need the /?
No idea about commet, but the error states that conduit already uses the domain and that another app (commet) couldn't do so (, because conduit needs a domain exclusively?).
[07:23:54]
<@chrichri:ween.de> > <@satadaes:matrix.org> how can I make emails without them being yunohost accounts? I have multiple sites that need "invoices@site.tld" or "staff@site.tld" on the same yunohost server aliases arent a very good solution as some services/products don't support aliases in replies, I could thesauraus different names for the same kind of action or add site.invoices@site.tld or something like that but that also seems messy, is there a way to make email accounts that are not yunohost accounts
I think I do not completely understand your question. Is it:
invoice@site1.tld → someone@email.tld and
invoice@site2.tld → someone_else@email.tld
and your services site1.tld, site2.tld and email.tld running all on the same yunohost?
[07:32:57]
<Guillaume Bouzige> I got sudo access back but know there is 'no installed app in webadmin' and when I run migration via command line I receive this error :
```root@server:~# yunohost tools migrations run
Error: Failed to read info for archivebox : Invalid version: '0.7.3~ynh1'
Error: Failed to read info for filebrowser : Invalid version: '2.31.2~ynh1'
Error: Failed to read info for forgejo : Invalid version: '9.0.3~ynh1'
Error: Failed to read info for glance : Invalid version: '0.6.4~ynh1'
Error: Failed to read info for my_webdav : Invalid version: '1.2~ynh3'
Error: Failed to read info for searxng : Invalid version: '2025.01.10~ynh1'
Error: Failed to read info for signaturepdf : Invalid version: '1.7.0~ynh2'
Error: Failed to read info for syncthing : Invalid version: '1.29.1~ynh1'
Error: Failed to read info for archivebox : Invalid version: '0.7.3~ynh1'
Error: Failed to read info for filebrowser : Invalid version: '2.31.2~ynh1'
Error: Failed to read info for forgejo : Invalid version: '9.0.3~ynh1'
Error: Failed to read info for glance : Invalid version: '0.6.4~ynh1'
Error: Failed to read info for my_webdav : Invalid version: '1.2~ynh3'
Error: Failed to read info for searxng : Invalid version: '2025.01.10~ynh1'
Error: Failed to read info for signaturepdf : Invalid version: '1.7.0~ynh2'
Error: Failed to read info for syncthing : Invalid version: '1.29.1~ynh1'
``` then the warning disclaimer...most of those apps are accessible and running just not searx and archivebox are not
[07:33:16]
<Guillaume Bouzige> most app works apart from archivebox and searx
[07:33:24]
<kirk> I just did this migration and had this issue come up
[07:33:45]
<kirk> I just kept updating things and eventually the migration ran fully and the apps came back in the webadmin
[07:33:54]
<kirk> but I didn't really understand why, lol
[07:34:40]
<Guillaume Bouzige> ok
[07:35:06]
<Guillaume Bouzige> thanks for your feedback I am running the migration again via command line this time
[07:35:11]
<kirk> I did a lot of `yunohost tools update system` and `yunohost tools upgrade system` and debugging some package issues before I was able to run the whole migration
[07:35:37]
<kirk> Good luck!
[07:41:07]
<Guillaume Bouzige> thanks kirk !
[08:19:50]
<Guillaume Bouzige> ok I made it, archivebox did not made it but using the yunohost app shell I was able to recover it
[08:21:36]
<Guillaume Bouzige> by reinstalling it via python in the venv...like explain here https://forum.yunohost.org/t/archivebox-cli-commands/30042/2 and with ```pip install --upgrade archivebox``` I had a few issue with files ownership so I solve them with ```root@server:/var/www/archivebox# chown -R archivebox .```
[08:22:20]
<Guillaume Bouzige> it is right to give rights to user archivebox in his venv folder right ?>
[08:57:13]
<thatoo> Hello,
I have installed the app zola.
I have to connect to ssh and modfy files thanks to nano.
To ease my work and avoid `chown zola:zola` every time I create a new file being root (thanks to `sudo su`), I'd like to change user to zola with `sudo su zola`.
My issue is that zola doesn't have any bash environnent so I only have `$` displaying so I don't know where I'm working. Am I in /var/www/zola or /var/www/zola/content and so on...
Second of all, as zola user, I don't have autocompletion.
How can I do that?
Can I create /home/zola and copy in it the .bashcr from the user I connect through ssh and have these feature? Is it enough or should I do something else like relaunch bash or something like that? Or I'm completely wrong and I should do something else?
[09:02:19]
<orhtej2> > <@thatoo:defis.info> Hello,
> I have installed the app zola.
> I have to connect to ssh and modfy files thanks to nano.
> To ease my work and avoid `chown zola:zola` every time I create a new file being root (thanks to `sudo su`), I'd like to change user to zola with `sudo su zola`.
> My issue is that zola doesn't have any bash environnent so I only have `$` displaying so I don't know where I'm working. Am I in /var/www/zola or /var/www/zola/content and so on...
> Second of all, as zola user, I don't have autocompletion.
> How can I do that?
> Can I create /home/zola and copy in it the .bashcr from the user I connect through ssh and have these feature? Is it enough or should I do something else like relaunch bash or something like that? Or I'm completely wrong and I should do something else?
`Yunohost app shell zola`?
[09:02:40]
<orhtej2> Then `bash` for a good measure
[09:04:09]
<orhtej2> > by reinstalling it via python in the venv...like explain here https://forum.yunohost.org/t/archivebox-cli-commands/30042/2 and with ```pip install --upgrade archivebox``` I had a few issue with files ownership so I solve them with ```root@server:/var/www/archivebox# chown -R archivebox .```
I'm confused why are you not fixing venv from app shell where you would be the proper user already. But yes, you can chown the files, they should be owned by the app
[09:04:59]
<thatoo> > `Yunohost app shell zola`?
I didn't know that one 🤩
[09:07:45]
<orhtej2> > <@thatoo:defis.info> I didn't know that one 🤩
One of the goodies shipped with packaging v2, shoutout to the team ❤️
[09:16:11]
<thatoo> ❤️😍😍😍😍❤️
[10:00:03]
<@chrichri:ween.de> Does anybody here run [Send](https://apps.yunohost.org/app/send) (former Mozilla product)? I didn't find information whether it is possible to protect uploads by a password or by accounts…
[10:06:42]
<@claush:matrix.org> Hi, I just tried to install synapse, but the install script exited with an error. Looks as if there's a problem with fail2ban. Here're the logs: https://paste.yunohost.org/raw/unupuyasiz Has anybody an idea what to do? Thanks in advance!
[10:28:44]
<isAAAc> hello o/
FYI #peertube #upgrade
diagnostic told me yarn.list wasn't ok,
i did `yunohost tools regen-conf apt --force`
peertube_ynh upgrade was quick and ok after that,
i don't know if there was the root cause of the precedent fails
[10:45:24]
<orhtej2> > hello o/
> FYI #peertube #upgrade
> diagnostic told me yarn.list wasn't ok,
> i did `yunohost tools regen-conf apt --force`
> peertube_ynh upgrade was quick and ok after that,
> i don't know if there was the root cause of the precedent fails
Logs?
[11:25:32]
<isAAAc> trying 7.0.1~ynh1 to 7.0.1~ynh2 right now
[11:48:40]
<isAAAc> ended with success version: 7.0.1~ynh2
[11:48:50]
<isAAAc> perfect orhtej2
[11:49:08]
<isAAAc> much more quick than before
[13:19:05]
<centralscrutinizer> Thank to the latest commit by Josue-T in testing branch the installation now goes well
[13:48:17]
<orhtej2> but I did nothing 🤔
[14:19:30]
<thatoo> I have an issue but I'm not sure it is related to ynh.
I have a proxmox server with a ynh VM in it.
ip proxmox server = 192.168.1.23
ip ynh = 192.168.1.24
ip box = 192.168.1.1
I set DNS serveur for proxmox to ip ynh (192.168.1.24) but it doesn't work :
```
root@pve:~# dig domain.tld
;; communications error to 192.168.1.24#53: timed out
;; communications error to 192.168.1.24#53: timed out
^Croot@pve:~ping 192.168.1.24
PING 192.168.1.24 (192.168.1.24) 56(84) bytes of data.
64 bytes from 192.168.1.24: icmp_seq=1 ttl=64 time=0.204 ms
64 bytes from 192.168.1.24: icmp_seq=2 ttl=64 time=0.191 ms
64 bytes from 192.168.1.24: icmp_seq=3 ttl=64 time=0.184 ms
^C
--- 192.168.1.24 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2049ms
rtt min/avg/max/mdev = 0.184/0.193/0.204/0.008 ms
root@pve:~# dig domain.tld
;; communications error to 192.168.1.24#53: timed out
;; communications error to 192.168.1.24#53: timed out
```
If I set DNS to the IP of the box (192.168.1.1), it works.
I check ynh firewall and the port 53 is open (not Upnp).
Where could the issue comes from.
proxmox firewall? but then why would it work with ip of box?
[18:56:28]
<Paprika> I am not sure I understand, but why are you trying to set up DNS for Proxmox to YNH IP? Are you running PiHole on YNH and trying to route your DNS requests through the VM? I really don't follow.
If you simply want to utilize the Proxmox firewall instead of using your router, you are fine as it is - you won't be managing DNS with Proxmox, it will only take care of the traffic. If you want to have a DNS server, you'd either have to set up another CT/VM and get a DHCP/DNS server running, or simply use your router for that.
[18:57:47]
<Paprika> I am not sure I understand, but why are you trying to set up DNS for Proxmox to YNH IP? Are you running PiHole on YNH and trying to route your DNS requests through the VM? I really don't follow.
If you simply want to utilize the Proxmox firewall instead of using your router, you are fine as it is - you won't be managing DNS with Proxmox, it will only take care of the traffic. If you want to have a DNS server, you'd either have to set up another CT/VM and get a DHCP/DNS server running, or simply use your router for that.
If you are setting up a VM and setting the VM's DNS IP to itself (YNH_IP), then you are best off simply using `127.0.0.1` instead of the YNH_IP, that should work. Otherwise, you can use the router IP, which you tried, and it is, I assume, `192.168.1.1`.
[19:03:32]
<Paprika> I am not sure I understand, but why are you trying to set up DNS for Proxmox to YNH IP? Are you running PiHole on YNH and trying to route your DNS requests through the VM? I really don't follow. If that is so, you might be running into firewall issues - it's either proxmox firewall, ynh firewall, or your traffic might be passing through the router as well, no idea what settings you got there.
If you simply want to utilize the Proxmox firewall instead of using your router, you are fine as it is - you won't be managing DNS with Proxmox, it will only take care of the traffic. If you want to have a DNS server, you'd either have to set up another CT/VM and get a DHCP/DNS server running, or simply use your router for that.
If you are setting up a VM and setting the VM's DNS IP to itself (YNH\_IP), then you are best off simply using `127.0.0.1` instead of the YNH\_IP, that should work. Otherwise, you can use the router IP, which you tried, and it is, I assume, `192.168.1.1`.
[19:10:30]
<Paprika> I am not sure I understand, but why are you trying to set up DNS for Proxmox to YNH IP? Are you running PiHole on YNH and trying to route your DNS requests through the VM? I really don't follow. If that is so, you might be running into firewall issues - it's either proxmox firewall, ynh firewall, or your traffic might be passing through the router as well, no idea what settings you got there.
If you simply want to utilize the Proxmox firewall instead of using your router, you are fine as it is - you won't be managing DNS with Proxmox, it will only take care of the traffic. If you want to have a DNS server, you'd either have to set up another CT/VM and get a DHCP/DNS server running, or simply use your router for that.
If you are setting up a VM and setting the VM's DNS IP to itself (`YNH_IP`), then you are best off simply using `127.0.0.1` instead of the `YNH_IP`, that should work. Otherwise, you can use the router IP, which you tried, and it is, I assume, `192.168.1.1`.
**EDIT**: Okay, I may have been confused. I see that you are trying to have YNH act as the DNS server for Proxmox. We can see that your DNS requests are timing out for unknown reasons. If port 53 is open on YNH, it could be your proxmox firewall, so verify the rules that you have set in place.
[19:16:47]
<Paprika> I am not sure I understand, but why are you trying to set up DNS for Proxmox to YNH IP? Are you running PiHole on YNH and trying to route your DNS requests through the VM? I really don't follow. If that is so, you might be running into firewall issues - it's either proxmox firewall, ynh firewall, or your traffic might be passing through the router as well, no idea what settings you got there.
<del>If you simply want to utilize the Proxmox firewall instead of using your router, you are fine as it is - you won't be managing DNS with Proxmox, it will only take care of the traffic. If you want to have a DNS server, you'd either have to set up another CT/VM and get a DHCP/DNS server running, or simply use your router for that.
If you are setting up a VM and setting the VM's DNS IP to itself (`YNH_IP`), then you are best off simply using `127.0.0.1` instead of the `YNH_IP`, that should work. Otherwise, you can use the router IP, which you tried, and it is, I assume, `192.168.1.1`.</del>
**EDIT**: Okay, I may have been confused. I see that you are trying to have YNH act as the DNS server for Proxmox. We can see that your DNS requests are timing out for unknown reasons. If port 53 is open on YNH, it could be your proxmox firewall, so verify the rules that you have set in place.