Troubleshooting

If you run into issues while using our platform, don’t worry, this guide will walk you through what to do.

Could not parse the URL. Is it valid and not blocked by a firewall?

When a site should be added to the platform and the error "Could not parse the URL. Is it valid and not blocked by a firewall?" is displayed, then it means that the site can't be scrapped and the initial pages loaded. This can have one of the following reasons:

The url is not valid, double check if it really works and there are no typing errors.
A firewall is blocking access to the web server. Ask your hoster if it is reachable by api.is-it.io.
Websites have nowadays bot protection activated to prevent spam. Configure the protection that access from api.is-it.io is allowed or from the user agent "is-it.io/1".

You have reached the maximum number of checks for today

There is a limit of 10 checks per day per site. You have to wait till tomorrow to run checks again.

The web server firewall blocks is-it.io after a security scan

The security scan performs some checks which can trigger a firewall. The firewall should be configured that it doesn't block the user agent is-ut.io/1 or the host api.is-it.io.

The web site calls appear in my site analytics

When the site gets tested, then we do that with a special user agent "is-it.io/1". It is possible to filter out the traffic then for this specific user agent string the site analytics app.

Filter is-it.io agent in Google Universal Analytics (UA)

It is possible to filter out traffic from a specific User Agent in UA by using custom dimensions and filters.

1. Capture the User Agent as a Custom Dimension

In Google Analytics Admin, go to
Property → Custom Definitions → Custom Dimensions, and create one named User Agent with Session scope.
In Google Tag Manager (GTM), create a Custom JavaScript Variable:
```
function() {
  return navigator.userAgent;
}
```
Add this variable to your GA Pageview Tag, mapping it to the custom dimension slot you created.

2. Exclude the Specific User Agent via Filters

Once data is flowing, in Google Analytics Admin, go to View → Filters → Add Filter.
Choose Custom → Exclude, set the field to your User Agent dimension, and enter the UA string or regex pattern you want to filter out.

Filter is-it.io agent in Matomo

To exclude traffic for a particular User agent (or several user agents), go to Administration, click on Settings under the Websites (or Measurables) section. Below the list of websites, you will find the option to specify Global list of user agents to exclude. More information can be found here.

Check is not started in Wordpress update plugin

If the plugin does not start a new check after a plugin or theme update, you can enable temporary logging to investigate the issue. Follow these steps:

Open your wp-config.php file in the root directory of your WordPress installation.
Find the line that says:

define( 'WP_DEBUG', false );

and change it to:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

Save the file and reproduce the issue (e.g. update a plugin or theme).
Check the log file at wp-content/debug.log for messages related to the plugin.
Once you are done troubleshooting, disable debugging by resetting the values to:

define( 'WP_DEBUG', false );

Important: Do not leave debugging enabled on production sites, as it may expose sensitive information.

Check is not started in Joomla update plugin

If the plugin does not start a new check after an extension update, you can use the Joomla log file to troubleshoot the issue. Follow these steps:

Go to your Joomla installation directory.
Open the file:

/administrator/logs/is-it.io.log.php

Review the log messages for any errors or warnings related to the plugin.
If you find repeated or unclear errors, copy the relevant lines and share them when requesting support.
If the file doesn't exist, turn on debug mode in Joomla and check it again.

Tip: After troubleshooting, clear or rotate the log file to prevent it from growing too large over time.