Installation Issues
Port 25 Blocked
Symptoms:- Cannot send emails
- Connection timeouts when sending
- Unable to capture emails
- Contact hosting provider to unblock port 25
- Use cloud provider that allows port 25 (AWS, DigitalOcean, Linode)
- Use authenticated SMTP relay instead of direct delivery
- Port 587 (SMTP with STARTTLS)
- Port 465 (SMTPS)
NGINX Won’t Start
Symptoms:- NGINX service fails to start
- Port 80/443 conflict errors
Node.js Server Won’t Start
Symptoms:- Server crashes on startup
- Port 4005 already in use
- Module not found errors
Email Delivery Issues
Emails Not Sending
Symptoms:- Campaign starts but no emails sent
- All targets remain phished=0
- No EMAIL_SENT events
- 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
- 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
- SPF record missing or incorrect
- Sending from wrong domain
- SMTP FROM doesn’t match SPF
- Content filtered as spam
- Attachment blocked
- URL on blacklist
- Test with mail-tester.com
- Remove suspicious content
- Check phishing domain reputation
- Use different payload domain
- Greylisting (normal, retry later)
- Rate limiting (too many emails too fast)
- Server temporarily unavailable
- Increase campaign delay
- Wait and retry
- Use slower sending rate
DKIM Signature Failed
Symptoms:- mail-tester.com shows DKIM failure
- Emails marked as suspicious
- Update DNS TXT record with correct public key
- Wait for DNS propagation
- Verify with
dig
- 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
Campaign Stops Unexpectedly
Symptoms:- Campaign starts then stops
- Some targets sent, others not
- Review logs for errors
- Check system resources (memory, disk)
- Restart Node.js server
- Increase campaign delay
- Use authenticated relay
- Spread sending over longer period
- 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
- Refresh page (Ctrl+F5)
- Check NGINX proxy WebSocket configuration
- Verify server is running
- 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
- Verify Humble Chameleon logging_endpoint
- Check admin_cookie value matches
- Ensure hostname is correct
- Verify admin cookie value
- Test with curl manually
- Check payload server logs
- Ensure payload server can reach Phishmonger
- Check firewall rules
- Verify DNS resolution
Database Issues
Database Locked
Symptoms:- “database is locked” errors
- Slow query performance
- 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
Database Too Large
Symptoms:- Slow performance
- Disk space warnings
- Long query times
Web Interface Issues
Cannot Access Admin Interface
Symptoms:- 401 Unauthorized error
- Page says “Not Authorized”
https://yourdomain.com/?SetMeAdmin
Cookie Expired:
- Clear browser cookies
- Re-visit set_admin URL
- 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
- 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
- Increase server resources
- Reduce concurrent campaigns
- Optimize database queries
- Choose closer SMTP servers
- Use faster network connection
- Reduce DNS lookups
- Stop other database access during campaigns
- Add database indexes
Slow Web Interface
Symptoms:- Pages load slowly
- Tracking page lags
- 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
- Verify bot token in config.json
- Create new bot with @BotFather
- Get updates to find chat ID:
- Verify server can reach api.telegram.org
- Check firewall rules
DKIM Keys Mismatch
Symptoms:- DKIM verification fails
- Emails not authenticating
- Copy public key output
- Update DNS TXT record
- Wait for propagation
Getting Help
Log Collection
When reporting issues, collect: Server Logs:Debug Mode
Enable verbose logging:Community Support
- GitHub Issues: https://github.com/fkasler/phishmonger/issues
- Documentation: Review this documentation thoroughly
- Related Projects: Check Humble Chameleon, Flik repositories
Common Pitfalls
Always Check First:- Port 25 is open (inbound and outbound)
- DNS records are configured correctly
- Admin cookie is set
- Server has adequate resources
- Targets added to campaign before sending
- Campaign is not already running
- Test with small target list first
- Always send test emails
- Monitor campaigns actively
- Keep backups of database
- Review logs regularly
- Update dependencies periodically