Instant monitoring for Linux servers

Quiet, fast alerts for SSH logins and reboots.

Drop-in scripts that notify your Telegram account via t69.me. No agents, no dashboards, no surprises.

Install SSH Alert Install Reboot Alert
PAM + systemd Secure API keys One-line installs

Sample notification

SSH login 
🔓 user@hostname [ 192.168.1.100 ]

🕓 2025-11-19 10:30:45 UTC

🇺🇸 203.0.113.1 (US)
One-line install SSH Login Alert
Command 
export SSH_LOGIN_API_KEY=your_api_key_here && curl -sSL https://s.fsend.me/ssh-login-alert-setup.sh | sudo -E bash

Replace your_api_key_here with your t69.me API key.

SSH Login Alert

Know who signed in, instantly.

Get instant notifications when users log in or out via SSH. Track access with geolocation and server context.

SSH

Login/Logout Tracking

Monitor SSH sessions in real time.

GEO

Geolocation

Country flags and location lookup on public IPs.

PAM

PAM Integration

Automatic notifications via PAM hooks.

INFO

Detailed Info

Username, IP, hostname, and timestamp.

Quick installation

Prerequisites: Linux system with PAM and curl installed. Root access required.
One-line install 
export SSH_LOGIN_API_KEY=your_api_key_here && curl -sSL https://s.fsend.me/ssh-login-alert-setup.sh | sudo -E bash
Replace your_api_key_here with your API key from t69.me. The -E flag preserves environment variables in sudo (works on Linux and macOS).
Alternative: download and run 
curl -O https://s.fsend.me/ssh-login-alert-setup.sh
export SSH_LOGIN_API_KEY=your_api_key_here
sudo -E bash ssh-login-alert-setup.sh

What gets installed

  • /usr/local/bin/ssh-login-alert.sh - Handles SSH event notifications.
  • /etc/pam.d/sshd - Modified to trigger notifications on login/logout.
  • /etc/t69.conf - Stores SSH_LOGIN_API_KEY (separate from REBOOT_API_KEY).

Notification format

Each notification includes user, hostname, IP address with country flag, and timestamp.

Public IP example 
🔓 user@hostname [ 192.168.1.100 ]

🕓 2025-11-19 10:30:45 UTC

🇺🇸 203.0.113.1 (US)
Private or local IP example 
🔓 user@hostname [ 192.168.1.100 ]

🕓 2025-11-19 10:30:45 UTC

🏠 Local: 192.168.1.50

Note: Private IPs (10.x.x.x, 172.16-31.x.x, 192.168.x.x, 127.x.x.x) are detected and shown with a house icon, skipping geolocation API calls.

Management

Test notification 
sudo /usr/local/bin/ssh-login-alert.sh
Uninstall 
sudo rm /usr/local/bin/ssh-login-alert.sh
sudo sed -i '/ssh-login-alert.sh/d' /etc/pam.d/sshd
SSH troubleshooting and updates

Notifications not working

  • Verify PAM configuration: grep ssh-login-alert /etc/pam.d/sshd
  • Check SSH_LOGIN_API_KEY in /etc/t69.conf
  • Test manually: sudo /usr/local/bin/ssh-login-alert.sh
  • Check SSH logs: journalctl -u sshd -f

Update API key

Update SSH_LOGIN_API_KEY 
# Update SSH_LOGIN_API_KEY in config
sudo sed -i 's/^SSH_LOGIN_API_KEY=.*/SSH_LOGIN_API_KEY=your_new_key/' /etc/t69.conf

# Or add if it doesn't exist
echo "SSH_LOGIN_API_KEY=your_new_key" | sudo tee -a /etc/t69.conf
sudo chmod 600 /etc/t69.conf

Restore PAM configuration

Restore from backup 
# List available backups
ls -la /etc/pam.d/sshd.backup-*

# Restore from backup
sudo cp /etc/pam.d/sshd.backup-YYYYMMDD-HHMMSS /etc/pam.d/sshd

Reboot Alert

Track boots, reboots, and shutdowns.

Get instant notifications when your server starts, shuts down, or reboots. Lightweight systemd integration with secure key storage.

BOOT

Boot Notifications

Get alerted when your server starts up.

RE

Reboot Detection

Distinguish between shutdown and reboot events.

CMD

One-Line Setup

Install with a single command.

LOCK

Secure Storage

API key stored with 600 permissions.

Quick installation

Prerequisites: Linux system with systemd and curl installed. Root access required.
One-line install 
export REBOOT_API_KEY=your_api_key_here && curl -sSL https://s.fsend.me/reboot-alert.sh | sudo -E bash
Replace your_api_key_here with your actual API key from t69.me. The -E flag preserves environment variables in sudo (works on Linux and macOS).
Alternative: download and run 
curl -O https://s.fsend.me/reboot-alert.sh
export REBOOT_API_KEY=your_api_key_here
sudo -E bash reboot-alert.sh

What gets installed

  • /etc/t69.conf - Securely stores your API key (600 permissions).
  • /usr/local/bin/t69-notify.sh - Handles sending notifications.
  • /etc/systemd/system/t69-notify.service - Auto-starts on boot and monitors events.

Testing and management

Test notification 
sudo /usr/local/bin/t69-notify.sh "Test notification"
Check service status 
systemctl status t69-notify.service
View logs 
# Follow logs in real-time
journalctl -u t69-notify.service -f

# View recent logs
journalctl -u t69-notify.service -n 50

Uninstall

Remove service and scripts 
sudo systemctl stop t69-notify.service
sudo systemctl disable t69-notify.service
sudo rm /etc/systemd/system/t69-notify.service
sudo rm /usr/local/bin/t69-notify.sh
sudo rm /etc/t69.conf
sudo systemctl daemon-reload
Notification format 
🖥️ [Hostname] | 📍 [IP Address] | 🔔 [Event] | ⏰ [Timestamp]

🖥️ prod-server-01 | 📍 192.168.1.100 | 🔔 Powered on | ⏰ 2025-11-19 10:30:45 UTC
Reboot troubleshooting

Service not active after installation

Check service status 
systemctl status t69-notify.service

Check for errors in the output. Common issues include network connectivity or incorrect API key.

Notifications not being received

  • Verify API key is correct in /etc/t69.conf
  • Check network connectivity to t69.me
  • Review logs: journalctl -u t69-notify.service -n 50
  • Test manually: sudo /usr/local/bin/t69-notify.sh "Test"

Script execution issues

Verify permissions 
# Verify script has execute permissions
ls -l /usr/local/bin/t69-notify.sh

# Should show: -rwxr-xr-x

Get Your API Key

Connect your Telegram account.

To use the monitoring tools, you need an API key from t69.me (MessageGateBot). This key lets your server send notifications to your Telegram account.

DM

Private Chat

For personal notifications.

1. Chat with @MessageGateBot
2. Send /start
3. Send /key

TEAM

Groups and Channels

For team notifications.

1. Add @MessageGateBot to group
2. Give admin permissions (channels)
3. Send /key in the group

TOPIC

Forum Topics

For organized alerts.

1. Enable Topics in group settings
2. Go to a specific topic
3. Send /key in that topic

Security note: Your API key is sent privately to your DMs. In group chats, only admins and owners can request the key.
Important: Keep your API key secure. Anyone with your API key can send notifications to your Telegram account. Never share it publicly or commit it to version control.

View full documentation on t69.me

What is next?

Once you have your API key, you can install the monitoring tools above. Use the same key for both Reboot Alert and SSH Login Alert, or request different keys for each service.

Use Both Services

Install Reboot + SSH alerts together.

Both services can run on the same server. They share /etc/t69.conf but keep separate API keys.

Installation order does not matter. Both installers will create /etc/t69.conf if it does not exist and preserve existing keys.

Shared configuration file

/etc/t69.conf 
# /etc/t69.conf
REBOOT_API_KEY=xxx-xxx-xxx-xxx
SSH_LOGIN_API_KEY=yyy-yyy-yyy-yyy

Install both services

Install both 
# Install Reboot Alert
export REBOOT_API_KEY=your_reboot_key && curl -sSL https://s.fsend.me/reboot-alert.sh | sudo -E bash

# Install SSH Login Alert
export SSH_LOGIN_API_KEY=your_ssh_key && curl -sSL https://s.fsend.me/ssh-login-alert-setup.sh | sudo -E bash

Update individual keys

Re-run either installer to update just that service's API key:

Update keys 
# Update only REBOOT_API_KEY (preserves SSH_LOGIN_API_KEY)
export REBOOT_API_KEY=new_reboot_key && curl -sSL https://s.fsend.me/reboot-alert.sh | sudo -E bash

# Update only SSH_LOGIN_API_KEY (preserves REBOOT_API_KEY)
export SSH_LOGIN_API_KEY=new_ssh_key && curl -sSL https://s.fsend.me/ssh-login-alert-setup.sh | sudo -E bash
Note: You can use the same API key for both services or different keys. Using different keys allows you to route notifications to different destinations if supported by your notification service.