Monarobase in France: WordPress pricing and PHP limits

Who Monarobase may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

French throughout the range and help.

Control panel

cPanel, with French guides. Check languages actually available.

Support

Email, tickets and phone advertised. French documented. Confirm other languages and precise response time.

Monarobase in France for checking a WordPress submission

Monarobase offers a shared hosting range in France with preinstalled WordPress, cPanel and a PHP settings interface. A fictional Chartres association receives applications through a WordPress form. It sets a maximum file size, but a request whose attachment respects that limit may still exceed the limit for the whole request.

File size and request size are not identical. The form also sends fields and the delimiters describing them. The local exercise builds the bytes of two requests and compares the file cap with the entire-request cap. It helps identify which setting to check while retaining rejection for an attachment that remains too large.

The profile connects this check with hosting price, access, backups and the ability to test on a copy. The decision concerns available space and assistance as much as the experience of the person submitting the application.

Read the initial price, VAT and expiry date

On 10 November 2026, the WordPress grid displayed Classic from 5.95 € before tax for one month, Optima at 13.95 € before tax and Ultra at 40.95 € before tax. For an invoice at the standard VAT rate of 20% in mainland France, this gives 7.14 €, 16.74 € and 49.14 € including VAT respectively. At that rate with no additional items, twelve months would represent 85.68 €, 200.88 € and 589.68 € including VAT. This calculation makes the three references comparable. It is not an annual quote. The terms provide for advance payment on monthly and annual contracts.

Renewal pricing is not presented in a separate grid column. The terms allow price changes. The FAQ states there is no tacit renewal and that automatic renewal may be requested. The terms also describe automatic renewal for card payments. Before paying, clarify the rule applying to the chosen payment method and the next period’s price. The renewal article in the terms requires a cancellation ticket at least seven days beforehand. The FAQ also mentions five days to request invoice cancellation in its on-request automatic-renewal workflow. Confirm which procedure applies.

The association must record the billed duration, VAT-inclusive price, domain, email and additional services in its quote. The FAQ states that the domain can remain with another registrar. If the association keeps it elsewhere, retain a contact address and two separate expiry dates. When choosing between Classic and Optima, assess the higher plan’s value by resources used by the site and its copy. Maximum upload size also remains an application and PHP rule.

Choose resources and check location

Classic lists one CPU at 3.25 GHz, 2 GB DDR5 RAM and 50 GB NVMe SSD. Optima lists three CPUs, 6 GB RAM and 100 GB. Ultra lists nine CPUs, 18 GB RAM and 300 GB. Classic advertises one cPanel account with two additional sites. Optima and Ultra offer a multi-account option, with advertised limits of ten and forty accounts. Check the option price and effective separation of the copy’s settings. The table presents file and database storage on NVMe. CPU and memory figures help size the environment. By themselves, they describe neither upload processing nor headroom in the server’s temporary directory.

Monarobase places this offer’s servers in France. The provider also describes synchronization to another data center and backups across several locations. For location requirements, record the advertised country and ask which sites are assigned to the account, replication and backups. The test copy and exports retained by the association belong in this record. When attachments contain personal data, test with a synthetic file whose size and type are sufficient to trigger the same workflow.

Before changing a PHP limit, measure site storage, space needed for a copy, temporary files and observed form sizes. Check whether the copy belongs to the same account and settings group. If a cPanel change affects several sites, repeat testing in a separate environment. Increasing disk quota, increasing RAM and increasing a request-size cap affect different things.

Define WordPress features, languages and support

The offer advertises preinstalled WordPress, LiteSpeed, WP Toolkit, WP-CLI and a PHP version selector. It presents update and staging features. Confirm the version actually used by the domain and update scope before touching the site. The form may also apply its own maximum or list of allowed formats. A more permissive PHP policy does not change those rules.

The consulted site and knowledge base are in French. The page advertises email and phone support and also mentions ticket tracking. The provider distinguishes routine support from more assisted services. Confirm hours, intervention response time and any other languages. cPanel is advertised with French guides. Check the panel’s active language in the account. When reporting an upload failure, provide the time, test domain, body byte count and message seen by the user, excluding real attachments.

Help describes SiteJet Builder AI, accessible in cPanel to create a site and content on a hosted domain or subdomain free of any other site. The tool generates an initial version from supplied information. This is a creation environment separate from WordPress. The reviewed grid documents no generative credits integrated into the WordPress installation. If a team considers SiteJet, check access, export rights and how it would recover the form. Decide on changes to the existing form’s limits within the WordPress copy.

Prepare backups and exit

The WordPress page advertises daily backups of files, email and databases to a remote server, duplicated in another data center. The disaster recovery plan describes arrangements for infrastructure incidents. Copies triggered for a WordPress operation address another need. To prepare a setting change, record the host’s latest recovery point, contents and download options. Clarify retention for the plan and recovery time before making this the only rollback route. Synchronization between centers may replicate an incorrect setting. A dated copy helps retrieve the previous state.

WordPress help advertises retention of seven daily, four weekly and two monthly recovery points. Verify dates actually accessible and point scope for your account. The guide also distinguishes on-demand WordPress backups from the full archive downloadable through cPanel. For rehearsal at an independent destination, retain files and a database export, plus current PHP settings. A full account archive helps inventory email and configuration, while isolated restoration may require separate elements. Open these before cancellation or migration. For the form, check where records and attachments are stored. Depending on the plugin, a different database or directory may be used.

Before changing the cap, record starting values, the relevant domain and active PHP version. Download copies to a location controlled by the association. Submitted applications need not be copied into an incident report. On a test target, check permissions for the temporary directory and final storage with synthetic documents. For transfer, also record domain ownership and email behavior. Their availability must be checkable separately from the form.

Practice the two upload limits

The multipart body size and attachment size must be checked separately. — Illustration by BlogPasCher.Open full-size illustration ↗

The ZIP in “Prepare your site” contains EXERCICE-MONAROBASE.cjs. The supplied result was obtained with Node 22.16.0. It assembles a form body in memory with a reference field, attachment and multipart delimiters. No PHP server or WordPress site receives these requests. The model counts actual produced bytes and applies the two selected thresholds. It does not reproduce every validation performed by PHP, WordPress and the web server.

The first set contains a file of 1,048,520 bytes. The complete body contains 1,048,802 bytes, including 282 bytes of envelope and field data. The file stays below the 1,048,576-byte cap while the body exceeds it. With both caps at that value, JSON reports rejection of the POST body. Doubling only the request cap in the model allows the same file. The small 65,536-byte control passes under the initial thresholds. A file of 1,048,584 bytes remains rejected by the individual cap even when the body has more room.

The program distinguishes rejection of the entire request from rejection of the file. The PHP manual states that a body exceeding post_max_size may leave $_POST and $_FILES empty. The web server or an intermediary may also reject the request before PHP. Test values are specific to this example. On the real form, count document bytes and record submitted fields to understand required headroom.

node .\EXERCICE-MONAROBASE.cjs

Check the PHP setting on a WordPress copy

Prepare a private copy using the same PHP version and form rules as the site. In cPanel, the Monarobase guide specifies Sélectionner une version de PHP, then the Options tab. Record upload_max_filesize for one file and post_max_size for the whole request. Check which site or account the setting affects. The guide gives example values in megabytes. The right setting depends on the allowed attachment count, combined size limit and fields users must submit. Retain the file cap and add headroom to the body cap.

Test from a browser with a small document, a synthetic document near the limit and a deliberately oversized document. Open network tools to record the status and rejection point, then verify that an accepted application appears exactly once in the management interface. Also read the message shown to someone whose file is rejected. If the request stops before the application, first examine the received status and the rejecting component’s log. If it reaches WordPress, check the plugin’s maximum and presence of expected files. Do not confuse increasing memory with adjusting an upload threshold.

If it fails, return to the values recorded in cPanel. Replay the small upload to verify rollback and keep the test document outside the public library. If the form saved a reference without an attachment, retain that result and plan a message or application-recovery process. Rehearsal finishes when the team can open the accepted document from the correct account and explain both rejections without exposing application content.

Decide and restore the previous setting if necessary

Classic is the first reference to examine if the association has one site and can rehearse within its 50 GB of storage. Optima and Ultra list more memory and disk. This choice does not automatically resolve a form threshold. Ask whether desired values are available through the plan’s PHP selector, whether a copy can use its own settings and at what price the service will renew. Have the renewal rule confirmed in writing for the chosen payment method, then keep that answer with the invoice.

Before opening the form, verify four things. An authorized document must reach the application, the attachment must link to the correct application, an oversized file must be rejected with a usable message and the previous value must be restorable. For a form accepting several documents, repeat the check with the maximum number advertised to visitors. Each file’s cap and the overall cap must be compatible. Also record whether the observed transfer time suits someone submitting over a slow connection. A useful limit depends on the actual expected file and behavior measured with synthetic data.

If rejection occurs before PHP, increasing only the two PHP directives will not allow the request through. Identify the responsible component from responses and authorized logs. If PHP receives fields but rejects the attachment, compare the per-file cap and plugin setting. If the plugin saved the form without a file, check the rule determining when an application is declared complete. For each case, note the result and person able to restore the previous setting. The association can then arrange recovery of real applications without confusing test attempts with received submissions.

After a production change, replay the small upload and then the permitted near-limit case with a fresh fictional reference. If a result differs, restore starting values and verify that they take effect. Tests and rollback plans remain useful even if the association ultimately chooses another storage tier. The reopening criterion is a submission read back through the management interface, with expected rejections still active.

Prepare your site

• 25 WordPress backup tools by recovery need
• WordPress requirements not met: check PHP and MySQL or MariaDB
• WordPress migration, staging and imports: choose the right tool
• Download the upload-limit exercise