openvpn3-log(1)
π openvpn3-log β the OpenVPN 3 Linux real-time session log π
okay bestie, buckle up, this is the openvpn3-log page from the OpenVPN 3 Linux manual set, and it's literally just "watch your VPN log scroll by in real time" energy β¨
πΈ NAME πΈ
openvpn3-log β OpenVPN 3 Linux β Real-time session log π¦
β¨ SYNOPSIS β¨
openvpn3 log [OPTIONS]
openvpn3 log -h | --help
π DESCRIPTION π
So here's the tea, bestie: this command grabs log events from all the various log senders and prints them straight to your terminal. It's giving live-streaming but make it sysadmin π
β οΈ Important vibe check: the user running this command must in advance have been granted access to these log events. If you haven't gotten that access? It will not generate any output. Zero. Nada. Crickets. π So sort out your permissions first, okay?
Also super important, no cap: log events you receive via openvpn3 log are processed in parallel with the system-wide openvpn3-service-log process. Like, your little terminal log stream is not the main character here β they're running side by side π
π OPTIONS π
-h,--helpβ prints the usage and help details right to your terminal. Classic. Helpful. Iconic. π--session-path SESSION-DBUS-PATHβ the D-Bus session path of a running VPN session you wanna pull log events from. Not sure what your path is? Runopenvpn3 sessions-listand it'll hand you a list of all the available session D-Bus paths. You're welcome π-c CONFIG-NAME,--config CONFIG-NAMEβ you can use this instead of--session-pathwhen you'd rather give the configuration profile name instead. Lowkey important detail: theCONFIG_NAMEmust be the name that was active when the session was started. The config names you can pick from? Find them withopenvpn3 sessions-list. Same list, same bestie, different vibe π«Ά-I INTERFACE,--interface INTERFACEβ another one you can use instead of--session-path, this time by handing over thetuninterface name that OpenVPN 3 is managing. Take your pick of the three, literally whatever's easiest for you π--log-level LEVELβ sets the log verbosity for the log events. Valid values are0to6. The higher the value, the more verbose your log events get. And level6? That one includes all the debug events, so prepare for a LOT of text, bestie π--config-eventsβ retrieves log events from the configuration manager. For this to actually work though,openvpn3-service-configmgrmust have been started with--signal-broadcast. No--signal-broadcast, no config events, simple as that β
π SEE ALSO π
openvpn3(1) openvpn3-service-configmgr(8) openvpn3-service-log(8) openvpn3-session-acl(1)
and that's a wrap on this one, babe π this page ships with the OpenVPN 3 Linux docs and it's filed under the manual page name openvpn3-log(1) β go forth and read your logs, you absolute legend π¦β¨
π¦ where this page comes from
- nixpkgs unstable: openvpn3 27.1
- ubuntu stonking: openvpn3-client 27.1+dfsg-2ubuntu1 Β· AGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms