How to Test Gutenberg 24.0’s DataForm Editor
Gutenberg 24.0 lets WordPress users try a redesigned settings panel for posts and pages. The redesign uses DataForm, a form-based way to…
When you update a Magento 2 store, maintenance mode blocks customers from using the storefront and shows them a maintenance page. Magento sends an HTTP 503 response to tell visitors that the store is temporarily unavailable. On a server you manage, enable maintenance mode from the Magento installation directory with bin/magento maintenance:enable.
Maintenance mode is separate from Magento’s developer and production modes, which control how Magento runs. The standard command-line instructions are followed by guidance on temporary IP exemptions and verification. Adobe Commerce on Cloud infrastructure uses a different deployment approach.
Connect to the server and go to the directory containing Magento’s bin folder. Run the commands as the Magento file-system owner, the operating-system account that owns Magento’s files and runs its command-line tools. Adobe requires Magento to be installed before you use these commands. See Adobe’s maintenance mode instructions.
cd
bin/magento maintenance:status
bin/magento maintenance:enable
# Perform the maintenance work.
bin/magento maintenance:disable
bin/magento maintenance:status
The first status check tells you whether maintenance mode is active. The final check confirms that Magento has returned to normal operation. If the shell reports that bin/magento cannot be found, make sure you are in the Magento installation directory. Adobe also documents running the command from the bin directory or using the full path to the CLI file in its on-premises installation instructions.
Magento uses the var/.maintenance.flag file to activate its built-in maintenance response. After you enable maintenance mode, test the storefront in a browser or with a client that does not use an exempted IP address. To check the HTTP headers, run:
curl -I https://store.example/
A 503 response indicates that the request reached the maintenance response. A browser test also confirms what a visitor sees. A proxy or cache in front of Magento can affect what the client receives, so check the actual storefront path used by customers.
Magento lets specified client IP addresses bypass the maintenance page. Add each address with a separate --ip option when enabling the mode:
bin/magento maintenance:enable --ip= --ip=
Replace the placeholders with the public IP addresses you will use to reach the store. Also test from a connection that is not exempt. An exempt address sees the storefront, which can make maintenance mode appear inactive.
To clear the exemption list, run:
bin/magento maintenance:allow-ips --none
You can also clear the list while enabling maintenance mode with bin/magento maintenance:enable --ip=none. That command keeps maintenance mode on; use bin/magento maintenance:disable when the work is complete and the store should reopen.
After enabling maintenance mode, Adobe instructs operators to stop message-queue consumer processes. These background processes handle queued work outside normal storefront requests. On a multi-node installation, stop the consumers on each node, as described in Adobe’s maintenance instructions.
You can look for consumer processes with:
ps -ef | grep queue:consumers:start
Use the process manager that runs the consumers, such as a service supervisor or container platform, to stop them. Adobe’s documentation shows kill <process_id> as an example, but the process manager might restart a consumer that you stop directly. Confirm that the consumers stay stopped before starting work that requires them to be inactive.
On Adobe Commerce on Cloud infrastructure, follow the Cloud deployment process instead of manually toggling maintenance mode on a remote environment. Adobe’s Cloud deployment best practices say Cloud deployments enter maintenance mode during the deploy phase and remove it after a successful deployment. Its application mode guidance warns against manually changing application modes or editing app/etc/env.php for this purpose.
If a Cloud storefront still shows cached pages after you enable maintenance mode, Adobe’s Cloud troubleshooting instructions recommend connecting to the environment and clearing the Magento cache:
php bin/magento cache:clean
That remedy applies to the documented Cloud issue; check your hosting setup before treating it as a general fix for other Magento installations. See Adobe’s Cloud maintenance-mode troubleshooting.
Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.
Take a look at vroni.com