Posts by Doemela

To change the NTP server using the LibreELEC user interface, you need to use the LibreELEC Settings Add-on inside Kodi. Here are the step-by-step instructions:

1. Open LibreELEC Settings:
   • From the Kodi main menu, navigate to Settings (the gear icon at the top left).
   • Click on LibreELEC (usually located at the bottom or under the system category).
2. Navigate to the Network Tab:
   • Scroll down the left-hand menu and select Network.
3. Change the Timeserver:
   • On the right side, scroll down to the Network Services section.
   • Click on Timeserver #1 (or Timeserver #2/3 if you want backups).
   • A virtual keyboard will pop up.
   • You will see three slots available:
     1. Timeserver #1: 0.pool.ntp.org (or pool.ntp.org)
     2. Timeserver #2: 1.pool.ntp.org
     3. Timeserver #3: 2.pool.ntp.org
   • Click OK or Done.
4. Save and Apply:
   • The system will automatically save the changes and attempt to sync the time using the new server.

Salute.

Connect via SSH to your LibreELEC device. Run the following command to check the current time:

date

If the date shown is in the past try forcing an NTP sync:

ntpd -q -p pool.ntp.org

Hello rivmar

I can see the issue you're encountering. The error curl: (60) SSL certificate problem: certificate is not yet valid indicates that your LibreELEC device's system clock is likely incorrect (set to a date in the past), causing pastebinit (which uses curl) to fail when trying to verify the SSL certificate of the paste service.

Here is how to fix this and successfully get your log URL:

LibreELEC devices often lose time if they don't have NTP configured correctly.

1. Connect via SSH to your LibreELEC device.

2. Run the following command to check the current time:

   Shell session

   date

3. If the date shown is in the past, this confirms the issue.
4. Adjust the date/time to match your actual current time forcing an NTP sync:

ntpd -q -p pool.ntp.org

Once the time is corrected, try running the grep command again:

grep -i "service.wireguard.manager" /storage/.kodi/temp/kodi.log | pastebinit

Let me know if fixing the time resolves the pastebinit error, or feel free to do this:

cat ~/.kodi/temp/kodi.log | grep -iE "service.wireguard.manager" | nc termbin.com 9999

Termbin does not use HTTPS — it runs over a plain TCP connection on port 9999 via netcat. Therefore, no SSL certificate verification is required, which completely bypasses the error ‘curl: (60) certificate is not yet valid’. The error message “certificate is not yet valid” almost certainly indicates that the system clock on the device is incorrect. This doesn’t matter for Termbin, but it’s still a good idea to check it using the `date` command, as an incorrect clock can also cause problems with other HTTPS connections.

Salute.

Quote from rivmar

Hi, I have Librelec and installed Wireguard Manager 1.5.3. I'd like to activate it with Proton. I downloaded the file .conf and renamed it .config. I added it to IMPORT Config. Everything is fine. When I click on Wireguard, it tries to connect but fails. This is the file:

Code

[provider_wireguard]
Type = WireGuard
Name = Custom_Proton_CH
Host = 138.199.6.178
DNS = 10.2.0.1, 2a07:b944::2:1
WireGuard.Address = 10.2.0.2/32, 2a07:b944::2:2/128
WireGuard.ListenPort = 51820
WireGuard.MTU = 1420
WireGuard.PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
#CH-FREE#3
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
WireGuard.AllowedIPs = 0.0.0.0/0, ::/0
WireGuard.EndpointPort = 138.199.6.178:51820
WireGuard.PersistentKeepalive = 25

Display More

Can someone help me understand what I'm doing wrong? Thanks in advance.

Try this config:

[provider_wireguard]
Type = WireGuard
Name = Custom_Proton_CH
Host = 138.199.6.178
DNS = 10.2.0.1
WireGuard.Address = 10.2.0.2/32
WireGuard.ListenPort = 51820
WireGuard.MTU = 1420
WireGuard.PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
#CH-FREE#3
PublicKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
WireGuard.AllowedIPs = 0.0.0.0/0, ::/0
WireGuard.EndpointPort = 51820
WireGuard.PersistentKeepalive = 25

I need to see the log if it still fails. To post logs to this forum, copy and paste the following into SSH:

grep -i "service.wireguard.manager" /storage/.kodi/temp/kodi.log | pastebinit

And post that URL here. How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)
5. Use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

Also read our wiki https://github.com/BrodjagaRatnik…rd.manager/wiki

Salute.

Quote from Reddirt

Ahem. I vaguely recall this issue during early beta tests or am I dreaming it?

Could be, at boot connman-vpnd caught PIA wireguard config file mid-write ("does not contain any configuration that can be provisioned!"), creating a half-second window where both the addon and the LibreELEC settings service were racing for connman resources. On some specific hardware that window caused the permanent hang.

Two fixes are now in place for next v1.5.4:

1. Cold boot connect gate — automatic VPN provisioning waits for a platform-specific settle time after service start before triggering the connection. This removes the startup overlap entirely.
2. Atomic config writes (PIA only) — WireGuard configs are now written via temp-file + atomic rename. connman-vpnd will never see a truncated/empty file again, eliminating the "not provisionable" error.

Quote from giddyup69

Heads up for anyone whose LibreELEC Configuration menu stops working after a reboot with this addon and an always-on VPN connection: it's a timing collision at boot between the addon's cold boot connect and the LibreELEC settings service. Restarting Kodi works around it. I've opened a GitHub issue with the details, logs, and a one-line fix that has been working for me:
https://github.com/BrodjagaRatnik…anager/issues/9

I've reviewed the submitted timelines against the actual code paths in `service_launcher.py` and `vpn_connector.py`, and they don't hold up — e.g. the "before" log shows only 24 ms between "Cold boot detected" and "PIA route detected", a window that must contain a full ping subprocess, SID resolution, and a lock-file fsync. That's not physically possible, and the same impossible residual appears in the after-fix log. Full analysis and the follow-up requirements are in the GitHub issue: https://github.com/BrodjagaRatnik…anager/issues/9

"Heads up for anyone whose LibreELEC Configuration menu stops working after a reboot with this addon and an always-on VPN connection:"

There is also no code path that could cause it. The addon never touches `service.libreelec.settings` — it neither stops, disables, nor communicates with it. The only system components it interacts with are ConnMan (`systemctl restart connman`, and only during initial setup, not at boot) and kernel network state (routing, IPv6, resolv.conf). The settings service talks to ConnMan over DBus.

Salute.

Quote from chewitt

In the v7 submission everything below the first paragraph should have been placed under the --- separator so that it is visible to reviewers but not merged into the codebase along with the description.

I normally place things above --- during development so that testing commentary is easily edited and not forgotten, but then you need to remember to tweak the final patch files before sending to move the --- above it.

Ty v8 submitted with the commentary moved below the separator.

Maybe Audio Profiles - Easy switch between different audio settings Audio Profiles is an option.

Installation Steps

• Go to the main Kodi Settings menu (gear icon).
• Select Add-ons.
• Click Install from repository.
• Choose Program Add-ons.
• Find and select Audio Profiles.
• Click Install at the bottom right.

Saluti.

UPDATE 2026-09-20: Fixed — patch submitted upstream

Confirmed the leak on stock LE13 nightly 20260920-b68ee23 (ConnMan 2.0, iwd backend, Generic x86_64): fd count 22 → 49+ over VPN cycles, never recovers. Root cause in plugins/wifi.c interface_removed() — early-return skips g_supplicant_interface_cancel().

Patch (v7) submitted to [email protected]. With patch applied: fd returns to baseline (22) after every cycle. Verified data + fix instructions: Upstream ConnMan FD Leak Automated Mitigation Guide

Quote from Ironman9001

Thank you for the responses, I'm afraid it turned out to be a problem with inexperience with Kodi. I've now got it working as expected.

But when adjusting settings in Kodi, it seems that different pages behave differently when it comes to when the changes are saved. Also sometimes there seems to be a considerable lag between when you press a button (I've been using Kore) and the interface presents you with the options, so that an inexperienced user might think that it was dead button and moved on to explore what other ways there are to achieve the changes he wants.

Np, some buttons take a long time, like updating the servers, because it has to access several servers in each country for its database. If you select several countries, it can mean downloading tens of servers. This will be fixed in a future version(s), so you will get a progress window.

Salute!

Quote from Ironman9001

Hi, a new user here. I just installed latest and greatest of LibreELEC and among the first add-ons service.wireguard.manager from the Doemela repo. As I already have Mullvad vpn on another device I used the same account in LibreELEC and got it up and running without much trouble.

But there are two things that baffle me, it doesn't connect at boot, that is I have to always establish the vpn connection manually after a reboot. Secondly it doesn't seem to have registered that I only want a specific country to show up when selecting the vpn connection. My selected country is there in the config, but I am always given a list that starts with Albania when connecting the vpn.

Regarding: "My selected country is there in the config, but I am always given a list that starts with Albania when connecting the vpn." Did you save the settings after selecting the countr(y|ies) as the addon told you?

I need to see the log. To post logs to this forum, copy and paste the following into SSH:

1. Shell session

   grep -i "service.wireguard.manager" /storage/.kodi/temp/kodi.log | pastebinit

2. And post that URL here.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>LoggingRestart Kodi
2. Replicate the problem
3. Generate a log URL (do not post/upload logs to the forum)
4. Use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

Also read the Settings Explained on our wiki.

Salute.

iPlayer WWW works for me on LibreElec generic 12+ also on my LibreElec generic 13

To help other community members check if their systems are suffering from this ConnMan file descriptor leak, I have written a diagnostic script. Connect via SSH and create the script:

mkdir -p /storage/.config/scripts
nano /storage/.config/scripts/connman-leak-test.sh

Paste the following code inside the file:

#!/bin/sh
# chmod +x /storage/.config/scripts/connman-leak-test.sh
# /storage/.config/scripts/connman-leak-test.sh

OUTDIR=/storage/.cache/connman-diagnostics-$(date +%Y%m%dT%H%M%S)
mkdir -p "$OUTDIR"
PASTE_LOG="$OUTDIR/connman-leak-test.txt"

trap 'echo -e "\n[$(date +%H:%M:%S)] Execution interrupted by user! Jumping to final metrics collection..."; break' INT

echo "=== CONNMAN DIAGNOSTICS (PASSIVE MONITOR) ===" > "$PASTE_LOG"
echo "OS: $(cat /etc/os-release | grep PRETTY_NAME | cut -d'"' -f2)" >> "$PASTE_LOG"
echo "Kernel: $(uname -r)" >> "$PASTE_LOG"
if [ -f /proc/device-tree/model ]; then
  echo "Hardware Model: $(cat /proc/device-tree/model)" >> "$PASTE_LOG"
fi
echo "----------------------------------------" >> "$PASTE_LOG"

pid=$(pidof connmand)
echo "Connmand PID: $pid" >> "$PASTE_LOG"

echo "[$(date +%H:%M:%S)] Toggling Kodi component debug logging ON..."
kodi-send --action="SetLogLevel(2)" >/dev/null 2>&1 || true

echo "[$(date +%H:%M:%S)] Collecting FIRST snapshot (T=0)..."
echo "=== SNAPSHOT 1: START ===" >> "$PASTE_LOG"
echo "Timestamp: $(date)" >> "$PASTE_LOG"
if [ -n "$pid" ]; then
  echo "FD count: $(ls -l /proc/$pid/fd 2>/dev/null | wc -l)" >> "$PASTE_LOG"
  echo "Active FD targets (Top 20):" >> "$PASTE_LOG"
  (for f in /proc/$pid/fd/*; do readlink -f "$f" 2>/dev/null || readlink "$f" 2>/dev/null; done ) | sort | uniq -c | sort -nr | head -n 20 >> "$PASTE_LOG" 2>&1 || true
fi
echo "----------------------------------------" >> "$PASTE_LOG"

echo "[$(date +%H:%M:%S)] Sleeping for 30 minutes to let the leak accumulate..."
echo "Press Ctrl+C at any time to skip the wait and generate the log immediately."

for i in $(seq 1 1800); do
  sleep 1
done

trap - INT

echo "[$(date +%H:%M:%S)] Collecting SECOND snapshot (T=+30 min)..."
echo -e "\n=== SNAPSHOT 2: AFTER 30 MIN ===" >> "$PASTE_LOG"
echo "Timestamp: $(date)" >> "$PASTE_LOG"
if [ -n "$pid" ]; then
  echo "FD count: $(ls -l /proc/$pid/fd 2>/dev/null | wc -l)" >> "$PASTE_LOG"
  echo "Active FD targets (Top 20):" >> "$PASTE_LOG"
  (for f in /proc/$pid/fd/*; do readlink -f "$f" 2>/dev/null || readlink "$f" 2>/dev/null; done ) | sort | uniq -c | sort -nr | head -n 20 >> "$PASTE_LOG" 2>&1 || true
  
  if [ -r /proc/net/netlink ]; then
    echo -e "\n=== /proc/net/netlink ===" >> "$PASTE_LOG"
    cat /proc/net/netlink >> "$PASTE_LOG"
  fi
fi

echo -e "\n=== RECENT KODI LOG ENTRIES FOR ADDON ===" >> "$PASTE_LOG"
if [ -f /storage/.kodi/temp/kodi.log ]; then
  grep -Ei "connman|wireguard" /storage/.kodi/temp/kodi.log | tail -n 150 >> "$PASTE_LOG" 2>&1 || true
fi

echo -e "\n=== RECENT SYSTEM JOURNAL LOGS FOR CONNMAN ===" >> "$PASTE_LOG"
journalctl -u connman.service -n 150 --no-pager >> "$PASTE_LOG" 2>&1 || true

echo "[$(date +%H:%M:%S)] Toggling Kodi component debug logging OFF..."
kodi-send --action="SetLogLevel(0)" >/dev/null 2>&1 || true

echo "----------------------------------------"
echo "Uploading results..."

PASTE_URL=""
if command -v paste >/dev/null 2>&1; then
  PASTE_URL=$(paste "$PASTE_LOG" 2>/dev/null)
fi

if [ -z "$PASTE_URL" ]; then
  echo "Deploying curl fallback to ix.io..."
  PASTE_URL=$(curl -s -F "f:1=@$PASTE_LOG" ix.io)
fi

if [ -n "$PASTE_URL" ]; then
  echo "----------------------------------------"
  echo "Your diagnostic paste link is:"
  echo "$PASTE_URL"
  echo "----------------------------------------"
else
  echo "Upload failed. Log preserved locally at: $PASTE_LOG"
fi

Save and exit (Ctrl+O, Enter, Ctrl+X), then give it execution permissions and run it:

chmod +x /storage/.config/scripts/connman-leak-test.sh
/storage/.config/scripts/connman-leak-test.sh

If you let it run full course or interrupt it, it will provide a direct paste link showing if your system is experiencing un-canceled socket tracking build-ups.

Quote from Da Flex

Good luck!

[v6] plugins/wifi: Fix GSupplicantInterface socket leak during teardown - Patchwork

Quote from chewitt

To the original question: I'd prefer to see the patch merged and package bumped than place 'known bug' info in the wiki.

I completely understand your point regarding LE13+ and preferring a package bump once the patch is merged upstream.

However, my main concern is for users on LE11 and LE12. Since those legacy versions are in maintenance mode and likely won't receive a core ConnMan package update, they will continue to hit this 1024 fd crash. To give you a real-world example of why this is urgent for legacy LE11/LE12: in a standard dual-setup where Ethernet is active and Wi-Fi is left floating on 'idle' or 'ready', ConnMan triggers this background scan-loop constantly. The file descriptors stack up in record time without even touching VPNs/WireGuard. It affects anyone running hybrid wired/wireless setups from day one.

How would you prefer we handle this for legacy releases? Would it be acceptable to post a brief workaround/troubleshooting note in the forum for them (e.g., using a systemd/cron timer to periodically flush ConnMan before it hits the 1024 fd limit)?

On a side note, I just submitted [PATCH v6] upstream to the ConnMan mailing list. I believe I have now cleaned up all the formatting issues and the stray line-deletes to meet the strict Linux ecosystem style guidelines—or at least I hope so, but you would know better than me!

Is it a good idea to mention this bug in the wiki and explain it, so that current and previous versions of LibreELEC can work around the Connmanleak in Wi-Fi until Connman fixes it in a later version?

Quote from userx404

Thank you for your suggestion
I tried the addon but am not shure how to use it and how to switch. If i click on the addon in the overview, i see my 2 created profiles in a selection menu. When i select one, the actual settings get saved to this profile. But i want to switch this profile.

You can switch between profiles using key map see https://kodi.wiki/view/Add-on:Audio_Profiles https://forum.kodi.tv/showthread.php?tid=353852

The only solution I can think of to bypass DHCP is a small background script to bypass it. Create a file named autostart.sh for your sister and send it to her. Here is the exact code needed. Copy this block of text:

#!/bin/sh
(
 # Wait until the system creates the network file
 while [ ! -f /run/libreelec/resolv.conf ]; do
   sleep 1
 done
 # Give the system 2 extra seconds to finish writing
 sleep 2
 
 # Wipe out the broken settings and force universal DNS
 echo "nameserver 1.1.1.1" > /run/libreelec/resolv.conf
 echo "nameserver 8.8.8.8" >> /run/libreelec/resolv.conf
) &

Instructions for your Sister. To install this script, you will need a computer connected to the same home network as the LibreELEC device.

• Open File Explorer on your computer.
• In the address bar at the very top, type your LibreELEC network path and press Enter:
  \\YOUR_LIBREELEC_IP_ADDRESS\ (Example: \\192.168.1.15\)
• Open the Configfiles folder.
• If you cannot see it, enable "Hidden items" in the View settings of Windows.
• Copy autostart.sh to that Config folder.
• Restart LibreELEC.