WireGuard VPN Manager

RapidRapunzel This wireguard config will do the trick:

[provider_wireguard]
Type = WireGuard
Name = Custom_Usa
Host = 23.234.116.3
WireGuard.Address = 10.70.70.181/32
WireGuard.ListenPort = 51820
WireGuard.MTU = 1420
WireGuard.PrivateKey = xxx
WireGuard.PublicKey = xxx
WireGuard.DNS = 100.64.0.63, 100.64.0.7
WireGuard.AllowedIPs = 0.0.0.0/0, ::/0
WireGuard.EndpointPort = 51820
WireGuard.PersistentKeepalive = 25

I am busy integrating Mullvad into version 1.5.3. You can try out this beta version in the meantime. https://github.com/BrodjagaRatnik….5.3~Beta.2.zip

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)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

Salute.

Quote from RapidRapunzel

You're awesome, I just install the 1.5.3 beta 2 and it worked perfect

Please note that this is a beta version. View the settings for this VPN provider in the add-on, then provide me with feedback. Run it for a couple of days, and if you encounter any problems, send me the log.

Saluti.

Yes, I used the Mullvads DNS servers from the blocklist, with beta.3 I set the unblocked and unfiltered DNS of Mullvad. https://github.com/BrodjagaRatnik….5.3~Beta.3.zip

Saluti.

Quote from chaosen3

Doemela I use the script from https://github.com/pia-foss/manual-connections to manually generate wireguard config files using my PIA dedicated token, is it a chore to build support for it into your add-on?

The integration of PIA into WireGuard VPN Manager is indeed based on that exact script https://github.com/pia-foss/manua…d_with_token.sh . In the add-on settings under 'VPN provider', you enter your username and password. The add-on after selecting countries/regions then automatically generates the WireGuard files in ~/.config/wireguard. https://github.com/BrodjagaRatnik…tings-Explained

Please note that it refreshes the standard session token only when it connects or updates in add-on. The update interval can be set in the hours settings. If you are not connected, it will refresh every hour (or whatever interval you choose). You can use it this way for now.

However, it does not officially support the 'PIA dedicated token' feature yet. In the meantime, I will look into adding a PIA authentication option specifically for dedicated tokens. I have looked into the script logic for the 'PIA dedicated token' and noticed it bypasses the standard user/password auth by using the token as a basic auth username. Since my add-on manages many other platform-specific tasks (like ConnMan routing and firewalls for LibreELEC), I will need to design a specific settings layout to let you input your dedicated IP, hostname, and token safely. I will look into adding this dedicated auth option in a future update!

Salute.

chaosen3 Before I look into building support for this standalone dedicated auth path, I want to make sure I design the logic correctly for your specific setup. I actually already wrote some alpha code for it! However, to save myself the headache and grief of a massive backend rewrite, I want to double-check how you plan to use it.

Jumping into the full add-on service means my background loops—like the connection watchdog, update crons, and ConnMan deadlocks—will constantly try to rotate tokens and ping public server lists. For a dedicated IP, I will have to build a lot of special overrides to tell the service: 'Stop, do not touch this connection, it is static!'

To be completely transparent: this add-on was born out of my own personal needs. While I love open-source and sharing my work for free, my time is limited. I have my own job, bills to pay, and a life outside of coding. I am happy to help up to a certain point, but I cannot do massive, time-consuming backend overhauls for free.

Could you tell me a bit more about your exact goal?

1. Full Integration: Do you want the add-on to fully manage the dedicated connection on the background (handling ConnMan routing, automatic firewall rules, and keeping the tunnel alive)?
2. Standalone WireGuard Config Generator Manager: Alternatively, I could pull the core connection, disconnection, killswitch, and system watchdog service logic from this manager and tie it together into a brand new, standalone add-on tailored specifically for custom/dedicated WireGuard tokens. This keeps this main project clean, saves me a massive rewrite headache, and gives you a fully functional, lightweight service for your dedicated connection.
3. Config Generator Only: Or do you just want a quick utility built into the UI to generate the WireGuard configuration files using your token, so you can run them via your own custom scripts or system paths?

Let me know your thoughts and what your setup looks like so we can see what is realistic!

Saluti.