Tywele

joined 2 years ago
[–] Tywele@lemmy.dbzer0.com 2 points 1 week ago

To my knowledge wireless charging is harder on the battery because of the heat it produces.

[–] Tywele@lemmy.dbzer0.com 1 points 1 week ago (2 children)

What did you actually gain here? With my Pixel 7 it looks almost the same with 3.1% capacity loss per year without taking any special care of my battery. Is my phone an outlier or does it just not matter? And I almost exclusively charge with wireless.

[–] Tywele@lemmy.dbzer0.com 8 points 1 month ago

Or like something that got typed by that same college freshman by falling asleep and hitting their head on the keyboard.

[–] Tywele@lemmy.dbzer0.com 36 points 1 month ago (2 children)

What is it with open source projects and their awful names?

[–] Tywele@lemmy.dbzer0.com 1 points 1 month ago* (last edited 1 month ago)

Good news, they are doing just that (in cooperation with Ecosia)

Edit: And it is supposed to be released this year (as early as Q1 apparently) https://betterweb.qwant.com/en/2024/11/08/ecosia-and-qwant-join-forces-to-develop-european-search-index/

1
submitted 7 months ago* (last edited 7 months ago) by Tywele@lemmy.dbzer0.com to c/selfhosted@lemmy.world
 

Solution: I just had to create the file

I wanted to install Pi-Hole on my server and noticed that port 53 is already in use by something.

Apparently it is in use by systemd-resolved:

~$ sudo lsof -i -P -n | grep LISTEN
[...]
systemd-r    799 systemd-resolve   18u  IPv4   7018      0t0  TCP 127.0.0.53:53 (LISTEN)
systemd-r    799 systemd-resolve   20u  IPv4   7020      0t0  TCP 127.0.0.54:53 (LISTEN)
[...]

And the solution should be to edit /etc/systemd/resolved.conf by changing #DNSStubListener=yes to DNSStubListener=no according to this post I found. But the /etc/systemd/resolved.conf doesn't exist on my server.

I've tried sudo dnf install /etc/systemd/resolved.conf which did nothing other than telling me that systemd-resolved is already installed of course. Rebooting also didn't work. I don't know what else I could try.

I'm running Fedora Server.

Is there another way to stop systemd-resolved from listening on port 53? If not how do I fix my missing .conf file?

 

I'm a beginner in networking things but due to my ISP I can only open a certain range of ports in my router to be accessible from the outside of my network (something like ports 11000-11500).

That means I can't open port 443 to access my reverse proxy from the outside. Is it possible to redirect all traffic that's coming from one of the ports in the range to port 443 of my server?

I haven't found that possibility in my router (Fritzbox 7530) so is there a way to do this on my server (running Fedora Server)?