Free tools Windows power users keep installed
One-click scans. No signup required.
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
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
You can self-host phpIPAM on a VPS with either a native Apache/Nginx stack or the maintained Docker images. For most small teams, a native install is easiest to understand and back up; Docker is preferable when you already operate containers and need repeatable packaging. In both cases, use a supported PHP runtime, MySQL-compatible database, HTTPS, filtered reverse-proxy headers, and tested daily backups. phpIPAM 1.8.2 is the current release identified in the project documentation.
This guide covers the requirements, architecture decision, installation sequence, reverse-proxy security, Docker-specific rules, API enablement, and recovery procedures needed for a production deployment.
Recommended Free Tools
What phpIPAM does and what a VPS deployment includes
phpIPAM is an open-source web IP address management application. It stores address space, subnets, VLANs, folders and related metadata in a SQL database, then presents that information through a browser and REST API. The application itself is not a DHCP server or a replacement for your network equipment; it is the authoritative inventory and planning layer you operate alongside those systems.
A self-hosted installation has four moving parts:
- Web tier: Apache with PHP or Nginx with PHP-FPM serves the application.
- PHP runtime: PHP and the extensions required by the release provide sessions, database access, encryption, LDAP integration and optional network-scanning functions.
- Database: MySQL or MariaDB stores the schema and all IPAM data.
- Persistent operations: HTTPS termination, scheduled backups, log monitoring, updates and (if used) a separate cron process.
The VPS must have a stable hostname or IP, firewall rules that expose only the services you need, and enough storage for the database and backup retention policy. A small deployment can run all native components on one VPS. Larger installations can separate the database, web front end and proxy, but that adds operational work rather than changing phpIPAM’s data model.
#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.
Check versions and prerequisites before installing
The installation guide still contains a legacy statement that MySQL 5.1 or newer is acceptable. That minimum is not appropriate for a current production release. Repository guidance for modern phpIPAM versions makes MySQL 5.7.7 or newer mandatory when using the utf8mb4 character set. MySQL 8.0 or newer, or MariaDB 10.2.1 or newer, is highly recommended because common table expression support is expected by current code paths. Select the database version first; upgrading the database after importing a live schema is more disruptive than choosing a supported version initially.
Native-stack requirements
Install one of the supported web-server combinations: Apache2 with PHP, or Nginx with PHP-FPM. The documented PHP modules are:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- PDO and PDO MySQL
- Sessions
- Sockets
- OpenSSL
- GMP
- LDAP
- Crypt
- SimpleXML
- JSON
- Gettext
- Filter
- mbstring
- PEAR
- pcntl and the CLI package when network scanning is required
Package names differ between Linux distributions and PHP versions, so verify that each extension is loaded by the same PHP binary used by the web server. A command such as php -m checks the CLI runtime; also inspect the PHP-FPM pool or Apache module used by the site. If an extension appears in the CLI output but not in the web runtime, restart PHP-FPM or Apache after installing it and check the web server’s PHP information page before running the installer.
Database account and character set
Create a dedicated database and account rather than allowing phpIPAM to use a shared administrative login. Give that account privileges on its own phpIPAM database so it can create and alter application tables during installation and upgrades, but do not grant global privileges such as SUPER or access to unrelated databases. Use utf8mb4 from the beginning; changing collation after users and network data exist is an avoidable migration.
Docker prerequisites
The maintained image separates the browser-facing phpipam-www frontend from a phpipam-cron container. Rootless Docker is unsupported. The frontend can be replicated and load-balanced, but exactly one cron container should run for a given installation. Running two cron containers can duplicate scheduled work.
Ping and SNMP discovery require the container capabilities NET_ADMIN and NET_RAW. In Kubernetes, the pod security context must allow allowPrivilegeEscalation=true for those capabilities to function. If discovery is not needed, do not add capabilities merely because an example compose file contains them.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRank #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
Choose native installation or Docker
Both deployment styles use the same phpIPAM application and database concepts. The practical differences are operational.
| Decision area | Native Apache/Nginx deployment | Docker deployment |
|---|---|---|
| Operational complexity | Fewer layers on a single VPS; you manage the operating system, PHP packages and web server directly. | Packaging is consistent, but you also manage image lifecycle, volumes, container networking and a separate cron role. |
| Upgrades | Pull the new application code, review configuration changes, run the documented database upgrade and restart the web service as needed. | Pull a tested image tag, recreate the frontend and cron containers, preserve volumes, and follow the image’s upgrade notes. |
| Isolation | PHP and web-server packages share the host with other services and are exposed to host-level configuration changes. | Application dependencies are packaged in containers; the kernel, Docker daemon and mounted volumes remain host responsibilities. |
| Backup layout | Back up the MySQL/MariaDB database and configuration files, plus any uploaded or persistent application data. | Back up the database and every persistent volume used for configuration or application state; a container image alone is not a backup. |
| Reverse proxy | Terminate TLS in Apache or Nginx directly, or place another proxy in front and configure the site’s URL base. | Terminate TLS in a proxy and forward traffic to the frontend container; keep forwarded-header trust restricted to that proxy. |
| Network discovery | Runs with the host’s normal network privileges and PHP CLI permissions. | Requires NET_ADMIN and NET_RAW for ping and SNMP functions; Kubernetes also needs allowPrivilegeEscalation=true. |
Choose native when this is your first phpIPAM service, the VPS already runs a conventional LEMP or LAMP stack, or you want the fewest components to troubleshoot. Choose Docker when your team already deploys and monitors containers, needs repeatable image-based rollouts, or plans to scale the web frontend independently. Docker does not remove the need for a database, backups or secure proxy configuration.
Install phpIPAM natively on the VPS
1. Prepare the host
- Apply operating-system security updates and set the VPS hostname and time zone.
- Configure the firewall to allow SSH from your administration network and HTTPS from the Internet or your private network. Keep the database port private unless a separate database host requires it.
- Install Git, your chosen web server, PHP with the extensions listed above, PHP CLI when scanning is required, and MySQL 8.0+ or MariaDB 10.2.1+.
- Create a DNS record for the hostname users will enter. Decide whether phpIPAM will be served at the domain root, such as
https://ipam.example.net/, or below a path such as/ipam; the BASE setting and rewrite rules must match that choice.
Do not expose the default web-server welcome page while you configure the application. A temporary internal-only listener or firewall restriction reduces the chance that an unfinished installer is reachable from the Internet.
2. Check out the application code
Use the official repository at https://github.com/phpipam/phpipam. Clone a release or a reviewed commit into a directory owned by the web server, rather than editing files directly in a home directory. A typical checkout is:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →git clone https://github.com/phpipam/phpipam.git /var/www/phpipam
cd /var/www/phpipamFor production, pin the checkout to the release you have tested instead of tracking an unreviewed development branch. Preserve the current configuration file before replacing application code during an upgrade.
3. Create config.php
Copy the supplied config.dist.php to config.php. Set the database host, database name, database username and password created for this installation. Set the BASE path to the exact URL prefix: an installation at the domain root uses /, while one under /ipam needs that path. Keep the file readable by the web-server account but not world-readable, because it contains database credentials.
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.
When the application is behind a proxy, do not enable forwarded-header trust yet unless the proxy is already configured to overwrite the headers described in the HTTPS section below. Incorrect BASE values usually appear as missing styles, redirect loops or links that point to the wrong path.
4. Create the database and load the schema
Create the database with utf8mb4 and grant the dedicated account privileges on that database only. Then choose one initialization method:
- SQL method: import
db/SCHEMA.sqlfrom the checked-out release using the database client. - Browser method: leave the schema empty and let the web installer create it after the web server is reachable.
Do not use both methods against the same empty database. If you imported the schema, the installer should detect an initialized database; if you use the browser installer, verify that the database account can create tables and indexes before opening the setup page.
5. Configure Apache or Nginx
Point the virtual host’s document root at the phpIPAM directory and pass PHP files to the matching PHP handler. Enable URL rewriting, because both the web interface and REST API rely on rewritten routes. Apache needs the equivalent of its rewrite module and an allowed directory configuration; Nginx needs a try_files rule that routes application paths to the front controller and a PHP-FPM socket or upstream.
Set the virtual host’s server name to the DNS name users will use and make sure the selected PHP-FPM pool can read the application files and write only the directories that phpIPAM documents as writable. Avoid making the entire checkout writable by the web-server user.
6. Complete the web installer
- Open the configured HTTPS hostname in a browser.
- Enter the database connection values and confirm the displayed BASE path.
- Let the installer validate PHP extensions, database connectivity and schema creation.
- Create the first administrator account with a unique password and, if available in your environment, multi-factor protection at the identity layer.
- Sign in and create a test section and subnet, then verify that a second user sees only the permissions you assign.
After the first successful login, disable or remove the installation helper according to the release instructions. Leaving an installer reachable is an unnecessary risk because it can expose setup functions or encourage accidental reinitialization.
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.
Deploy phpIPAM with Docker
Follow the maintained image documentation at https://hub.docker.com/r/phpipam/phpipam-www/. Build a deployment with a database service, one or more phpipam-www frontend containers, and exactly one phpipam-cron container. Put the containers on a private network and expose only the frontend through your HTTPS reverse proxy.
Supply credentials without baking secrets into images
The image accepts environment variables for database settings and also supports corresponding *_FILE variables, allowing a secret manager or mounted files to provide credentials. Prefer the file-based form in a shared VPS environment so passwords do not appear in shell history or ordinary process listings. Restrict secret-file permissions and rotate the database password through a planned maintenance window.
Persist the right data
Bind or name persistent volumes for application configuration and any state documented by the image. A container replacement must not erase configuration, and a database container must not rely on its writable layer. Record volume names and mount points in your operations documentation so a restore can recreate the same layout.
Apply capabilities only when discovery needs them
Add NET_ADMIN and NET_RAW to the container that performs ping or SNMP operations, normally the cron role. Test discovery from the same network namespace and user context that production uses. If discovery is disabled, omit these capabilities and reduce the attack surface.
Disable the installer helper
After setup, set IPAM_DISABLE_INSTALLER=1 in the frontend environment and recreate the container. Confirm that the setup endpoint is no longer usable, then record the setting in your deployment manifest so a future rollout does not accidentally remove it.
Scale only the frontend
Multiple frontend replicas can sit behind a load balancer when they share the same database and persistent configuration. Do not scale the cron role horizontally; keep one active scheduler. Health checks should test an authenticated-safe endpoint or a lightweight application response rather than performing a write on every probe.
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.
Put HTTPS and a reverse proxy in front
Use HTTPS for every login and API request. You can terminate TLS in Apache or Nginx on the VPS, or place a dedicated reverse-HTTPS proxy in front of a container deployment. Redirect plain HTTP to HTTPS and renew certificates before expiry. Keep the backend listener private when a separate proxy is used.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteForwarded-header trust is conditional
The phpIPAM README states that, as of v1.6.0, an installation behind a reverse proxy can set $trust_x_forwarded_headers = true in config.php. Enable it only when the trusted proxy strips and overwrites client-supplied forwarding headers on every request. The proxy must filter or replace:
X_FORWARDED_FORX_FORWARDED_HOSTX_FORWARDED_PORTX_FORWARDED_PROTOX_FORWARDED_SSLX_FORWARDED_URI
Leaving these values under end-user control can enable abuse and produce login loops, incorrect absolute URLs or misleading audit information. Restrict the backend so users cannot bypass the proxy and submit crafted headers directly. If you cannot guarantee header sanitization, leave forwarded-header trust disabled and correct the proxy topology instead.
Verify the proxy path
- The browser remains on the HTTPS hostname after login.
- Static CSS and JavaScript load without mixed-content warnings.
- Redirects preserve the correct domain and BASE path.
- Client IP logging reflects the real client only after header filtering is verified.
- API requests reach the rewritten endpoint and return an authentication response rather than a generic 404.
Back up phpIPAM and prove that restoration works
The official installation guide shows a daily mysqldump job and deletion of backup files older than 10 days. Treat that retention period as an example policy, not a universal rule. Your business requirements may require longer retention, point-in-time recovery or an immutable copy.
What to back up
- The complete MySQL or MariaDB database, including schema, permissions relevant to the application and all IPAM records.
config.phpand any deployment manifests or secret references required to reconnect the application.- Docker volumes containing persistent application configuration when using containers.
- Proxy configuration, TLS certificate renewal configuration and firewall rules needed to rebuild the service.
Encrypt backup files before sending them off the VPS. Store at least one copy in separate failure domain or object storage, restrict access to the backup key, and monitor the job exit status rather than assuming a scheduled command succeeded. A backup that silently produces an empty dump is not a recovery plan.
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 →Use a restore drill
- Provision a separate test VPS or isolated database instance.
- Restore the dump and persistent configuration without connecting it to production DNS.
- Start phpIPAM at a temporary hostname and verify administrator login, subnet records, permissions, API access and any scheduled discovery jobs.
- Measure restore time and document missing files or manual steps.
- Destroy or securely reset the test instance after validation.
Run this exercise periodically and after major version changes. It is the only reliable way to discover that a volume, encryption key or configuration file was omitted from the backup set.
Use the REST API safely
phpIPAM provides a REST API with authentication, authorization and encrypted-request options for sections, subnets, folders, VLANs and other IPAM objects. The API documentation describes the available controllers and authentication flow. URL rewriting must work before API routes will function.
- Create a dedicated API identity or token with the narrowest permissions required by the automation.
- Store credentials in a secret manager, CI secret store or protected file; never commit them to scripts.
- Test reads and a small write against a non-production instance before bulk imports or address reclamation.
- Log request outcomes without logging passwords or bearer tokens.
- Rate-limit or otherwise protect the API at the proxy when an integration can generate bursts.
Troubleshoot common deployment failures
| Symptom | Likely cause | Action |
|---|---|---|
| Installer reports a missing PHP module | The extension is absent from the web PHP runtime, even if php -m shows it for CLI. |
Install the matching module, restart Apache or PHP-FPM, and check the web runtime again. |
| Database connection fails | Wrong host, port, credentials, blocked socket or an account without privileges on the selected database. | Test the same credentials from the VPS, confirm firewall and bind settings, then grant only the required rights on the phpIPAM database. |
| Tables fail during schema creation | Unsupported database version, wrong collation, insufficient DDL privileges or a partially initialized database. | Use MySQL 5.7.7+ for utf8mb4, preferably MySQL 8.0+ or MariaDB 10.2.1+, reset the empty database and initialize it once. |
| CSS is missing or links point to the wrong place | BASE path does not match the virtual-host URL or the proxy path. | Correct BASE, document root and rewrite rules, then clear browser cache and reload. |
| Login loops behind a proxy | Forwarded headers are untrusted, inconsistent or accepted directly from clients. | Sanitize all listed headers at the proxy, block direct backend access and enable trust only after those controls are in place. |
| API returns 404 while the web UI works | URL rewriting is disabled or the proxy does not pass the API path. | Enable Apache rewrite or the equivalent Nginx front-controller rule and verify proxy path forwarding. |
| Ping or SNMP discovery fails in Docker | The worker lacks NET_ADMIN/NET_RAW, Kubernetes disallows privilege escalation, or network routing blocks the target. |
Add capabilities only to the discovery worker, set allowPrivilegeEscalation=true where Kubernetes requires it, and test routing from that container. |
| Scheduled jobs run twice | More than one cron container is active. | Scale the frontend, not the cron role; stop extra schedulers and check deployment manifests. |
Production readiness checklist
- phpIPAM release and database versions are recorded; the database meets the current compatibility guidance.
- All required PHP extensions are loaded by the web runtime, with CLI extensions added if scanning is enabled.
- The database account is dedicated and limited to the phpIPAM database.
- The BASE path, rewrite rules and DNS name match the public URL.
- HTTPS is enforced and the backend cannot be reached around the proxy.
- Forwarded headers are overwritten by the proxy before forwarded-header trust is enabled.
- The installer helper is disabled after first setup; Docker uses
IPAM_DISABLE_INSTALLER=1. - Only one cron container runs, and discovery capabilities are present only when required.
- Daily encrypted database backups run, failures alert an operator, and copies exist off the VPS.
- A recent restore drill has verified database, configuration, volumes and API behavior.
- API credentials are scoped, secret and tested against a non-production instance.
Which deployment should you use?
For a single VPS managed by a small team, install phpIPAM natively behind Nginx or Apache, use a current MySQL or MariaDB release, and keep the database and application on the same private host unless you have a reason to separate them. This path has fewer moving parts and makes backup and troubleshooting straightforward. Use Docker when container operations are already routine or when independent frontend scaling and image-based rollbacks justify the extra volume, capability and cron management. Whichever path you choose, secure the proxy, disable installation helpers, and regularly demonstrate that a backup can become a working phpIPAM instance.
Quick Recap
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.
