Give me the all OK if you experience no other problems, as I have seen your screenshot this version is working.
Salute.
Give me the all OK if you experience no other problems, as I have seen your screenshot this version is working.
Salute.
Display MoreOK. Here's what i get:
https://paste.libreelec.tv/mannered-rolf.log
sorry... RPI5 running LE 12.2.1 fresh install and Private Internet Access
Again sorry... RPI5 seems to forget wifi password on reboots. A real PIA not to be confused with my service. Here's the link
Try this one service.wireguard.manager-1.4.6~beta.1. Did you import or fill in username / password?
Salute.
I'd like to test out your work and Thank You. I hoped someone might tackle this issue. I have an RPI5 and 4. Is there any specific LE build I need to use or should this work out of the box on LE12.0.2?
It runs on the stable LibreELEC 12.2 and @deepee runs it on Raspberry Pi 5 and Pi 4 with LibreELEC nightly builds. If you have trouble with it just send debug logs.
Salute.
WireGuard does not depend on OpenSSL so it will not have the same issue with bad CRL certs (as they are not used). If it has issues they will be entirely WireGuard issues.
Wireguard not but PIA with nightly build system is using a very new version of OpenSSL. These newer version strictly enforce web standards (RFC 5280) and instantly drop connections if a Certificate Authority (CA) certificate has formatting flaws. Private Internet Access (PIA) signs their local node handshake API (:1337/addKey) using an internal root certificate that violates this strict new rule (its Basic Constraints are not marked as critical). Stable LibreELEC 12.2.1 is forgiving and ignores this, but the nightly build instantly drops the connection to protect you, resulting in the CERTIFICATE_VERIFY_FAILED crash.
The Wireguard VPN Manager add-on will still try to run a strict, fully verified connection first. However, if it detects that nightly build's strict SSL rules are tripping over PIA's certificate formatting, it will automatically fall back to a bypassed SSL context specifically for that local PIA handshake. This allows the connection to succeed without crashing the get_live_config function in the code.
🚀 [RELEASE] WireGuard VPN Manager v1.4.0 (2026-05-21)
Hello everyone! We are proud to announce the stable release of v1.4.0 for the WireGuard VPN Manager. This update introduces a full multi-provider backend architecture, crucial hardware-specific enhancements for the Raspberry Pi 5, and significant reliability improvements to stop loop crashes.
Special thanks to deepeefor the exhaustive User Acceptance Testing (UAT) on the Raspberry Pi 5 (8GB) and Pi 4 (2GB) under LibreELEC nightly builds!
🔑 Multi-Provider & Custom Backends
⚡ Raspberry Pi 5 & Network Tuning
🛡️ Crash & Loop Prevention
🎨 UI & Code Enhancements
Follow these clean steps to install the manager correctly. Installing via our official repository guarantees you will get automated bug fixes and performance updates immediately.
📦 Step 1: Install the Doemela Repository
⚙️ Step 2: Install WireGuard VPN Manager[/size]
Ready to deploy? Grab the master repository installer directly from our package hub:
📥 Download Doemela Repo ZIP Installer
If you notice any unexpected errors or timing glitches on your device layout, please run a quick terminal check.
The command below filters your log file to capture only our add-on's tags, uploads it instantly, and generates a short shareable URL. Run this single command in your LibreELEC terminal:
What happens: It pushes the filtered data straight to LibreELEC's default pastebin server and prints a clean link right inside your terminal window. Please share that link directly in this thread. Do not post full raw logs here!
📘 VPN Provider Integration Policy
This page outlines the strict technical standards required for adding new VPN provider integrations into the WireGuard Manager addon.
To keep this open-source project maintainable, fast, and free of architectural clutter, new provider integrations will only be considered if their backend infrastructure meets modern, clean development standards (like NordVPN).
If a provider relies on messy, multi-layered, or dynamic handshake mechanisms, it will be rejected automatically.
🟢 What We Accept (The "Good Stuff")
We look for clean, predictable, and standard implementations. A provider will be considered if it features:
🔴 What We Reject (The "Grief Standards")
We will not spend days reverse-engineering closed, broken, or undocumented backend platforms. A provider is automatically disqualified if it uses:
📥 How to Request a New Provider
If your desired provider meets all the green-lit requirements above:
Requests that do not include working public documentation links or are missing the verified checklist will be closed automatically to keep repository history clean.
For any mod can the title of the thread WireGuard Manager for NordVPN be changed to "WireGuard VPN Manager"? If not please remove thread so that I can make a new thread.
Salute.
Great work, thank you.
I've been hoping for something that would fill the gap left by the discontinued development of VPN Manager For OpenVPN.
However, my use case would be for PIA.
Any plans for a PIA (or other) variant, or tips to apply their tokens within your program structure?
Nothing planned, but it was in my head somebody would... will look into it, but I say this I will only do this kinda options, requests if the API of provider is public. Give me some time to get this ready for multi VPN providers I will contact you if I need anything to debug this like a token..., ... or if you capable you could debug a non-public version.
A lightweight, high-performance Kodi service add-on for LibreELEC 12+ (Kodi 21 Omega). This tool manages WireGuard connections natively via connmanctl, providing a faster and more stable experience than traditional OpenVPN-based add-ons.
If you already know what you're doing, grab the repository installer here:
📦 Download Doemela Repo ZIP
QuoteTip: Installing via the Repository is the recommended method. It ensures you receive automatic updates for bug fixes and new Raspberry Pi 5 performance optimizations as soon as they are released.
Already included in nightlies. https://github.com/LibreELEC/LibreELEC.tv/pull/9048
That was an easy answer but does not solve a critical vulnerability you have in the stable releases that majority of people use. Security wise, this is a very bad policy, the worst!
OpenSSH resolves a critical vulnerability (CVE-2024-6387)that enables remote code execution. The vulnerability affects versions 8.5p1 through 9.7p1. As LibreELEC 12.0 uses OpenSSH version "OpenSSH_9.7p1, OpenSSL 3.2.1 30 Jan 2024" can it be updated? If not, in the meantime, you can mitigate the vulnerability by assigning the value 0 to LoginGraceTime in /etc/ssh/sshd_config. This causes a temporary denial-of-service that prevents code execution.