Why not use Tailscale on each device?
No need to expose any ports, no need for a bastion, no need for any complicated method of retrieving their public IP address, can use ACLs to restrict their access to other devices on the tailnet (if they’re tech-savvy enough to go looking at the tailnet in the first place).
Essentially, as long as they have internet and Tailscale is running, you’ll be able to connect to their device without exposing anything over the internet.
I’m afraid that I’ve never used either Guake or Yakuake so I don’t know either of their feature sets 😁
You could try Yakuake instead of Guake in KDE?
I use Prometheus, Grafana and the proxmox exporter.
Important to note that I run this on a separate machine, not on the proxmox server itself!
Looks like it’s encrypted with ansible-vault
Have you read this? https://tailscale.com/kb/1185/kubernetes
That isn’t a bug, it’s because you haven’t got a display name set against that profile on the accounts home lemmy server (not in sync)
Use the Contrib version of the collector, it has many more receivers, processors and exporters
Node exporter on hosts, OpenTelemetry collector to scrape metrics and collect logs, shipping them to Prometheus and Loki, visualising with Grafana.
Day job is for an observability platform where we heavily encourage the use of (and also contribute) to the OpenTelemetry collector project, hence my use of it.
That is what it means, If the movie in your library is not on one of your lists it will be removed from radarr and the file will be deleted from disk.
I’m glad it helped! As i said, it was all from memory and was a good few years ago, so hopefully it all still applies!
The biggest issue you’re going to have is that the Virgin hubs don’t allow you to change the DNS server that they hand out via DHCP.
By default, Virgin hubs are in ‘Router mode’, this means that they use DHCP to hand out IP addresses, a default gateway address (the hubs own IP address), and DNS server addresses. Typically the DNS server will be the Hub itself and any request sent to the hub will then be forwarded on to the DNS servers that the hub had defined for forward lookup.
Virgin have decided that they know best and don’t allow you to change the DNS servers that they forward your requests to, so you can’t modify the router to point to your PiHole.
There are a couple of options here (and forgive me, I’m doing this from memory as I no longer use virgin):
Disable DHCP (IP addresses management) on the Virgin hub and enable it on the PiHole, if possible. You can then configure the PiHole to hand out the IP addresses for the network, including the PiHole address as the DNS servers (and the Virgin hub as the gateway).
Put the Virgin Hub into ‘modem mode’. This requires you to buy an additional router that will allow you to change the DNS servers to point to your PiHole. Putting the Virgin hub in modem mode basically disables all Router functionality and tells it to only terminate the network connection of the virgin connection, you then connect you new router to the hub (and only your new router) to perform all of the functions required to handle your network. You’ll also need to disable WiFi on the Virgin hub (but I think it may do that automatically in modem mode).
In my opinion, if you can use the method in point 1, that’ll be your easiest and cheapest option, if not, you’re going to have to get a new router.
When I had Virgin (many, many years ago) I went down route 2, but mainly because I wanted more control over my network than Virgin would allow me than with their shitty virgin hubs.
I haven’t, but it looks like I’ve got another exporter to install and dashboard to create 😁
Not a whole lot to be honest. But I work with OpenTelemetry everyday for my day job, so it was a little exercise for me.
Though, OTEL does have some advantages in that It is a vendor agnostic collection tool. allowing you to use multiple different collection methods and switch out your backend easily if you wish.
Prometheus for metrics
Loki for logs
Grafana for dashboards.
I use node exporter for host metrics (Proxmox/VMs/SFFs/RaspPis/Router) and a number of other *exporters:
I use the OpenTelemetry collector to collect some of the above metrics, rather than Prometheus itself, as well as docker logs and other log files before shipping them to Prometheus/Loki.
Oh, I also scrape metrics from my Traefik containers using OTEL as well.
CyberPunk 2077?
Aaannd… Done.
Amazing work @ljdawson@lemmy.world!
No problem, I used Sync everyday, in the before times, can’t wait to see the Lemmy version!
I’m guessing it’s this https://www.emma-sleep.co.uk/