Common Monitoring Errors
When WebMon checks your website, various errors can occur. Here is what they mean and how to fix them.
Connection Errors
Connection Refused
What it means: The server actively rejected the connection attempt.
Common causes:
- Server is not running
- Firewall blocking the connection
- Wrong port number
- Service crashed
How to fix:
- Verify the server is running
- Check firewall rules
- Confirm the correct port is open
- Restart the web server service
Connection Timeout
What it means: The server did not respond within the expected time.
Common causes:
- Server is overloaded
- Network issues
- Server is too slow
- DNS resolution problems
How to fix:
- Check server resources (CPU, memory)
- Verify network connectivity
- Optimize server performance
- Check DNS configuration
DNS Resolution Failed
What it means: The domain name could not be resolved to an IP address.
Common causes:
- Domain does not exist
- DNS server issues
- Domain expired
- DNS propagation in progress
How to fix:
- Verify domain is registered and active
- Check DNS records are configured correctly
- Wait for DNS propagation (up to 48 hours)
- Try different DNS servers
SSL/TLS Errors
SSL Certificate Error
What it means: There is a problem with the site's SSL certificate.
Common causes:
- Certificate expired
- Certificate not valid for domain
- Self-signed certificate
- Incomplete certificate chain
How to fix:
- Renew expired certificates
- Ensure certificate matches domain
- Install intermediate certificates
- Use a trusted certificate authority
SSL Handshake Failed
What it means: The secure connection could not be established.
Common causes:
- Incompatible SSL/TLS versions
- Cipher suite mismatch
- Certificate issues
- Server misconfiguration
How to fix:
- Update SSL/TLS configuration
- Enable modern cipher suites
- Check certificate installation
- Verify server SSL settings
HTTP Errors
Too Many Redirects
What it means: The page keeps redirecting in a loop.
Common causes:
- Misconfigured redirects
- HTTP to HTTPS redirect loop
- CMS configuration issue
- .htaccess problems
How to fix:
- Check redirect rules
- Verify SSL redirect configuration
- Review .htaccess or nginx config
- Check CMS URL settings
Request Timeout
What it means: The server took too long to respond.
Common causes:
- Slow database queries
- Heavy server load
- Large page size
- External API delays
How to fix:
- Optimize database queries
- Scale server resources
- Enable caching
- Review slow external calls
Content Errors
Empty Response
What it means: The server returned no content.
Common causes:
- Application error
- Blank page bug
- Output buffering issue
- Server misconfiguration
How to fix:
- Check application logs
- Review recent code changes
- Test page manually
- Check PHP/server error logs
Content Mismatch (Keyword Monitors)
What it means: Expected keyword was not found on the page.
Common causes:
- Page content changed
- Dynamic content loading
- JavaScript-rendered content
- Wrong page being checked
How to fix:
- Verify the keyword still exists
- Check if content loads via JavaScript
- Update keyword if content changed intentionally
- Verify correct URL is monitored
Network Errors
Network Unreachable
What it means: Cannot establish network connection to the server.
Common causes:
- Server is offline
- Network outage
- Routing issues
- IP blocked
How to fix:
- Verify server is online
- Check for network outages
- Verify IP is not blocked
- Contact hosting provider
Getting Help
If you continue experiencing errors:
- Check the error message - It often contains specific details
- Review check history - Look for patterns in when errors occur
- Test manually - Try accessing the URL in your browser
- Check server logs - Look for corresponding errors on your server
- Contact support - If the issue persists, reach out for help