How to Auto-Renew Tailscale HTTPS Certificates on PiKVM Using systemd

·1 views

PiKVM users running Tailscale for remote access must manually handle HTTPS certificate renewals, as certificates obtained via 'tailscale cert' are not automatically renewed. A community-developed solution uses a systemd timer that runs daily to check whether the current certificate matches the device's Tailscale FQDN and has at least 30 days of validity remaining. If renewal is needed, the script temporarily switches PiKVM's read-only filesystem to read-write, fetches a fresh certificate using the '--min-validity=720h' flag, and replaces the nginx SSL files before restoring the filesystem to read-only. The approach aligns with official PiKVM documentation, which recommends placing Tailscale certificates in '/etc/kvmd/nginx/ssl/' and restarting the kvmd-nginx service after updates. Since Let's Encrypt certificates are valid for 90 days, triggering renewal at the 30-day mark provides a comfortable buffer against expiration.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Go Experiment Links pprof CPU Profiles to OpenTelemetry Traces via OTLP

A developer experiment demonstrates how to connect Go's built-in pprof CPU profiling data to OpenTelemetry trace and span IDs using the OTLP Profiles format. The approach embeds trace and span IDs as pprof labels during request handling, then converts the profiling data into OTLP Profiles for export. The pipeline routes traces to Grafana Tempo and CPU profiles to Pyroscope, allowing engineers to navigate from a slow HTTP span directly to a flame graph of the functions that ran during it. The lab uses specific component versions including OpenTelemetry Collector 0.158.0, Pyroscope 2.2.0, and Grafana 13.1.2, and is published in a public GitHub repository. The authors caution that OpenTelemetry Profiles is still an evolving standard, so compatibility must be re-verified as versions change.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Git Version Control: A Complete Guide for Developers and Beginners

Git is a Distributed Version Control System created in 2005 to support Linux Kernel development, designed to track code changes across projects of any size. It allows developers to record project history, revert to previous states, and collaborate simultaneously without overwriting each other's work. Key concepts include the Working Directory, Staging Area, and Repository, which together form Git's three-stage workflow for managing code changes. Git and GitHub are distinct tools — Git is the version control software itself, while GitHub is an online platform for hosting Git repositories. The guide covers essential commands and concepts such as branching, merging, merge conflicts, and advanced operations like rebase and cherry-pick, aimed at helping beginners build a practical Git workflow.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Local AI Voice Model Struggles With Part Numbers in Industrial German Text

A developer tested Qwen3-TTS, a 1.7B parameter open-source text-to-speech model, on 40 German sentences typical of industrial and workshop documentation, including part numbers, acronyms, dates, and currency figures. Running locally on Apple Silicon via the MLX framework, the model derailed on 3 of 40 sentences in raw mode, silently producing 20 seconds of fluent but unrelated German with no error or warning. Adding a text rewrite layer ahead of the model eliminated all derailments on unseen test sentences, though identifier accuracy remained low at 2 out of 7. Amazon Polly handled the same raw sentences without any derailments or preprocessing rules, making it the more reliable choice for most use cases. The developer concluded local synthesis is worth considering only for strict data residency, air-gapped environments, or high-volume cost savings, given the added maintenance burden of a rewrite layer.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Closes July 2026 With 24 WordPress Pull Requests Across 9 Repos

A developer contributed 24 pull requests across 9 WordPress repositories during July 2026, with WooCommerce accounting for the largest share at 10 merged PRs. A key fix addressed a log cleanup bug where WooCommerce's daily cron job deleted only 20 expired log files per run due to a missing pagination parameter, leaving excess files stranded indefinitely. Another fix corrected stale order counts in the admin panel caused by a cache shortcut that ignored custom query filters added by plugins. The most complex contribution replaced six separate REST API calls per page load with a single combined endpoint, reducing unnecessary network overhead for the WooCommerce Activity Panel and homescreen widget. The developer shared full code diffs for each change to help others understand the context and impact of each fix.

0 comments Read more at DEV Community