ionCube24 is a three-part suite for monitoring service availability and performance, ensuring security and protection against malware, and capture of PHP and JavaScript errors.
Monitoring is performed every minute by testing the time it takes to connect and receive a response. Alerts are raised for error conditions, and both real-time and historical charts are available to view performance trends. Common services such as Website, DNS, SMTP can be monitored, with a choice of regions of the world to connect from.
PHP errors in website and CLI code are captured with a PHP extension, so no code changes are required, and JavaScript errors are captured by adding a script tag to web pages. Errors can be easily viewed, filtered and prioritised via the ionCube24 web interface.
ionCube24 keeps websites secure by blocking files added or modified on the server after security is enabled, and sends notifications when new or modified PHP files are detected. As some websites may routinely generate new files, file blocking is switched off by default to avoid accidental blocking and behaviour to be monitored. Enabling and disabling of security, blocking behaviour, whitelisting and whether files are blocked or unblocked can all be controlled via the web interface. Security can also be managed via an API.
You can disable ionCube24 on the ionCube Loader by setting the entry ic24.enable to 0 in
your php.ini file:
ic24.enable = 0
This will disable ionCube24, while leaving the ionCube Loader intact. Should you wish to uninstall the ionCube Loader, you
can remove the relevant zend_extension entry pointing to your ionCube Loader files from your php.ini,
as well as remove any ionCube Loader files from your system.
54.172.250.61.
Cloudflare discuss whitelisting IP's in
this article.
Each plan also offers a longer data retention period than the preceding plan. Please contact us if you need a plan for more than 10 domains. Further details are available in the pricing table.
The Site Errors feature is a sortable, filterable and searchable table of PHP and JavaScript Errors of varying error
levels such as Notice or Warning. Any errors detected by the ionCube Loader will be reported here.
Entries to the Site Errors page however, won't necessarily generate any notifications because many sites will produce
errors such as Notices which aren't fatal nor necessarily within your control to fix. Due to this,
only PHP Errors and Warnings will generate Notifications, which you can receive through
the UI, Email or Pushover.
However, Site Error entries and Error Notifications do share functionality in that reading a Site Error Warning
or Error will also read its corresponding Error Notification and vice versa. Note that whilst Site Errors and
PHP Errors are linked via the ability to read notifications, ignoring Notifications or Site Errors are not linked and will
produce different effects. More info can be found in the "Can I ignore a notification permanently?" entry below.
Notifications can also be raised via other means such as the Security feature. These are not related to Site Errors in any way.
PHP has several error levels. These include non-critical Notices that may be due to poor coding,
Warnings of operations that failed but that did not stop the request, and Errors that
caused a request to fail and usually giving a blank page. PHP can also warn when a program uses Deprecated
features that are going to be removed from PHP in the future, and cases where code did not follow Strict
usage guidelines.
A well coded website should produce no errors at all, however many websites will produce errors, with Notices being the most common. As they are not fatal errors, they will not prevent the site from working, however in some cases Notices can be an indication of bugs. If these occur in your own code, you should aim to resolve them.
Yes. You can silence a non-security notification by clicking the icon before marking it as read with .
Use the Filter dropdown if you wish to show ignored notifications later.
Because only PHP Errors and Warnings generate notifications however, there is a difference between
ignoring a notification and a entry on the Site Errors table. Ignoring the notification will prevent the
same notification from reappearing whereas ignoring the Site Errors entry will hide it from the table
Yes. Use the Site Error Reporting > Global Settings feature to select types of errors to ignore. Note that this will take effect for all domains across all servers.
You can also ignore errors with a setting in the php.ini file. Suppose you want to ignore
all Notice level notifications. Add the following setting to
your php.ini file:
Error types can also be combined as in the following examples:
If your domain is reachable under any name other than the ones you have configured, you should enable Domain Wildcard Protection on one of the domains for your server. This will ensure that all domains on the server are protected, including those not configured in the interface. This will also protect if a domain is accessed by a fake name. As this setting will protect all domains on your server, it is best to ensure that all domains have been configured accordingly.
If your plan does not include Domain Wildcard Protection, it is recommended to ensure that your domain is reachable only by the names you have configured in ionCube24. Furthermore, your domain should not be the default domain on your server, (i.e., your webpage should not be reachable through the IP address of the server), as this may allow your site to be reached using an unprotected domain name.
If you have problems setting up your system, please contact us so we can assist.
There are several mechanisms for this.
ic24.sec.trusted_include_paths in your php.ini to automatically trust entire directories.
For example, if you wanted to trust the directory /var/cache then simply set this setting to /var/cache.
If you wanted to trust multiple directories, you can use : as a seperator, e.g. /var/cache:/var/other+ or -
to either include or exclude the directory, which could be used
to trust files in a directory except a specific sub directory. This can be doing via the following:
/var/cache:-/var/cache/private
.php
Changes are likely to be blocked because they will be unexpected, and your site is protected precisely because ionCube24 does block unexpected changes.
Before updating files, our recommended approach is to temporarily disable security, then update the files on your website and re-enable security once all updates have completed. It is best to update as quickly as possible so there is no window of opportunity for an attacker. The interface has options to disable security for 5, 10 and 15 minutes, as well as indefinitely. If you choose one of the temporary options, security will automatically be re-enabled after that period of time.
Another option is to have certain directories of the site automatically trusted with the ic24.sec.trusted_include_paths
setting, who's usage is detailed in the section 'How do I allow trusted Website Files'.
The exclusion key can also be used to indicate that a file should be trusted. Last, you can add sets of files to be trusted via the web interface.
curl -sS -d {' "trustpoint_delta": 5 }' \
-X POST -H 'Authorization: API key="XYsdfhooufhukwerhuosrghoisgho348734sdfbukZ"' \
-H 'Content-Type: application/json' https://ioncube24.com/api/v1/domains/xyz.com/trustpoint