Depending on where you live, going to IT events and conferences to connect to people in person is even more powerful. Ask them about their work and talk passionately about related stuff that you have some knowledge/skill in. Exchange contacts, say you're looking for work.
For example, next month is DEVWORLD in amsterdam. They always give away free tickets close to the start of the event. I'm sure there are a ton more like this around the world.
As for writing applications:
For me writing very high quality applications did the trick.
only apply to companies/positions that you are REALLY interested in
research the position
research the company
if you can find somebody that works there in a similar position, ask them some questions
use the info you gathered to show interest in your appplication
write everything yourself, no AI writing. Be a genuine human.
But you can use AI to give it the position and your application and tell it to make a hiring decision with pro/con arguments and rework it based on that
make a small demo project that shows off your relevant skills and tell them about the challanges you had and what you learned to overcome them
(About the last point: I found that talking about relevant hobby projects I did and showing the code made a huge difference)
It usually takes me about a week to write one such application. But I only sent out 3 before hearing back from 2 of the companies and getting signed on by one.
I know it's a lot more hoops then just clicking "auto apply" or "apply with AI", but the effort pays off.
Contrary to that I often see people complaining online about how they wrote 100 applications in a month and got no job interviews... yeah buddy. (And I was initially one of those people)
Njalla's default TTL for DNS records is 3600 seconds (1 hour). If you just created or modified the A record, it can take up to that full hour for the change to propagate across the internet, which would perfectly explain why Certbot is connecting to the right IP but failing to fetch the file (the request might be hitting an old IP or a cached null response).
Before changing any more configurations, you should verify what the rest of the internet is actually seeing for your domain right now.
Check the current DNS record
You can usedig to see exactly what IP your domain is resolving to, and importantly, the remaining TTL on that record.
From your local machine (or any computer), run:
bash
dig yourdomain.com +noall +answer
This will output something like:
text
yourdomain.com. 3412 IN A 203.0.113.45
The second column (3412) is the remaining TTL in seconds. If that number is counting down from 3600, the record is still propagating. If the IP address shown there doesn't match your server's current public IP, the change hasn't taken effect yet for that DNS server.
Check from a different perspective
To ensure it's not just your local ISP or router cache serving an old record, query an external public DNS server directly:
If these external servers show the correct IP but Certbot still fails, the DNS is fine, and the problem is somewhere in your network routing or web server config. If they show a wrong IP or no record at all, you simply need to wait for the TTL to expire.
and it can use locally run models. But have realistic expectations. If you want it to work well, you need a beefy GPU, a lot of RAM and swap. The "intelligence" is kind of limited if you run low spec models, to the point of it maybe being utterly useless.
not sure if it still works, last commit was 3 years ago (on the other hand, there was no AI vibecoding back then, so thats a plus), but it looks like it might do exactly what you're looking for
there’s prep and glam I like to do or tend to set up but that I would prefer to explicitly set up instead of it being done automaticall
Back in the x11 days I had a script that would take a config file and open multiple programs in a specified arrangement across my displays.
I used KDE activities by task and had such a config for each task. KDE activities can run arbitrary scripts on being started. So when I opened the "work" activity for example, all my work apps would open up in my preffered arrangement. When I opened the gaming activity, steam would start on my side monitor and the main monitor had all of the other gaming related shortcuts on it etc.
Together with the preload daemon or a custom vm-touch (i switched from one to the other at some point) it was blazingly fast and very comfy. (Again, I overprovisioned my RAM so I used it by filling it post boot with a cache of pages that my apps load on startup)
Then wayland came and broke it and I didn't bother to fix it yet.
But everybody has their own prefered workflows, I'm not saying one is better than the other. Just wanted to share.
But just in case you were serious about "We don’t shutdown.":
In my case - clean boot takes 25s. Waking up from hibernation takes over 60 seconds, because of huge RAM. And sleep is broken due to some USB interface shenanigans. Soooo yeaaah, I fully shut down and power on every day.
Oh and btw. by default windows doesn't do a full shutdown, but a sneaky hibernate. You can see that for example if you "shutdown" windows (not reboot.), then power on the pc and boot into linux - trying to access the windows drive, you will see an error that windows "didn't shutdown properly" and is still claiming access to the windows drive. Because it's hibernating and changing content on the drive might break the wakeup.
Should have used agpl if they wanted to be noble.
But this is just a corpo moating strategy.