Skip to main content
ORIV can now move an existing Nginx server from the deprecated Ondřej/Ubuntu package source to the official nginx.org build in one click, straight from your server dashboard. The Ondřej PPA that ORIV previously relied on is being deprecated and no longer ships new Nginx releases, which left servers on it stuck on older versions. This upgrade moves you to the officially maintained nginx.org build so your server stays current, and it rebuilds the modules ORIV depends on (headers-more for custom headers/Web Rules, and brotli compression) so you lose none of the functionality your sites already use. You also gain newer capabilities like HTTP/3. The upgrade is designed to be safe by default. Your existing Nginx keeps serving traffic the entire time, ORIV validates your configuration before it starts, and if the final check or module build fails it automatically rolls back and leaves your original Nginx running. It runs in the background and usually finishes in a few minutes, without you needing to run any server commands manually. This guide is for server owners and admins on Ubuntu 24.04 who want newer, supported Nginx releases, and it covers what the upgrade does, how to run it, and what to expect at each step. Follow the steps below:

​
Prerequisites / required permissions

​
Step 1: Open the eligible server

Open the server dashboard for an eligible Nginx server. ORIV shows an upgrade banner near the top of the server page.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step 2: Review what the upgrade will do

The confirmation modal explains the upgrade plan before anything is queued. If the information looks correct, choose Upgrade Nginx.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
3. Resolve pre-flight warnings when custom config is incompatible

Before queuing the upgrade, ORIV scans custom Nginx config for directives that are known to break on newer official Nginx builds. If it finds blockers, the modal switches to an incompatibility view.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.
If you intentionally want to proceed, type the server name in the confirmation field and select Upgrade anyway. The rollback gate still protects the server if the final config test fails.

​
Step 4: Let the upgrade run in the background

After the upgrade is queued, the banner changes to a running state.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Step 5: Confirm completion

When the upgrade completes successfully, ORIV shows a success banner.
[!NOTE] Precisa de ajuda visual para esta etapa? Entre em contato com o nosso suporte em support@oriv.cloud.

​
Limits / edge cases

  • The offer is only shown for provisioned Nginx-based servers on Ubuntu 24.04 that are not already on the official nginx.org source.
  • OpenLiteSpeed servers are intentionally excluded.
  • ORIV blocks automatic package restart during the swap and performs one final reload only after the generated configuration passes nginx -t.
  • If the final config test or module build fails, ORIV rolls back and leaves the existing Nginx serving traffic.
  • Pre-flight issues do not make the upgrade impossible, but they should be fixed first unless you are intentionally relying on rollback protection.

​
Frequently Asked Questions

​
What is this upgrade?

This is ORIV’s guided move from the older Ondřej/Ubuntu Nginx package source to the official nginx.org build. ORIV handles the repository change, rebuilds compatible headers-more and brotli modules, and keeps ORIV features such as Web Rules/custom headers and brotli compression available after the upgrade. It also enables newer Nginx capabilities such as HTTP/3.

​
Was my server vulnerable earlier?

No customer action is needed for earlier exposure. ORIV already mitigated the relevant vulnerability immediately with targeted package and security fixes. This guided upgrade is the long-term package-source transition; it does not mean customer sites were left exposed until now.

​
Why did ORIV not update earlier?

Moving to the official nginx.org packages was a large platform change. ORIV previously used the Ondřej package source because it included modules and features ORIV needed. The official nginx.org package does not include every ORIV-required module out of the box, so ORIV needed to rebuild and support missing pieces such as headers-more and brotli, add compatibility checks, add rollback behavior, and verify the flow carefully before offering it on customer servers.

​
Should I back up my sites first?

A backup is recommended, but it is not required for the upgrade to run. ORIV keeps the current Nginx serving during the build and rolls back if the final config test or module build fails. A recent backup is still a good precaution and helps you recover faster if the server has unrelated site issues, custom Nginx snippets, or manually edited configuration.

​
Does this restart Nginx during the build?

No. Existing Nginx continues serving sites while ORIV prepares the repository and compiles compatible dynamic modules. ORIV blocks automatic package restarts during the swap and performs a single nginx -t-gated reload at the end.

​
What happens to headers-more and brotli?

ORIV rebuilds them as compatible dynamic modules for the official nginx.org build, so custom headers/Web Rules and brotli compression remain available after the upgrade.

​
Can I leave the page after starting?

Yes. The upgrade is queued and runs in the background. The banner reflects the current status when you return.

​
What should I do if pre-flight warnings appear?

Fix the listed custom Nginx config first whenever possible. If you proceed anyway, ORIV still uses the final config test and rollback path to avoid leaving the server on a broken Nginx build.

​
What happens if I dismiss or ignore the banner?

Dismissing the banner disables the upgrade banner for that server. If you need it again, contact support, or start the same upgrade from the server’s Management Settings page when the server is still eligible.

​
Where else can I start the upgrade?

For eligible servers, ORIV also shows an Upgrade Nginx action in the server’s Management Settings service list. The action opens the same confirmation and pre-flight flow as the dashboard banner.