In the field of Advanced options of your CURIAWEB cPanel you can find various tools for automation, technical diagnostics, and special web server settings.
At CURIAWEB you will find the functions here Cron jobs, DNS tracking, Index, Error pages, Apache Handler, MIME types and Antivirus scanner.
You may need some of these tools regularly, while others are intended primarily for special technical requirements. In this article, we explain what each function is designed for and when you should use it.
Briefly explained: Some of the advanced options directly affect the technical processes of your web hosting. You normally do not need to change anything here unless a specific application or issue requires it.
Where do you find the advanced options? #
Log in to your CURIAWEB cPanel and open the section on the home page Advanced options.
There you will find the following features:
- Cron jobs
- DNS tracking
- Index
- Error pages
- Apache Handler
- MIME types
- Antivirus scanner
An overview of all areas of your cPanel can be found under cPanel at CURIAWEB explained: All areas and functions at a glance.
Cron jobs #
Cron jobs make it possible to execute certain commands or scripts automatically according to a set schedule.
Instead of starting a task manually every time, the server can run it, for example, hourly, daily, weekly, or at custom-defined times.
Cron jobs are used, among other things, for maintenance tasks, data imports, synchronizations, scheduled scripts, or other recurring processes.
How does a cron job work fundamentally? #
A cron job essentially consists of two parts:
- the schedule that determines when the process is executed
- the command to be executed at this time
For example, a schedule can specify that a script is started at a specific time every day.
Classic cron syntax uses five time fields for this:
Minute Hour Day Month Weekday
The command to be executed follows.
Important: A cron job runs automatically. Therefore, an incorrect command can be executed again with every scheduled run. Carefully check paths, parameters, and the schedule before saving a cron job.
What does an asterisk mean in a cron schedule? #
The sign * serves as a placeholder in a cron time field and simply means that every permissible value is taken into account for this field.
A cron expression must therefore be read as a whole. Multiple asterisks do not simply mean „automatically“, but rather define the execution times together with the remaining fields.
We will cover the exact setup and typical schedules step by step later at Create a cron job in cPanel and set the schedule correctly.
How often should a cron job be executed? #
That depends entirely on the task.
A task that is only needed once a day should not be run every few minutes without a reason. Frequently executed cron jobs can cause unnecessary processes and additional resource consumption.
Conversely, a time-critical process must, of course, not be executed only once a day if the application requires more frequent processing.
Practical Tip: Select the execution frequency according to the actual needs of the application. „As often as possible“ is usually not a sensible default setting for cron jobs.
Cronjob and WordPress-Cron are not the same #
In WordPress, the term can also help you WP-Cron meet.
WP-Cron is a system provided by WordPress for scheduled tasks within the application. A classic server cron job, on the other hand, is started by the server-side cron service according to a set schedule.
Both mechanisms can be combined with each other, but technically they are not the same.
When you set up a standard cPanel cron job, you are working at the hosting level and not directly within the WordPress task scheduler.
Why does a cron job sometimes not work? #
A cron job may not run as expected for various reasons.
Typical causes include, for example, an incorrect file path, a faulty command, missing permissions, an incorrect runtime environment, or an inappropriate schedule.
Even a script that works manually does not necessarily execute identically under the conditions of a cron job. Among other things, the environment, paths, and available variables may differ.
We will cover systematic troubleshooting later under Cron job not working: Causes and solutions.
DNS tracking #
The function DNS tracking provides tools for examining DNS information and the network connection to specific destinations.
With this you can investigate technical information regarding the resolution of a domain or network paths.
The feature is particularly interesting when diagnosing DNS or connection issues.
What does DNS resolution mean? #
The Domain Name System ensures, among other things, that a hostname like:
www.deine-domain.ch
can be resolved into the technical information required for communication.
Therefore, during a DNS query, you can examine, for example, which IP address is returned for a hostname.
This can be helpful if you want to check whether a domain points to the expected technical target.
Important: DNS tracking is primarily used for diagnostics. If you actually want to change a DNS record, you use the Zone editor in the domain of domains.
We cover the practical management of DNS records under Using the DNS Zone Editor in cPanel.
Consider the DNS cache when troubleshooting #
When a DNS record has just been changed, various DNS resolvers may still use a previously cached value.
Therefore, a query from a specific system does not necessarily show that every resolver on the internet is already using the same new value.
Therefore, when making a diagnosis, you should also take into account when the DNS record was changed and what TTL applies to the record in question.
Index #
With the function Index you can control how the web server behaves for specific directories when no normal index file is present there.
Typical index files of a website can be named, for example:
index.html
or:
index.php
If a corresponding start file is not present, the web server may, depending on its configuration, list the contents of the directory or prevent access to such a listing.
What is directory listing? #
Under Directory Listing Directory listing is understood when no matching index file is loaded.
This may allow visitors to see file names and directory structures that should not be displayed as a normal webpage.
Safety: A public directory listing should only be allowed if it is explicitly requested. For standard website directories, it generally makes sense to avoid accidental file listings.
Indexes are not responsible for your website's homepage #
The function Index should not be confused with the content-related homepage of a CMS.
In WordPress, for example, it is determined within the application which content is displayed as the home page. The cPanel feature Index controls the behavior of the web server during directory access.
Therefore, if you only want to change the homepage of your WordPress website, this cPanel feature is not the right place.
Error pages #
With the function Error pages custom output pages can be defined for certain HTTP errors.
For example, if a visitor requests a non-existent URL, the web server can return an HTTP status code 404 return.
Instead of a simple standard message, a custom-designed error page can be displayed.
Other typical status codes include, for example:
400– Bad Request401- Unauthorized403- Forbidden404- Not Found500- Internal Server Error
A custom error page does not fix the error #
A customized error page primarily changes the presentation for the visitor. It does not automatically eliminate the technical cause of the respective HTTP error.
For example, if your website unexpectedly encounters an error 500 spends, it makes no sense to merely make the 500 error page look nicer. The cause of the server error still needs to be investigated.
Briefly explained: An error page determines what the visitor sees in the event of a specific error. It is not a tool for repairing the underlying cause.
CMS and custom error pages #
Content management systems and web applications can handle certain errors themselves.
For example, WordPress has its own processing for much of the content that is not found and can display a 404 page that matches the theme being used.
Therefore, an error page defined in cPanel does not necessarily have to be visible for every error in a web application. The decisive factor is at which level the request is processed and the error is generated.
Apache Handler #
With Apache handlers it can be specified how the Apache web server handles certain file types.
In the process, a file extension can be mapped to a specific handler that tells the web server how to process corresponding files.
This function is intended for special server or application configurations.
For a standard website, you usually don't need to make any changes here.
Attention: Do not change Apache handlers on a hunch. An incorrect mapping can cause certain files to no longer be processed correctly.
MIME types #
MIME types describe the content type of a file or an HTTP response.
This allows a client to be informed about the type of content it is.
Examples of MIME types are:
text/html
for HTML content or:
image/jpeg
for JPEG images.
CSS, JavaScript, PDF files, videos, and numerous other file formats also have corresponding content types.
Why are MIME types important? #
Browsers and other clients can use the transmitted Content-Type to decide how content should be handled or displayed.
An incorrect MIME configuration can therefore cause a file type not to be processed as expected.
For common web files, the necessary associations are usually already present. Custom MIME types are mainly needed for special file formats or individual requirements.
Practical Tip: If an application simply uses a specific file extension, that does not automatically mean you need to create a dedicated MIME type for it in cPanel. Only change these settings if there is an actual technical requirement.
Do not confuse Apache handlers and MIME types #
Both functions can refer to file types or file extensions, but they fulfill different tasks.
A MIME type describes the content type communicated to a client.
A Apache Handler influences, on the other hand, how the web server processes certain files.
Therefore, an issue with one file type should not automatically be handled by changes in both places.
Antivirus scanner #
With the Antivirus scanner Areas of your hosting account can be scanned for known malware or suspicious files, provided this is supported by the provided scanner configuration.
A scan can be useful, for example, if you suspect that unwanted or harmful files are in your hosting account.
The virus scanner is to be understood as an additional tool. In the CURIAWEB hosting environment, there are also other security mechanisms such as Imunify360 available.
Found malicious code may be only part of the problem #
When a website has been compromised, an attacker may have modified several files or created additional access points.
Removing a single infected file is therefore not necessarily sufficient.
In addition, it should be clarified how the compromise occurred. Possible causes could include outdated web applications, insecure credentials, or vulnerable extensions.
Important: When malware is detected, not only the found file should be examined. It is also crucial to find and close the cause of the security incident.
Virus scanners and Imunify360 – why do both exist? #
The virus scanner visible in cPanel and Imunify360 are simply not two different buttons for the exact same function.
Imunify360 is a more comprehensive security platform that can provide various protection and analysis mechanisms within the hosting environment. The virus scanner, on the other hand, provides a targeted scanning function within the corresponding cPanel area.
Which specific detection and treatment options are available depends on the respective server-side configuration.
When should you use the advanced options? #
Some functions in this area are very useful in everyday life. Cron jobs, for example, are regularly used for automated tasks, while DNS tracking can help with technical problems.
Other tools like Apache handlers or custom MIME types are only needed for special configurations.
You don't have to fully configure the advanced options just because they are present in cPanel.
Always investigate only one cause at a time when making technical changes #
Especially in this area, small changes can have a direct impact on the behavior of a website.
Therefore, if there is a problem, you should not modify cron jobs, add MIME types, and adjust Apache settings at the same time.
Make changes specifically and then check whether they have the expected result.
Basic rule: A specific technical requirement should lead to a specific change. The fewer unnecessary settings you change at the same time, the easier it is to trace a problem later.
Summary #
The area Advanced options Your CURIAWEB cPanel contains tools for automation, diagnostics, and special web server configurations.
With Cron jobs can you execute recurring tasks automatically. The DNS tracking helps with the investigation of DNS and network issues. About Index can the behavior during directory access be influenced, while Error pages being able to customize the display of certain HTTP errors.
Apache Handler and MIME types are intended for special requirements in the processing of file types. The Antivirus scanner assists in scanning your hosting account for suspicious or malicious files.
You do not need to change many of these settings on a normally functioning website. Use them specifically when a specific application or technical problem requires it.
In our advanced guides, we show you in particular how to properly set up cron jobs, diagnose faulty cron jobs, and manage DNS records using the cPanel Zone Editor.
