Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The reliable way to move Magento from localhost to an Nginx VPS is to migrate four things together: the Magento codebase, deployment configuration, media and generated assets, and a consistent database export. You then reconnect environment-specific settings, change both base URLs, point Nginx at Magento’s pub directory, deploy static content, and test the live stack before changing DNS.
Treat the move as a controlled cutover rather than a file copy. Record the local installation first, prepare a compatible VPS, freeze writes while taking the final database dump, keep the local store and a verified backup available, and do not send production traffic until checkout, Admin, media, search, cron, queues, cache, email, and HTTPS have all passed validation.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →What a Magento localhost-to-VPS migration actually moves
A Magento installation is not just a directory and a MySQL database. The destination must have the application files, the Commerce deployment configuration, user-uploaded media, any generated or published assets required by the release, and services such as PHP-FPM, the database, search, cache, and message queues when the project uses them.
- Application code: the Magento release, custom modules, themes, and any project-specific libraries.
- Shared deployment configuration:
app/etc/config.php, which records enabled modules and deployment configuration shared by environments. - Installation-specific configuration:
app/etc/env.php, which contains values that normally change between localhost and the VPS, including database connection details and cryptographic settings. - Assets:
pub/media(includingpub/media/wysiwyg), generated files, and the static content required by the production build. - Database: catalog, customers, orders, configuration, users, and extension data in a transactionally consistent dump.
- Runtime services: the supported PHP version with PHP-FPM, database engine, search service, cache/session backends, cron, and queues required by this Magento release.
Adobe describes config.php and env.php together as the Commerce deployment configuration: they are created during installation and are required to start the application. Preserve the shared file, but adapt the environment-specific file for the VPS.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Local installation versus VPS responsibilities
| Area | What you carry over | What you configure on the VPS |
|---|---|---|
| Code | Magento code, custom modules, themes, and project libraries | Destination Magento root and release-appropriate file permissions |
| Configuration | app/etc/config.php and the settings that should remain shared |
app/etc/env.php values for the VPS database, cache, sessions, and cryptographic key |
| Content | pub/media, WYSIWYG uploads, generated assets, and required static files |
Ownership by the Magento filesystem owner and Nginx access through pub |
| Data | A final consistent database dump | New database, user, permissions, import, and connection test |
| Services | Search, cache, session, queue, and cron settings discovered during inventory | Compatible service versions, credentials, workers, schedules, and firewall access |
1. Inventory localhost before preparing the server
Write down the current state before changing anything. This inventory is your compatibility checklist and your rollback reference.
- Magento edition and exact version.
- PHP version and enabled extensions.
- Database engine, version, host, database name, and user.
- Search engine and connection details.
- Cache and session backends, including whether sessions are stored in the database, files, or a separate service.
- Enabled modules, custom themes, and local patches.
- Unsecure and secure base URLs, Admin path, and any store-view-specific URLs.
- Cron jobs, queue consumers, scheduled imports, and indexing jobs.
- Payment, shipping, tax, email, search, and other integrations that use credentials or allow-listed IP addresses.
- The size of the database,
pub/media, generated directories, and static assets.
Compare this list with the Magento release’s compatibility requirements before installing the VPS stack. The PHP, database, search, and cache versions must be supported by the specific release you run; matching only the operating system is not enough.
Choose a cutover window
Pick a period when order volume is low and external integrations can be checked. Decide when to stop writes, how the final dump will be transferred, who can change DNS, and how you will roll back. Keep localhost available until the VPS has passed validation and the database backup can be restored.
2. Prepare and harden the Nginx VPS
Install a supported Linux distribution, Nginx, PHP with PHP-FPM, the supported database, and every search, cache, session, and queue service required by your release. Create a deployment user rather than performing routine Magento work as root.
- Use SSH keys and disable password-based administration where your operating-system policy permits.
- Configure a firewall that exposes only the services you actually need, normally SSH and web traffic; keep the database and internal services off the public interface.
- Plan backups that cover both the database and
pub/media, and verify that a restore is possible. - Prepare DNS for the live hostname and obtain a TLS certificate plan before cutover.
- Set monitoring and log retention for Nginx, PHP-FPM, Magento, the database, search, cache, and queues.
- Confirm disk space for the database dump, generated files, static deployment, and future media growth.
VPS selection criteria
Do not select a VPS by advertised CPU count alone. Check these items against your recorded inventory and expected workload:
| Criterion | What to verify | Why it affects the migration |
|---|---|---|
| Software compatibility | Supported PHP, database, search, and cache versions for your Magento release | An incompatible service can prevent Magento from starting or indexing correctly |
| CPU and RAM headroom | Capacity for PHP-FPM workers, indexing, compilation, cron, queues, and database activity at the same time | Deployment jobs and storefront traffic compete for resources during and after cutover |
| Storage and I/O | NVMe or equivalent performance, enough capacity for code, database, media, logs, and backups | Database imports, static deployment, indexing, and media handling are I/O-heavy |
| Backup and restore controls | Scheduled snapshots or backups, retention, and a documented restore path | A rollback is useful only when the backup can actually be restored |
| Network and region | Expected throughput, latency to customers and third-party services, and a suitable geographic region | Large media transfers and payment or shipping API calls depend on network quality |
| Access and security | Root or equivalent administrative access, SSH, firewall tooling, and TLS support | You need control over Nginx, PHP-FPM, certificates, and hardening |
| Operations support | Managed patching, monitoring, support scope, and SLA | These determine who responds when a service or disk fails |
| Magento expertise | Whether support understands Magento deployment, queues, indexing, and Nginx | Generic VPS support may not diagnose application-specific failures |
3. Freeze localhost writes and create the final backup
Users must not be able to place orders or change customer, catalog, or configuration data while you create the final dump. Put the local store into maintenance mode or otherwise stop writes, and pause jobs that could modify the database during the export.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
- Record the current time and confirm that no import, queue consumer, or scheduled job is still writing.
- Enable Magento maintenance mode using the local installation’s normal deployment procedure.
- Stop or pause local cron and queue processes for the duration of the final export.
- Dump the database with transaction consistency, triggers, and compression. Adobe’s migration example is:
mysqldump -h <database host> --user=<database username> --password=<password> --single-transaction --triggers <database name> | gzip - > /tmp/database.sql.gz - Record the dump file size and checksum, then copy it to protected storage as well as the VPS transfer location.
- Copy the application code and assets only after you know which files are generated, which are source-controlled, and which are uploaded content.
Do not expose the SQL archive through a web directory. Use an encrypted administrative transfer path and remove temporary copies after you verify the import and backup retention.
4. Transfer the Magento code and assets
Create the destination Magento root outside the public document tree, then transfer the complete application codebase. Preserve the directory structure and file contents; extensions often depend on files that are not obvious from the storefront.
Files that need particular attention
app/etc/config.phpshould travel with the deployment so the enabled-module state remains consistent.app/etc/env.phpmust be reviewed and adapted rather than blindly reused, because localhost database hosts, credentials, cache endpoints, and other environment-specific values will be wrong on the VPS.pub/mediacontains product, category, customer, and WYSIWYG uploads. Copy it completely, includingpub/media/wysiwyg.- Adobe’s production guidance identifies
generated,pub/media,pub/media/wysiwyg, andpub/staticamong production assets. Ensure the destination has the generated and static files required by your release, whether you transfer them or recreate them during deployment. - Keep custom themes, modules, patches, and any Composer metadata required to reproduce the exact codebase.
Do not make pub/media or the Magento root world-writable. After transfer, assign ownership to the deployment user or Magento filesystem owner used by your process, and allow Nginx only the read and write access Magento requires.
5. Create the VPS database and import the dump
- Install the database version supported by your Magento release.
- Create an empty destination database and a dedicated database user with the privileges Magento needs. Keep the database bound to the private interface unless the architecture explicitly requires remote access.
- Copy the compressed dump into a protected temporary directory on the VPS.
- Import it into the empty database, watching the database and disk logs for errors.
- Check that the import completed, that the expected tables exist, and that the database account can connect using the credentials you intend to place in
env.php.
Do not edit table contents casually to fix a URL or credential problem. Magento configuration can be changed with its CLI, and any direct database edit should be limited to the documented configuration rows and performed with a backup available.
6. Reconnect Magento to the VPS environment
Update the installation-specific values in app/etc/env.php, or use bin/magento setup:config:set to write the database configuration. Adobe documents the parameters --db-host, --db-name, --db-user, --db-password, and --key.
bin/magento setup:config:set --db-host=<database host> --db-name=<database name> --db-user=<database username> --db-password=<password> --key=<encryption key>Use the command form that matches your Magento release and deployment policy; do not overwrite unrelated environment settings. Review the resulting env.php for the database connection, cache and session backends, search endpoint, queue configuration, and cryptographic key. The encryption key must remain the same as the source installation when encrypted catalog, customer, or integration data must continue to decrypt.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Run Magento CLI commands as the Magento filesystem owner, not as an arbitrary root shell. If the CLI cannot bootstrap, inspect the PHP-FPM and command-line PHP versions, file permissions, database credentials, and missing PHP extensions before attempting deployment.
7. Change both Magento base URLs
Replace localhost URLs with the final hostname for every relevant website or store view. Set both unsecure and secure values; leaving one localhost value behind commonly causes redirects, broken assets, or an Admin that appears to work only from the old machine.
Free tools Windows power users keep installed
One-click scans. No signup required.
bin/magento config:set web/unsecure/base_url http://<live-hostname>/
bin/magento config:set web/secure/base_url https://<live-hostname>/Adobe documents bin/magento config:set for paths such as web/unsecure/base_url. If a value is scope-specific, make the change at the correct website or store-view scope rather than assuming the default scope controls every storefront. The corresponding settings are stored in the core_config_data table, but the CLI is preferable because it records the intended configuration change through Magento’s own interface.
Use the exact public hostname, including the trailing slash expected by Magento. If the site will force HTTPS, configure the secure URL and the Nginx redirect deliberately; do not create a redirect loop by pointing one URL at localhost or by applying conflicting proxy headers.
8. Configure Nginx and PHP-FPM for Magento
Start from Magento’s nginx.conf.sample rather than a generic PHP site configuration. Set $MAGE_ROOT to the directory containing the Magento application, include the sample configuration from the server block, and connect the PHP upstream to the PHP-FPM socket or endpoint used by the VPS.
Why the document root must be pub
Set Nginx’s public document root to the Magento pub directory. This allows the web server to serve static assets and the front controller while preventing direct browser access to sensitive directories such as app, var, and configuration files. Pointing Nginx at the project root is a security mistake even if URL rewrites appear to work.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Apply the server configuration safely
- Set the server name to the live hostname and the root to
$MAGE_ROOT/pub. - Include the Magento Nginx sample and verify that its path matches the installed release.
- Set the PHP-FPM upstream to the actual socket or listener configured on the VPS.
- Configure the TLS server separately from the HTTP-to-HTTPS redirect, using the certificate and private key locations approved by your operating-system policy.
- Test the Nginx configuration before reloading it. If the test fails, correct syntax, file paths, certificate permissions, or the PHP-FPM endpoint before sending traffic.
- Reload Nginx and restart or reload PHP-FPM after confirming the service names and pool configuration.
Keep Nginx, PHP-FPM, and Magento logs available during the first request. A 502 generally points to the PHP-FPM connection or process pool; a 404 for every route often indicates the wrong root or missing Magento rewrite rules; a 403 can indicate ownership or restrictive permissions.
9. Deploy code, static content, and caches
After the database and web server are connected, perform the release-specific deployment steps as the Magento filesystem owner.
- Set production mode where appropriate for the live store.
- Run
bin/magento setup:upgradeso the database schema and data patches match the transferred code. - Compile dependency-injection code and deploy static content when required by the release and mode. Use the locale and deployment options that match the store’s configured languages.
- Flush Magento caches after configuration, URL, and deployment changes. Also clear or warm any external cache service used by the environment.
- Confirm that the generated and static directories are readable by Nginx and writable by the Magento filesystem owner where Magento needs to regenerate files.
- Restart or reload PHP-FPM and Nginx, then inspect their logs for startup errors.
Do not run compilation or static deployment as root and then leave root-owned files in the application tree. That pattern often makes the first later cache flush or cron run fail with a permissions error.
Recommended Free Tools
10. Validate the VPS before DNS cutover
Test the VPS directly with the intended hostname, a temporary hosts-file entry, or another controlled method before changing public DNS. Validation must cover the functions that a simple homepage request cannot prove.
- Storefront: home page, category pages, product pages, search, layered navigation, and store-view switching.
- Admin: login, dashboard, configuration save, user permissions, and the correct Admin URL.
- Customer accounts: registration, login, password reset, address book, and session persistence.
- Checkout: cart, tax, shipping rates, payment authorization, order placement, confirmation email, and order visibility in Admin.
- Media and static files: product images, WYSIWYG images, CSS, JavaScript, fonts, and cache-busted static URLs.
- Integrations: payment, shipping, tax, email, analytics, ERP, imports, and webhooks. Recheck allow-listed IP addresses and credentials.
- Background work: cron schedules, queue consumers, indexers, search service, cache backend, and session storage.
- HTTPS: certificate validity, HTTP-to-HTTPS behavior, secure cookies, canonical URLs, and the absence of mixed-content errors.
- Observability: Nginx access and error logs, PHP-FPM logs, Magento logs, database errors, disk usage, and service health.
Place a real test order only when payment and fulfillment teams are ready to void or refund it. Confirm that the order reaches every downstream system before declaring the migration complete.
11. Cut over DNS and monitor the first live requests
- Confirm the final database dump is backed up independently and that the VPS validation checklist is complete.
- Disable maintenance mode only when the VPS is ready to accept users and the DNS change is being made.
- Update DNS to the VPS address according to your DNS provider’s procedure.
- Watch Nginx, PHP-FPM, Magento, database, search, and queue logs while traffic shifts.
- Check the storefront, Admin, checkout, email, and payment notifications again from an external network.
- Keep localhost stopped or read-only so an operator cannot accidentally place new orders in the old database.
DNS propagation means some users can still reach the old address for a period. Do not treat the first successful request on the VPS as proof that every resolver has switched; monitor both environments and keep the rollback plan active until traffic has converged.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Common migration failures and precise fixes
Magento still redirects to localhost
Check both secure and unsecure base URLs at the correct scope, flush Magento and external caches, and inspect the database configuration for a store-view value that overrides the default. Also check whether a reverse proxy or Nginx redirect contains the old hostname.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
CSS, JavaScript, or images return 404
Verify that Nginx serves $MAGE_ROOT/pub, that the static and media directories were transferred or redeployed, and that the generated URL uses the live hostname. Re-run the release-appropriate static deployment as the Magento filesystem owner, then flush caches.
The homepage returns 502 Bad Gateway
Check that PHP-FPM is running, that Nginx points to the actual PHP-FPM socket or listener, and that the pool has enough workers and permission to access the application. Review the Nginx error log and PHP-FPM log together; changing Magento code will not fix a broken upstream connection.
Database connection errors prevent bootstrap
Compare env.php with the database host, name, user, and password created on the VPS. Test the same credentials from the VPS, confirm the database service is listening on the expected private interface, and verify that the user has privileges on the imported database.
Admin or checkout fails after login
Check secure base URLs, HTTPS certificate and proxy headers, cookie domain and path behavior, session storage, cache configuration, and the encryption key. A changed key can make previously encrypted values unreadable.
Permission errors appear during cache flush or cron
Find files created by root or the wrong deployment account, restore ownership to the Magento filesystem owner, and ensure Nginx has only the access it needs. Run future Magento commands consistently as the same owner.
Search, queues, or cron are silent
Confirm that the required service is installed and reachable from the VPS, credentials were adapted from localhost, cron is scheduled for the deployment user, and queue consumers are running where the project requires them. Check service-specific logs rather than relying only on the storefront.
Rollback if validation fails
Rollback is a controlled return to the last known-good environment, not an attempt to merge two databases. Keep the original localhost database untouched after the final dump. If a serious defect appears after DNS cutover, direct DNS back to localhost or the previous server, place the VPS in maintenance mode, and preserve its logs and database state for diagnosis.
If orders or other writes reached the VPS after cutover, do not simply switch traffic back and continue accepting orders in both locations. Decide which database is authoritative, restore the chosen backup if necessary, and reconcile any transactions with the people responsible for payments and fulfillment. Once the VPS is corrected, repeat the final dump, transfer, URL, deployment, and validation sequence.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesQuick Recap
Final migration checklist
- Magento, PHP, database, search, cache, and queue versions are compatible.
- SSH, firewall, backups, monitoring, DNS, and TLS plans are in place.
config.php,env.php, code, media, generated assets, and static assets are present in the correct locations.- The database dump was consistent, transferred securely, imported successfully, and backed up independently.
- Database credentials and other environment-specific values point to the VPS.
- Both base URLs use the live hostname.
- Nginx uses Magento’s sample configuration, PHP-FPM is connected, and the document root is
pub. - Upgrade, compilation, static deployment, cache flush, ownership, and service reloads completed without errors.
- Storefront, Admin, customer accounts, checkout, media, email, integrations, cron, queues, search, cache, HTTPS, and logs have been tested.
- DNS was changed only after validation, and the local instance and backup remain available for rollback.
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.
