Oxahost in Tunisia: WordPress pricing and rollback

Who Oxahost 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 on the Tunisian offer pages consulted.

Control panel

File manager and staging advertised. Panel languages to confirm.

Support

Technical support advertised as continuously available. Public channels in French. Arabic and English to confirm.

Oxahost in Tunisia: choosing a WordPress rollback

Oxahost markets a managed WordPress range in Tunisia, with four levels sharing security, backup and staging functions. The fictional association in Sfax updates the plugin that records its registrations. The new code also changes the database structure. After the incident, the team has an older plugin folder and two data states. Its choice is to determine which pair allows a restart.

The first check separates a file fault from a schema change. A working copy lets the team compare states without intervening on the public site. The local exercise shows failure with old files and a newer database, then successful reading with a pair from the same state. Choosing to return to an older database has a separate consequence. Registrations received between the two backups must be inventoried before any rollback.

This profile examines terms billed in dinars, declared data residency, the provider’s role and export procedures. Staging is used to test a pair and write the rollback plan. The decision point is reached when the file version, database state and handling of recent registrations are known.

Read the billed price and cycle in dinars

On November 10, 2026, the WordPress table displayed twelve-, twenty-four- and thirty-six-month selectors. In the thirty-six-month view, the advertised amount is 455.94 TND excluding tax for WP Basic, 914.94 TND for WP Developper, 1,220.94 TND for WP Business and 1,832.94 TND for WP Prime. For Basic, the displayed monthly equivalent is 12.665 TND excluding tax, alongside a crossed-out reference of 14.9 TND excluding tax. Crossed-out references for the other plans are 29.9, 39.9 and 59.9 TND excluding tax. The advertised total equals the monthly equivalent multiplied by thirty-six.

The same page’s code also contains a product configuration in USD. For Basic, it lists 59.60 USD over twelve months, 113.24 USD over twenty-four months and 151.98 USD over thirty-six months. The table’s 455.94 TND is exactly three times the last figure. This arithmetic ratio appears across all four thirty-six-month plans. Billing help presents dinars for Tunisia, euros and dollars internationally, and currency selection at account creation. The embedded configuration establishes neither a billing exchange rate nor the final amount for a given profile. The local record uses the visible TND table and distinguishes these technical data.

The same view displays a three-month benefit and billing every thirty-six months. Clarify the first due date and how the benefit is applied. The terms specify automatic renewal for an equivalent term and allow price changes on renewal. The commercial cycle label and crossed-out amounts therefore do not establish a contractual amount for the following cycle. The provider describes a renewal invoice issued fourteen days before expiry and a request to cancel renewal at least twenty-four hours beforehand. Keep the plan reference, dates and written amount in the association’s file.

Table prices are expressed in Tunisian dinars. The billing page mentions 19% VAT and a 1 TND stamp duty where applicable. In the example of an invoice with both lines, 455.94 TND excluding tax gives approximately 543.569 TND. Check rounding and the total on the invoice. A domain free for the first year does not settle its cost at subsequent renewals. Distinguish domain renewal, email used by the site and any backup options.

Size the plan and check data location

The cards advertise 10, 25, 60 and 100 GB SSD. Listed WordPress instance counts rise from two to five, seven and ten. Displayed RAM is 1, 2, 4 and 8 GB. CPU values are presented in GHz, and the cards also give I/O limits of 4, 6, 8 and 10 MB/s and PHP request counts of 25, 35, 55 and 75. These labels describe neither reserved core counts nor guaranteed application throughput. The Basic profile presents use of one main site while displaying two instances. Ask how test copies are counted.

The range’s FAQ places its servers in a data center in Tunis. It describes data retention in Tunisia with exceptions when an external option is activated on request, giving Acronis Cloud Europe as an example. For the association, record separately the site location, native-copy location and location of exports it chooses to keep elsewhere. A data-residency statement does not specify the exact center of all copies or handling of any network cache. Ask about the scope of options activated on the reference.

A plan for this association must leave enough space for the active database, a temporary archive and the private copy used for testing. Assess download sizes and import time on a copy before making recovery depend on an entry-level plan. Increasing storage helps only if the team has access to open archives and select the correct components. If staging shares a quota, prepare it with a fictional subset or in a separate environment.

Define managed WordPress, support and AI scope

Oxahost presents WP Clone for staging, WP-CLI, LiteSpeed cache, SSL certificates and security management. The page also advertises automatic updates of the core, themes and plugins. For a business-critical form, identify plugins whose updates modify tables and check site settings after every change. Prepare a window and copy for a schema-changing update. The association team decides how to recover registrations and who authorizes restoration.

The offer website and consulted terms are in French. The page presents continuously available technical support, and the terms list account, form and telephone channels. Arabic or English support, panel languages and timeframes for a specific restoration remain to be confirmed. Send support a timestamped record including the module version and date of every available copy. Specify whether the team wants file recovery, database recovery or simply access for testing.

Oxahost markets a separate AI site builder. Its page advertises multilingual page generation starting at 15 TND excluding tax per month, with hosting included in that product. The WordPress table does not document inclusion of that product or a generation quota in the four plans. AI is therefore a separate need and budget line. For the association, verify the editable format and export mechanism of any creation tool before making forms or content dependent on it.

Establish the actual scope of backups and exit

Guidance for preparing a targeted restore. — Illustration by BlogPasCher.Open full-size illustration ↗

The WordPress FAQ embedded in the page advertises daily snapshots on all four plans, retained off-site for thirty days, with restoration from the panel. Prime adds on-demand copies. The general terms give varying indications by service, with indicative weekly or monthly frequency and retention of thirty to ninety days. They disclaim guarantees of completeness, integrity and restoration. Ask which points are visible for WP Basic, whether a point can be downloaded and how to restore files or the database separately. Ask for capture time, timezone, included elements and the procedure for extracting a specific point. A backup from the incident day may already contain the update.

The cPanel shared-hosting range presents JetBackup and its own procedures. The WordPress screen and export method must be checked on the WordPress plan. For a recovery exercise, record site files and contained data for each point. Identify separate volumes, media stored elsewhere and mailboxes used to send confirmations. Files and the database are two distinct parts of a WordPress backup. A plugin-only copy allows examination of its code, while a media-folder copy allows checking that document links work.

The sales page presents inbound migration. For exit, record the separate operations for downloading the file archive, exporting the database, retrieving DNS settings and opening the site outside the plan. The terms mention thirty days of retention in one contract-ending case, while also providing for access revocation. The entitlement to obtain a download and its procedure after closure remain unclear. For the association, the exit milestone is a copy already opened elsewhere before cancellation, with someone designated to retain keys and documentation.

Practice file and database recovery

The ZIP in “Prepare your site” contains EXERCICE-OXAHOST.php and RESULTAT-OXAHOST.json. Run the former with PHP and PDO SQLite, supplying a new working path. The delivered result comes from PHP 8.4.8. The script builds two manifests simulating plugin versions. In the first state, an SQLite database contains a reference registration, SFAX-001, and a contact column. The script copies this database, then evolves the copy by replacing the column with email. It adds a second fictional registration, SFAX-002. The test uses a deliberately reduced local model. Its result measures neither Oxahost backups nor the behavior of a real WordPress plugin.

The first trial reads the old manifest with the schema 2 database. It reports rejet because expected and found versions differ. The second matches the old manifest to the schema 1 database. It opens the state and finds SFAX-001. The third opens the current pair and finds both references. SHA-256 hashes of the current database match before and after the recovery trials. The difference between registration lists isolates SFAX-002. That is precisely the reconciliation work that would remain if the association restored the older pair.

To reproduce the test in PowerShell from the script folder, run this command with a nonexistent, accessible path on D:.

In the JSON, read the module_schema and database_schema pair for the rejected control, then compare the two references lists. If recovery is announced without presenting the list of writes to reconcile, the exercise remains incomplete. In a real WordPress installation, also record the PHP version and destination-database compatibility. Local recovery with SQLite is used here to make the schema change’s effect visible. The WordPress test on a copy uses the same engines and versions as the environment planned for return to service.

php .\EXERCICE-OXAHOST.php 'D:\CODEX_STORAGE\tmp\reprise-oxahost-essai-01'

Prepare rollback and preserve newer data

Before any manipulation, make an independent copy of the incident state. Keep the database and files together with a UTC time, plugin versions and scheduled-task status. During active operation, choose when the form stops accepting new writes or provide a register for registrations received during intervention. A copy retained after the freeze supplies the starting point for reconciliation. In staging, restrict access, replace personal data with examples and disable outgoing email and external integrations.

Then compare the two paths opened by the exercise. If the fixed plugin can read the recent schema, test a fix on a copy of the current state. Verify reading, creating and updating a test registration, and the confirmation destination. If the association chooses the older pair, first export the list of writes differing between the two states and document their recovery. The model’s column rename does not establish that every relationship, metadata item and attachment of a real form can be reimported without transformation.

In the test copy, recover one fictional reference at a time and observe the result after a second attempt. The association wants to find a single registration, its expected fields and confirmation state. Define with the responsible person which cases require manual recovery. If the backup also concerns other plugins, compare new accounts and other changes received since capture. One person signs the list of resolved discrepancies; another checks the form and public display. The export-and-import trial helps verify the plan’s access before an incident.

Decide before restoring the public site

The Basic plan may suit the association if space permits opening a working copy and the provider confirms capture of files and the database at the same recovery point. Staging, WP-CLI and the file manager provide ways to perform the check. Snapshots, resource limits and support’s exact role determine the time needed. Include in the quote the tax-inclusive amount, currency, actual covered term, renewal date, domain cost and procedures for downloading a copy. For a project requiring Tunisian residency, also record options and data that would pass through an external service.

Before returning to service, record the last valid state and the time from which data must be recovered. The exercise gives three observable decisions. Old files with the recent database are rejected. The older pair can restart after preparing reconciliation of SFAX-002. The current pair remains available for checking a fix that preserves both registrations. In a real situation, decide with the person who knows the data, then record form-test results and handling of newer writes in the incident log.

The stopping point is a pair of uncertain origin, an archive that will not open or new registrations whose fate has not been decided. In that case, keep the public form paused and continue on the working copy. If the validated state is old, recover the agreed writes before lifting restrictions. If the form returns to service, check from a separate session that the result read by the team matches what the registrant sees. Attach the retained copy’s reference and the procedure for repeating the operation to the file.

Prepare your site

• 25 WordPress backup tools by recovery need
• WordPress prerequisites unmet: check PHP and MySQL or MariaDB
• WordPress migration, staging and imports: choose the right tool
• Download the rollback exercise