Can you post some hardware specs? In general, the local client is going to use similar resources as a browser session since it’s just a repacking of the same software in most cases unless it’s horribly handled. Slack comes to mind in this instance.

Some details about what the actual issues are might be helpful as well.

I really think you have conflicting resolvers running on startup, which would explain this. Double check your systemd units that are enabled on boot. If you don’t see anything like networkmanager, reboot the machine, get the status of systemd-resolv to make sure it’s actually running after a fresh boot, check the logs and see if you see anything interesting there, then restart it and check the logs again once DNS works. Something is different between those two actions.

See if this helps at all:

sudo systemctl revert systemd-resolved
sudo systemctl restart systemd-resolved

Also, what does ls -lh /etc/resolv* show?

What’s happening in journalctl -u systemd-resolved?

Well only your DNS is broken, so that’s all that needs to get fixed. Are you POSITIVE you’re using systemd resolve and not networkmanager?

1. Check if the CPU is overheating. You didn’t mention anything about cooling.
2. Are you sure your installed RAM is frequency compatible with the new CPU?

Did you insert the sysctl values and reboot?

Revert and see if it’s faster on the previous version.

Yes, PSK will work.

No

No

Add it to /etc/fstab. Tons of guides everywhere online.

It’s an open source project, so have at it!

Are you using ZHA, or another coordinator?

No, it can just affect the boot record in some cases. This is not that case.

• Can’t find anything: everything is meant to be searchable in lieu of having a programs menu and such. Hit your meta key (Winkey) and start typing to find or launch something, use URL bar in your file manager to search for names or content of files…etc. You can also just set icons for things if you wish.
• Instability: there is almost zero chance of you being able to destroy your environment so bad that it would require a reinstall of the OS. Since it’s just flat files on a disk and no central registry like Windows, everything can be repaired quite simply, you just need to be familiar with how.
• Capslock: unfamiliar with your intended behavior as I’ve never used Capslock like that before, but I bet there is a solution for this if you just search around. Input behavior is totally customizable.
• Desktop icons: no idea what that could be, but as mentioned above, most DE’s have or are moving away from desktop as a launch source.
• Firefox: ‘about:config’ has these settings
• Software center is just one GUI for finding things. You can install whatever you want however you want, and that’s just up to you. If you find some piece of something you want to run, the preferred method is also using a package for your OS’s package manager, but that’s just for convenience and not a hard rule. There is no “best” solution, just good habits.

Good luck!

HA on your private network. Tailscale or Wireguard into that network. Problem solved.

It’s all errors. Address them.

Don’t look at the browser, look at the service logs. Turn on debug if needed. You’re only seeing one side of the conversation.

Yeah, but you have a wildcard in your caddy file. Does your SSL cert respond to wildcard requests? One of these services logs has the real issue logged.