Troubleshooting
If you encounter issues with Login AlertX v4.0, use this guide to resolve common problems, check diagnostic logs, and verify service connectivity on Windows and Linux.
Diagnostic Log File Paths (v4.0)
When troubleshooting or contacting support, check the diagnostic log files generated by the service and client applications:
| Platform | Component | Log File / Journal Path |
|---|---|---|
| Windows | Background Service | C:ProgramDataLoginAlertXLogsservice.log |
| Desktop UI & Tray | %LocalAppData%LoginAlertXLogsapp.log |
|
| Linux | Daemon Log File | /var/log/loginalertx/daemon.log |
| Systemd Journal | journalctl -u loginalertx.service -n 100 --no-pager |
1. Installation & Setup Issues
Windows: Installer Won’t Run or Fails
- Run as Administrator: Right-click
LoginAlertX_Setup.exeand select Run as Administrator to allow service registration. - Disk Space: Verify that you have at least 350+ MB of free disk space for the self-contained .NET 10 runtime binaries and local AI models.
- Antivirus False Positives: If an endpoint security program blocks the service registration, add an exclusion for
C:Program FilesLogin AlertX.
Linux: Package Installation Dependency Errors
If dpkg -i reports missing dependencies, resolve them automatically:
sudo apt-get update && sudo apt-get install -f
2. Service or Daemon Not Running
Windows Service
- Press
Win + R, typeservices.msc, and press Enter. - Find Login AlertX Service in the list.
- If status is not Running, right-click and select Start.
- If the service fails to start, inspect
C:ProgramDataLoginAlertXLogsservice.logfor errors.
Linux Daemon
Verify daemon health using the CLI:
sudo loginalertx status
To restart the background systemd service:
sudo systemctl restart loginalertx.service
3. Notification Delivery Issues
Failed Login Attempts (Event 4625) Not Triggering Alerts
If typing an incorrect password does not generate a failed login alert, Windows Security Auditing for logon failures was likely turned off in local security policy:
- Automated Self-Remediation (v4.3.1+): Login AlertX automatically checks Windows Audit Policy every 6 hours and auto-enables failure auditing for the Logon and Credential Validation subcategories.
- Manual Verification: Open an elevated Command Prompt or PowerShell and run:
Ensure Failure is listed as Enabled. If not, manually enable it with:auditpol /get /subcategory:"Logon"auditpol /set /subcategory:"Logon" /failure:enable
System Tray Warning: “X channel issue(s) detected”
Login AlertX continuously monitors delivery health across all channels (v4.3.0+):
- View Exact Reason: Open the app dashboard and look at the Delivery Health section. It shows the exact protocol error (e.g., SMTP 535 bad password, Telegram bot blocked, or WhatsApp quota reached).
- 1-Click Resolution: Click the Fix button next to the failing channel to navigate directly to its settings page.
- Clear Warning: Once corrected, sending a successful test message (e.g. Send Test Email or Test Webhook) immediately resets the failure counter and restores the tray icon to healthy.
Email Notifications Not Arriving
- Google OAuth: Re-authenticate your Google account in settings. If popups are blocked in your browser, allow popups for localhost authentication.
- SMTP (Gmail / Yahoo): You must generate an App Password in your Google/Yahoo Account Security settings. Standard passwords will be rejected by mail providers.
- Firewall Ports: Ensure outbound traffic is allowed on Port
587(TLS) or Port465(SSL). - Spam Folder: Check your Spam / Junk folder and mark alerts from Login AlertX as “Not Spam”.
Telegram, WhatsApp, Push, or Webhook Alerts Missing
- WhatsApp: Verify the recipient phone number includes the international country code (e.g.
+15550192834or+919876543210). - Slack / Teams / Discord: Use the Test Webhook button in settings to confirm the webhook endpoint returns HTTP 200.
- Mobile Push: Open the Android companion app and ensure the device is paired via QR code in the Linked Devices tab.
4. Webcam Photos or Audio Clips Missing
- Windows Privacy Permissions: Open Windows Settings > Privacy & security > Camera (and Microphone). Ensure “Allow desktop apps to access your camera/microphone” is turned On.
- Linux Device Permissions: Ensure the background user/daemon has permissions to access
/dev/video*and audio capture devices. - Fast-Path Event Bypass: Remember that Screen Lock, Sleep, Hibernate, and Shutdown events intentionally bypass camera and audio capture to dispatch instantly before network standby.
5. Contacting Support
If an issue persists, our engineering team is here to help. Send an email to [email protected] with the following details:
- Operating System & Build: (e.g. Windows 11 23H2, Ubuntu 22.04 LTS).
- Description: Brief description of the issue and steps to reproduce.
- Log Attachments: Attach
C:ProgramDataLoginAlertXLogsservice.log(Windows) or/var/log/loginalertx/daemon.log(Linux).
