Use Joomla’s built-in maintenance control: sign in to the Administrator back end, open Global Configuration → Site, set Site Offline to Yes, choose the message behavior, and save. Visitors then receive Joomla’s offline page while authorized administrators can continue working. After the work is complete, return to the same screen, set the option to No, and save again.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What Joomla’s offline mode actually does
Joomla’s Site Offline switch changes the public frontend into an offline message page. Joomla describes the result this way: “When set to Yes all site visitors see an offline message page with login form.” The administrator interface is not taken offline, so you can still sign in to manage the site.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frontend access for staff is permission-based. Joomla’s configuration reference for Joomla 4.x identifies Offline Access as the permission that lets selected user groups view the frontend while the site is offline. A person who can enter the Administrator area is not automatically a suitable frontend tester; confirm that the intended group has this permission before you begin.
The switch is designed for a short, reversible outage while you make relatively minor changes. It is not a substitute for a development copy when you need to test a major extension upgrade, database migration, or template rewrite.
#1 Best Overall
Before switching the site offline
Decide whether production maintenance is appropriate
Use offline mode when the work is brief and the public site needs a consistent message during the change. Examples include a small configuration adjustment, a controlled content change, or the final cutover after testing elsewhere.
For complex work, clone the site to a development server or subdomain. Test the change there, take a current production backup, schedule the cutover, and use offline mode only for the final production steps. This keeps an extended test cycle away from visitors and gives you a tested rollback path.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Prepare access and recovery
- Confirm that an Administrator account can sign in before enabling the switch.
- Identify the user group that will test the frontend and verify its Offline Access permission.
- Record the maintenance window and a realistic completion message.
- Take the backup required by your hosting and Joomla change procedure, especially before extension or database work.
- If you plan to use hosting-level directory protection instead, make sure you have the directory credentials and a separate recovery route.
How to put a Joomla site offline
- Sign in to the Joomla Administrator back end. Use an account that can edit global configuration.
- Open Global Configuration. From the current dashboard, choose Home Dashboard → Global Configuration. Older Joomla documentation may show the route as System → Global Configuration; both labels lead to the same configuration screen in the versions that use those menus.
- Open the Site tab. The offline controls are part of site-wide settings, not an individual menu item or article.
- Set Site Offline to Yes. This enables the maintenance response for public frontend requests.
- Choose the offline-message behavior. Select Use Custom Message, Use Site Language Default Message, or Hide, depending on what visitors should see.
- Optionally choose an offline image. Use a small, appropriately sized image and check it on a phone as well as a desktop browser.
- Select Save or Save & Close. The setting does not take effect until Joomla accepts the configuration change.
- Test the result. Open the frontend in a private browser window or a session that is not logged in. Check the message, image, layout, and any contact information.
Joomla’s documented English default message is: “This site is down for maintenance. Please check back again soon.” The exact language shown can follow the site language when you select the language-default option.
Choosing the message and image
Use Site Language Default Message
This is the lowest-maintenance choice when a standard notice is sufficient. Joomla supplies the default wording in the active site language, so you do not have to maintain a separate translation for each visitor language.
Use Custom Message
A custom notice is better when visitors need operational information. State what is happening, give a time window only when you can support it, and provide a support or status contact if one exists. Avoid promising an exact reopening time unless the work is tightly controlled.
Keep the message readable without relying on scripts or a logged-in session. Test the typography and line wrapping on a narrow mobile screen, where long notices can become difficult to scan.
Hide
Hide suppresses the explanatory text while retaining the offline behavior. Use it only when a blank or minimal maintenance presentation is intentional; it gives visitors no context about why normal pages are unavailable.
Optional offline image
An image can reinforce the maintenance page, but it should be lightweight and legible at mobile sizes. Verify that its contrast works with the offline template and that the page remains useful if the image fails to load.
Rank #3
- Used Book in Good Condition
Let selected people view the frontend while it is offline
The offline page is not the same as a complete lockout. Joomla keeps the Administrator interface available, and users with the appropriate frontend permission can continue to view the site. Joomla’s User Manual states: “The Site Offline switch does not apply to the administrator interface and users who can login to the backend can continue to login to the frontend.”
- Identify the account or group that should preview the frontend.
- In Joomla’s user and permission configuration, confirm that the group has Offline Access.
- Have a tester sign in through the frontend and load several representative URLs, including the home page, an article, a form, and any extension affected by the maintenance.
- Test once while logged in with the permitted account and again in a private window. The private window should receive the offline page, proving that public visitors are not bypassing the setting.
If a permitted tester still sees the offline page, check the account’s group membership, inherited permissions, session state, and whether the tester is using the frontend login rather than only an Administrator session.
Carry out maintenance without losing the recovery path
Use a short, observable change window
Record the start time, the configuration you changed, and the first checks you will run after each step. Keep an Administrator session open in one browser window, but do not rely on that session as proof that anonymous visitors can reach the site.
Make and verify backups before destructive work
For extension upgrades, schema changes, or file replacements, use the backup and rollback process supplied by your hosting and site-management setup. A maintenance page prevents visitors from submitting new frontend requests; it does not protect you from a failed update or a bad database migration.
Check integrations that may not use the normal frontend
List external callbacks, scheduled jobs, feeds, APIs, and payment or form endpoints before the outage. The Joomla offline switch governs the site frontend; a separate integration may have its own authentication and availability behavior. Pause or test those services according to their own documentation if the maintenance could affect them.
Bring the Joomla site back online
- Return to Home Dashboard → Global Configuration (or System → Global Configuration in older menu documentation).
- Open the Site tab.
- Set Site Offline to No.
- Select Save or Save & Close.
- Sign out of the frontend or use a private window and load the home page.
- Check a representative article, navigation link, contact or form page, and any extension changed during the window.
- Review the server and Joomla logs for errors generated during the change, then confirm that scheduled tasks and external callbacks are operating normally.
Do not leave the switch enabled after the work ends. A successful Administrator session can hide the fact that ordinary visitors are still receiving the offline page, so the anonymous-window check is essential.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Built-in offline mode, directory lockout, or staging?
| Approach | Scope | Trusted access | Message control | Operational risk | Best use |
|---|---|---|---|---|---|
| Joomla Site Offline | Joomla frontend; Administrator remains available | Backend administrators plus groups granted Offline Access | Default language message, custom message, hidden message, and optional image | Simple, reversible configuration toggle | Short or relatively minor maintenance |
| Hosting Directory Privacy | Entire protected Joomla directory | Anyone with the directory username and password | Hosting control’s authentication prompt rather than Joomla’s offline page | Hosting-level lockout can block administrators and testers without credentials | When every request to the directory must be blocked |
| Development server or subdomain | Separate copy, leaving production available | Staff with access to the development environment | Defined by the development copy and its access controls | Requires cloning, test data handling, and a planned cutover | Complex changes, major upgrades, migrations, or template rewrites |
These choices are not interchangeable. The Joomla switch communicates a maintenance state while preserving controlled access. Directory protection sits below Joomla and can stop all visitors, including people who would normally use the Administrator interface. Staging reduces production risk by moving the work to a separate environment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to block every visitor with Directory Privacy
When the requirement is to prevent all web access to the Joomla directory, Joomla’s user guide describes using the hosting control panel’s Directory Privacy feature. The exact labels vary by host, but the process is generally:
Best Value
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
- Open the hosting control panel and locate Directory Privacy (also called directory or folder protection by some hosts).
- Select the directory containing the Joomla installation.
- Enable password protection for that directory.
- Create an authorized directory user and a strong password when prompted.
- Save the protection settings.
- Test from a browser that is not already authenticated. The protected directory should request the directory username and password before serving Joomla.
- Give the credentials only to the people who require access, and record a recovery method before starting maintenance.
This control is independent of Joomla users and permissions. It can therefore block the Administrator path as well as the public frontend unless the person has the directory credentials. Remove or disable the protection through the same hosting control panel when the maintenance is complete, then test both the public site and Administrator login.
Staging guidance for complex Joomla work
Joomla documentation recommends a development server or subdomain for changes that go beyond relatively minor maintenance. A practical sequence is:
- Clone the production files and database to an isolated development location.
- Apply the extension, database, or template changes there first.
- Exercise the important user journeys and record any required configuration changes.
- Take a fresh production backup immediately before the cutover.
- Schedule a production window and enable Joomla’s offline mode for the final change.
- Repeat the tested steps on production, verify the site, and disable offline mode.
- Keep the tested copy and the backup available until the production result is confirmed.
Staging does not eliminate the need for a maintenance window: data created on production after the clone may need to be reconciled, and the final migration can still require a brief outage. It does, however, keep experimentation and failed attempts away from the live site.
Troubleshooting common problems
The public site still looks online
- Confirm that Site Offline is set to Yes and that you saved the configuration.
- Retest in a private window while logged out. A permitted user session can bypass the public offline page.
- Check whether a proxy, cache, or content-delivery layer is serving an older response. Purge or revalidate that cache according to its configuration.
A tester cannot see the frontend
- Verify the tester’s group has Joomla’s Offline Access permission.
- Confirm the tester is signed in through the frontend and has a current session.
- Check that the account is not being blocked by another access rule or extension.
The custom message or image is wrong
- Return to Global Configuration → Site and check the selected message mode.
- Confirm that the custom text was saved in the intended site language.
- Check the image path, file permissions, dimensions, and mobile rendering.
No one can reach Administrator after directory protection was enabled
Use the hosting control panel’s Directory Privacy settings and the authorized directory credentials to regain access. If those credentials are unavailable, contact the hosting administrator through the account’s recovery process. Plan this recovery route before enabling a directory lockout; Joomla’s own Administrator permissions cannot override a web-server password prompt.
The maintenance takes longer than planned
Update the custom message if the new timing is known, keep a permitted tester checking the frontend, and continue using the backup and rollback plan. If the work has expanded into untested changes, stop adding scope in production and move the remaining work to staging rather than extending an uncontrolled outage.
Quick Recap
Final maintenance checklist
- Backup and rollback plan confirmed.
- Administrator login tested.
- Frontend tester group confirmed with Offline Access.
- Maintenance message and optional image reviewed on desktop and mobile.
- Site Offline set to Yes and saved.
- Anonymous and authorized frontend tests completed.
- Maintenance steps and integration impacts recorded.
- Site Offline returned to No and saved.
- Anonymous post-maintenance checks completed.
- Logs, scheduled tasks, forms, and external callbacks reviewed.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
