Skip to content

Mideye Authentication & Error Guide

This guide helps you diagnose and resolve common issues with Mideye Server. Each section focuses on specific problem areas with practical solutions based on real-world customer scenarios.

  1. Start with symptoms — If you see an error message, search for it in this guide or check the Quick Reference
  2. Use the web interface — Most issues are visible in the web administration interface under Log Files, Authentication Logs, and Audit Logs
  3. Follow diagnostic steps — Each section provides step-by-step troubleshooting procedures
  4. Apply solutions — Implement fixes via the web interface when possible, then verify resolution
  5. Contact support — If issues persist, collect logs and contact Mideye Support
SymptomMost Likely Section
”Phone or token number is invalid or missing”Phone Number Issues
Service fails to start after upgradeInstallation & Upgrade Issues
”Failed to connect to LDAP profile”LDAP Connection Issues
Database connection errors on startupDatabase Issues
Magic link authentication not workingExternal Service Issues
RADSEC certificate errorsCertificate & RADSEC Issues
Service starts but authentication failsStartup & Timing Issues
Special characters in username/passwordCharacter Encoding Issues
SMS OTP not delivered / Switch unreachableExternal Service Issues
SSL proxy intercepting Switch trafficExternal Service Issues

Common problems during package installation and upgrades:

  • Service starts before configuration files are ready
  • Missing or inaccessible configuration files
  • File permission errors after upgrade
  • Database not ready during first startup
  • Database migration failures

Phone number authentication and validation problems:

  • “Phone or token number is invalid or missing” errors
  • Hidden characters from copy-paste operations
  • Wrong plus sign Unicode characters
  • LDAP attribute mapping issues
  • Phone number format requirements

Problems connecting to LDAP or Active Directory:

  • Connection timeout errors
  • Certificate validation failures with LDAPS
  • “User does not exist” vs connection errors
  • SSL/TLS configuration
  • Testing directory connectivity

Database connectivity and configuration problems:

  • Connection pool errors
  • Database not available during startup
  • Database migration lock issues
  • Verifying database connectivity

Problems with Mideye external services:

  • MAS Magic Link connectivity
  • Mideye Switch primary/secondary failover
  • SSL proxy and MITM interception of Switch traffic
  • Proxy configuration issues
  • Verifying external endpoints

Certificate and RADSEC configuration problems:

  • Self-signed certificate issues
  • RADSEC certificate loading failures
  • Certificate format requirements
  • Certificate expiration
  • Using the Certificate Management page

Service initialization and timing problems:

  • Service start order dependencies
  • Silent failures during initialization
  • External services not ready at startup
  • Health check procedures

How to read and interpret Mideye Server logs:

  • Using the web interface Log Files page
  • Authentication failure patterns
  • Connection error identification
  • Error code reference
  • Collecting logs for support

Character encoding and internationalization problems:

  • RADIUS encoding types per client
  • Username with special characters
  • Password encoding issues
  • Database character encoding

Fast lookup reference:

  • Common error messages and solutions
  • File locations (Linux and Windows)
  • Default ports and protocols
  • Emergency recovery procedures
  • What failed? Authentication, service startup, configuration change?
  • When did it start? After upgrade, config change, or spontaneously?
  • Error messages? Note exact text including error codes
  • Reproducible? Does it happen consistently or intermittently?

2. Gather Information Using the Web Interface

Section titled “2. Gather Information Using the Web Interface”
  • Check Authentication Logs for user authentication issues
  • Review Log Files for system errors
  • Examine Audit Logs for recent configuration changes
  • Check service status from the operating system
  • Test individual components (LDAP, database, external services)
  • Review recent changes (upgrades, configuration, network)
  • Compare with known working configuration
  • Check firewall and network connectivity
  • Use the web administration interface for configuration changes when possible
  • Apply fixes incrementally
  • Test after each change
  • Test the original failing scenario
  • Monitor logs for recurring errors
  • Verify dependent functionality works

If you cannot resolve an issue using this guide:

  1. Collect diagnostic information:

    • Export relevant log files from the Log Files page
    • Note exact error messages and timestamps
    • Document reproduction steps
    • Capture screenshots if relevant
  2. Contact Mideye Support:

    • Provide collected diagnostic information
    • Include Mideye Server version
    • Describe expected vs actual behavior
    • Share relevant configuration (sanitize passwords and secrets)
  3. Include context:

    • Operating system and version
    • Database type and version
    • LDAP/AD infrastructure details
    • Network topology (firewalls, proxies, VPNs)
    • Recent changes to environment