Pango Platform
HomeConsole
  • What is Pango Developer Platform
  • Getting started
    • Sign up on the Management Console
    • Create a new project
    • Switch projects
    • Change console settings
    • Edit your profile
    • Try out the demo app
    • Keep exploring
    • Deprecation and Sunset
  • Console details
    • Dashboard
      • General
      • Location loading
    • Users
      • User page
    • Active sessions
    • Network
      • Countries
      • Locations
      • Pools
        • Optimal location
        • Location rules
    • Settings
      • General
        • Project config description (JSON format)
          • Server selector (JSON format)
          • Request selector (JSON format)
      • Authentication methods
        • Auth Plugin requirements
      • VPN
        • General
        • VPN Bypass list
        • Client Networks
      • Member
    • Export Data
    • Log
  • SDK
    • Unified VPN SDK
      • Features
        • Personal Bridge
      • Tunnel Vision and Tunnel Crack Prevention
      • Unified VPN SDK Feature Comparison By Platform
    • Unified VPN SDK for Android
      • Setup
        • Application Setup
        • Proguard Rules, Notification, and Analytics Configurations
        • Backend URL Configuration
      • Usage
        • Initialization
        • VPN Interface
        • Backend interface
      • Features
        • Hydra Protocol
          • Location profile (Hydra only)
        • Custom sdk dependencies
        • Deferred VPN Service Initialization
        • Authentication
        • Client Network List (CNL)
        • OpenVPN transport
        • Wireguard Transport
        • Reconnection strategy
        • Single Protocol SDK
        • Killswitch
        • Domain route via VPN
        • Process route via VPN
        • Process Bypass
        • Domain Bypass
        • Traffic rules
        • VPN Node DNS Configuration
        • Multihop
          • Optimal Location
      • Exceptions
      • Version migration
      • Changelog
    • Unified VPN SDK for Apple
      • Setup
        • Application Setup
        • Network Extension Setup
          • Network Extension Setup for tvOS
        • Backend URL Configuration
      • Usage
        • Single Protocol SDK
        • Unified SDK
        • Logging
        • Decoding Encoded VPN SDK Logs
        • Analytics Configuration
      • Features
        • Deferred VPN Service Initialization
        • Authentication
        • Wireguard Transport
        • Reconnection strategy
        • Killswitch
        • Domain Bypass
        • Multihop
          • Optimal Location
        • Client Network List (CNL)
        • Domain route via VPN
      • Changelog
      • API Reference
    • IPSEC VPN SDK for Apple
    • Unified VPN SDK for Windows
      • Setup
        • Backend URL Configuration
        • Service command line arguments
        • ARM Platform Support
      • Usage
        • CoreAPI
        • Events
        • Generating a Unique Device Identifier
        • Error processing
        • Pipe Messaging
      • Features
        • Traffic protection
          • Killswitch
          • Prevent IP Leaks
          • Block Local Networks
        • Other
          • Firewall
            • DNS Monitor
            • Process Bypass
            • Domain Bypass
            • Process route via VPN
            • Domain route via VPN
          • Throttling
          • Optimal Location
          • Common issues
        • Hydra Protocol
          • CustomDNS, UserDNS, MultiHop, VpnProfiles
        • OpenVPN Protocol
        • Wireguard Protocol
        • IPSec Protocol
      • Collecting Debug Logs
      • Changelog
    • Unified VPN SDK for Routers
      • SDK. Shared library.
      • Configuration Interface (CI)
        • Unix Domain Sockets CI
        • REST API CI
  • REST API
    • Partner API
  • Sample applications
    • Unified VPN SDK demo for Windows
    • Hydra VPN SDK demo for iOS
    • IPSEC VPN SDK demo for iOS
    • Unified VPN SDK demo for Android
    • Hydra VPN SDK demo for OpenWRT
    • OpenVPN configuration file
  • Resources
    • Use cases
      • Public VPN
      • Business VPN
        • Creating a Business VPN Project
        • Wi-Fi Security for Business
      • Application anti-blocking
    • How-to
      • Create a Firebase project for User Authentication
      • AWS CloudFront Distribution of the Platform URL
      • How can I get Shared Secret key from iTunes Connect for In-App Purchase
  • FAQ
    • General
      • VPN Platform Flow
      • What data is collected by the Platform?
      • What analytic data is collected by your SDK?
      • How the Platform restricts access to our data?
      • Why DNS Leak tests often indicate positive result?
      • Do we need to perform endpoint health checks?
      • How is the VPN exit node found?
      • How are streams re-marked if VPN is enabled/disabled on an active flow?
      • Is there a maximum number of supported devices?
      • Are both IPv4 and IPv6 supported?
      • What is the MTU of the tunnel?
      • Are any redundancy measures in terms of reliability provided?
      • Is there any load balancing?
      • Do you block broadcast and multicast to/from the VPN?
    • List of Open Source libs
Powered by GitBook
On this page
  • UnifiedSDK Logs
  • Protocols Logs
  • Windows Event Logs
  • Memory Dumps

Was this helpful?

  1. SDK
  2. Unified VPN SDK for Windows

Collecting Debug Logs

When reaching out for debugging assistance with the Unified SDK, please collect and provide the following logs:

UnifiedSDK Logs

Logs contain information about the Unified SDK service.

Default location: C:\ProgramData\UnifiedSDK.Service\logs\UnifiedSDK.Service.log

Or you can specify where UnifiedSDK service should store log files by options -lf "<path to the log file>" or -d "<path to the data folder>".

Note, that by default UnifiedSDK service writes only Error logs (Error log level) and it can be not enough for investigation in some error scenarios.

You can configure logging level with -ll option when you are installing UnifiedSDK service.

UnifiedSDK.Service.exe -i "ServiceName" -ll "Debug" -lf "c:\ProgramData\MyApp\logs\service.log"

Also you can use the following method to configure the log level for SDK service on runtime:

await sdk.ConfigureLogLevelAsync(requiredLogLevel).ConfigureAwait(false);

Note, that the -ll option passed during service installation has higher priority comparing to the value updated by this method and will take in place after service restart.

And to get the minimum log level used by SDK service at the moment:

var result = await sdk.GetCurrentLogLevelAsync().ConfigureAwait(false);

Note, that with Trace and Debug levels you will take all requests and responses without any encryption. All keys and token will be logged to the log file. So we recommend to use default option settings (only error logging), Warning or Information (only general data logging) in production.

Protocols Logs

Protocol logs can be enabled via StartVpnRequest using EnableTunnelLogging property.

// This example shows the launch of the Hydra protocol with enabled logs 
var startVpnRequest = new StartVpnRequest
{
    AccessToken = loginResponse.AccessToken,
    Credentials = getCredentialsResponse.Credentials,
    DeviceId = DEVICEID,
    EnableKillSwitch = false,
    EnableTunnelLogging = true,
    VpnNode = getNodesResponse.VpnCountries.FirstOrDefault(),
};
    
var startVpnResponse = sdk.StartVpn(startVpnRequest);

Once enabled, protocol logs will be stored at the following locations:

Protocol
Location

Hydra

C:\ProgramData\UnifiedSDK.Service\system\logs\hydra.log

WireGuard

C:\Program Files (x86)\%your_app_folder%\Executable\Wireguard\log.bin

Windows Event Logs

Some events, such as unexpected service drops, are logged to Windows Event Logs.

To access these logs:

  1. Open Event Viewer by running: %windir%\system32\eventvwr.msc /s

  2. Navigate to Windows Logs > Application

  3. Look for log entries with the source UnifiedSDK.Service

Memory Dumps

PreviousIPSec ProtocolNextChangelog

Last updated 6 days ago

Was this helpful?

More information about memory dumps can be found .

here
EventViewer logs example