Skip to main content
This guide covers common issues encountered when using Phishmonger and their solutions.

Installation Issues

Port 25 Blocked

Symptoms:
  • Cannot send emails
  • Connection timeouts when sending
  • Unable to capture emails
Diagnosis:
Solutions:
  1. Contact hosting provider to unblock port 25
  2. Use cloud provider that allows port 25 (AWS, DigitalOcean, Linode)
  3. Use authenticated SMTP relay instead of direct delivery
Alternative Ports:
  • Port 587 (SMTP with STARTTLS)
  • Port 465 (SMTPS)

NGINX Won’t Start

Symptoms:
  • NGINX service fails to start
  • Port 80/443 conflict errors
Diagnosis:
Solutions: Port Conflict:
Configuration Error:
Missing Certificates:

Node.js Server Won’t Start

Symptoms:
  • Server crashes on startup
  • Port 4005 already in use
  • Module not found errors
Diagnosis:
Solutions: Port Already in Use:
Missing Dependencies:
Permission Errors:

Email Delivery Issues

Emails Not Sending

Symptoms:
  • Campaign starts but no emails sent
  • All targets remain phished=0
  • No EMAIL_SENT events
Diagnosis:
Solutions: No Targets:
Campaign Stuck:
SMTP Configuration:
  • Verify mail server is correct
  • Check SMTP credentials if using relay
  • Test with authenticated relay (SendGrid, Mailgun)

Emails Going to Spam

Symptoms:
  • Emails deliver but go to spam folder
  • Low mail-tester.com score
Diagnosis:
Solutions: Missing SPF:
Failed DKIM:
Missing Reverse DNS:
Suspicious Content:
  • Remove excessive capitalization
  • Avoid spam trigger words (FREE, URGENT, CLICK HERE)
  • Include unsubscribe text (even if non-functional)
  • Use proper HTML structure

SMTP Errors

550 5.1.1 User Unknown
  • Invalid recipient email address
  • Typo in target list
  • Mailbox doesn’t exist
Solutions:
550 5.7.1 SPF Failure
  • SPF record missing or incorrect
  • Sending from wrong domain
  • SMTP FROM doesn’t match SPF
Solutions:
554 Message Rejected
  • Content filtered as spam
  • Attachment blocked
  • URL on blacklist
Solutions:
  • Test with mail-tester.com
  • Remove suspicious content
  • Check phishing domain reputation
  • Use different payload domain
450/451 Temporary Failure
  • Greylisting (normal, retry later)
  • Rate limiting (too many emails too fast)
  • Server temporarily unavailable
Solutions:
  • Increase campaign delay
  • Wait and retry
  • Use slower sending rate

DKIM Signature Failed

Symptoms:
  • mail-tester.com shows DKIM failure
  • Emails marked as suspicious
Diagnosis:
Solutions: Missing Private Key:
DNS Mismatch:
  • Update DNS TXT record with correct public key
  • Wait for DNS propagation
  • Verify with dig
Wrong Domain:
  • Ensure SMTP FROM domain matches DKIM domain
  • Cannot DKIM sign for domains you don’t control

Campaign Issues

Campaign Won’t Start

Symptoms:
  • “Send Campaign” button does nothing
  • No emails sending
Diagnosis:
Solutions: No Remaining Targets:
Campaign Stuck:
Node.js Process Died:

Campaign Stops Unexpectedly

Symptoms:
  • Campaign starts then stops
  • Some targets sent, others not
Diagnosis:
Solutions: Server Crash:
  • Review logs for errors
  • Check system resources (memory, disk)
  • Restart Node.js server
Rate Limiting:
  • Increase campaign delay
  • Use authenticated relay
  • Spread sending over longer period
Network Issues:
  • Verify network connectivity
  • Check firewall rules
  • Test SMTP server reachability

Tracking Issues

Events Not Appearing

Symptoms:
  • No real-time events in tracking interface
  • Events in database but not displayed
Diagnosis:
Solutions: WebSocket Disconnected:
  • Refresh page (Ctrl+F5)
  • Check NGINX proxy WebSocket configuration
  • Verify server is running
Events Ignored:
Wrong Campaign:
  • Verify you’re viewing correct campaign
  • Check campaign name spelling

Missing Click/POST_DATA Events

Symptoms:
  • EMAIL_SENT events appear
  • No CLICK or POST_DATA events from payload server
Diagnosis:
Solutions: Integration Not Configured:
  • Verify Humble Chameleon logging_endpoint
  • Check admin_cookie value matches
  • Ensure hostname is correct
Authentication Failed:
  • Verify admin cookie value
  • Test with curl manually
  • Check payload server logs
Network Issues:
  • Ensure payload server can reach Phishmonger
  • Check firewall rules
  • Verify DNS resolution

Database Issues

Database Locked

Symptoms:
  • “database is locked” errors
  • Slow query performance
Solutions:
Prevention:
  • Run only one Phishmonger instance
  • Don’t run long queries during campaigns
  • Backup database before modifications

Database Corruption

Symptoms:
  • “database disk image is malformed”
  • Errors reading data
Diagnosis:
Solutions: Minor Corruption:
Major Corruption:

Database Too Large

Symptoms:
  • Slow performance
  • Disk space warnings
  • Long query times
Diagnosis:
Solutions: Delete Old Data:
Vacuum Database:
Archive Data:

Web Interface Issues

Cannot Access Admin Interface

Symptoms:
  • 401 Unauthorized error
  • Page says “Not Authorized”
Diagnosis:
Solutions: Cookie Not Set:
Visit: https://yourdomain.com/?SetMeAdmin Cookie Expired:
  • Clear browser cookies
  • Re-visit set_admin URL
Wrong Cookie Value:
  • Check browser cookies match config.json
  • Clear cookies and re-set

Email Capture Not Working

Symptoms:
  • “Capture Email” button unresponsive
  • Emails sent to domain not captured
Diagnosis:
Solutions: Port 25 Not Open:
DNS MX Record:
Send from Different Network:
  • Outlook may not connect on same network
  • Send from external email address
  • Use different mail client

Performance Issues

Slow Campaign Sending

Symptoms:
  • Emails sending slower than configured delay
  • Campaign takes much longer than expected
Diagnosis:
Solutions: Server Overloaded:
  • Increase server resources
  • Reduce concurrent campaigns
  • Optimize database queries
Network Latency:
  • Choose closer SMTP servers
  • Use faster network connection
  • Reduce DNS lookups
Database Lock Contention:
  • Stop other database access during campaigns
  • Add database indexes

Slow Web Interface

Symptoms:
  • Pages load slowly
  • Tracking page lags
Solutions: Large Event Count:
Database Optimization:
Clear Browser Cache:
  • Hard refresh (Ctrl+F5)
  • Clear browser cache and cookies

Miscellaneous Issues

Telegram Notifications Not Working

Symptoms:
  • No Telegram messages received
  • Events logged but no notifications
Diagnosis:
Solutions: Invalid Bot Token:
  • Verify bot token in config.json
  • Create new bot with @BotFather
Wrong Chat ID:
  • Get updates to find chat ID:
Network Issues:
  • Verify server can reach api.telegram.org
  • Check firewall rules

DKIM Keys Mismatch

Symptoms:
  • DKIM verification fails
  • Emails not authenticating
Solutions: Regenerate Keys:
Update DNS:
  • Copy public key output
  • Update DNS TXT record
  • Wait for propagation

Getting Help

Log Collection

When reporting issues, collect: Server Logs:
NGINX Logs:
Database State:
System Info:

Debug Mode

Enable verbose logging:

Community Support

Common Pitfalls

Always Check First:
  1. Port 25 is open (inbound and outbound)
  2. DNS records are configured correctly
  3. Admin cookie is set
  4. Server has adequate resources
  5. Targets added to campaign before sending
  6. Campaign is not already running
Best Practices:
  • Test with small target list first
  • Always send test emails
  • Monitor campaigns actively
  • Keep backups of database
  • Review logs regularly
  • Update dependencies periodically