No matching documentation found

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:\ProgramData\LoginAlertX\Logs\service.log
Desktop UI & Tray %LocalAppData%\LoginAlertX\Logs\app.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
  1. Run as Administrator: Right-click LoginAlertX_Setup.exe and select Run as Administrator to allow service registration.
  2. 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.
  3. Antivirus False Positives: If an endpoint security program blocks the service registration, add an exclusion for C:\Program Files\Login 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
  1. Press Win + R, type services.msc, and press Enter.
  2. Find Login AlertX Service in the list.
  3. If status is not Running, right-click and select Start.
  4. If the service fails to start, inspect C:\ProgramData\LoginAlertX\Logs\service.log for 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

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 Port 465 (SSL).
  • Spam Folder: Check your Spam / Junk folder and mark alerts from Login AlertX as “Not Spam”.
WhatsApp, Push, or Webhook Alerts Missing
  • WhatsApp: Verify the recipient phone number includes the international country code (e.g. +15550192834 or +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:\ProgramData\LoginAlertX\Logs\service.log (Windows) or /var/log/loginalertx/daemon.log (Linux).
Scroll to Top