Yes a VPN could solve it. Run the VPN on a domain you know is good and on port 443 HTTPS.

Im not sure I understand your issue, DNS is the magic that allows you to goto home.somedomain.com and get a webpage. But you still need to give DNS the location of the server, much like the contacts in your phone.

DDNS is how you have your home connection attached to a DNS record that is updated when the IP changes, see other comments.

Also once you understand how it all hangs together, you can do some really cool magic to make getting to your services easier

Can confirm that zigbee is much better for IOT things, I find the zigbee stuff is quicker to react to events as there is not WiFI setup. Some WiFi devices running on batterys will have lag while they get WiFi link back up.

Oh, not sure where I got glow from. Will have a look.

Pulsar is a fork of atom and is in active development, it can still be a little slow sometimes. But is now getting updates to make it run better

Edit: this https://github.com/charmbracelet/glow

I use pulsar edit, the successor to atom. Also on the terminal, have a look at glow.

First off, backups of the configs any user data that you can’t torrent should the inevitable happen.

Then set time aside to do updates, I spend Wednesday evenings updating and improving my setup.

Then find a way to track update announcements, I use both an RSS reader and newrealeases.io to know when something I run gets an update

What I can tell you, working for a company hosting data for the UK NHS.

Is that hosting is easy, I have a very reliable homelab. I keep things up to date and make sure to secure things the best I can.

But security is hard, there are many things to secure. Blind spots you didn’t even know you had.

The bast way to look at security, it to start with secure and dial things back so that it works.

With let’s encrypt and DNS APIs, theres no excuse not to have a real certificate!

More so if you want to have that service interacte with other systems not your own

Yes you can use lemmy apps to access a self hosted instance, but you will need a real certificate for that to work.

A quick check of Lemmy.rip show it has a self signed certificate, thats not going to allow you to access it easily and my even stop federation from working.

You should be able to get a lets encrypt certificate very easily.

I have my home assistant check and also my nagios, better safe then sorry

no, just no

Oh no, anyway have you seen ducksuckgo?

Or a git repo and ansible/semaphore, thats how I manage my docker services. I have a git repo with all my configs and compose files (not in github, but my own server), then in semaphore I have a playbook to update a compose or swarm stack.

Having been in company at sales time my self, I can tell you that management will say all sorts of things. But once the sale completes the new owners can do anything, that could be drop all the staff.

I my self also loved the pebble, till it all died. I did try repebble. But the android app was way past it then.

My hope is that the mobile apps get a much needed update, then all the working watches get a firmware update. If that happens, I might have to get my working watch out and setup.

What you have missed is the ability to run what ever you need, self hosting is more then just backups and sync.

Some self hosting to self reliant, nextcloud can do way more then just file sync. For example I use it for calendar and contact sync, photo and file backup from my phone, an office suit, RSS server.

I have time on a Wednesday to run updates on all the things, I also have notifications about changes to software I run.

Your very welcome

I see, my guess is that the path is in an nginx file somewhere. Could be the fpm config, but unlikely.

Nextcloud will look in the root of the nextcloud install for config/config.php

So unless you have been hacking the code, I think it’s nginx config

I can see the error log file, that has a very odd path in it. How are you running php?

Apache module or fpm?

Can you give a screenshot of the error?