Mideye Fleet requirements: Ports, Database, Versions
Check these points before you install Mideye Fleet.
| Suggested minimum | Recommended | |
|---|---|---|
| Operating system | Ubuntu 24.04 LTS or 26.04 LTS, x86-64 (both tested with the quickstart) | Same |
| CPU | 2 vCPU | 4 vCPU |
| Memory | 4 GB | 8 GB |
| Disk | 30 GB | 60 GB |
- The sizes are for the Docker quickstart, which also runs Mideye Server and a database. The minimum is an estimate, not a tested size.
- This version supports Fleet in Docker on Ubuntu. Fleet on Windows Server is planned for the next version.
- The Fleet image is for Linux on x86-64 only.
- Fleet itself is light. Customers usually run 10 to 300 computers. In a test, one Fleet on SQLite took 1,000 simulated computers reporting at once without a failed call. There is no measured minimum for a smaller host, so size the disk from your event retention (below).
- Fleet needs a correct clock. Use NTP. In an air-gapped network, use an internal NTP source.
- Keep the data volume and the backups on storage that is itself backed up.
Network
Section titled “Network”Open these ports.
| From | To | Port | Why |
|---|---|---|---|
| Administrator’s browser | Fleet | 9443/tcp | The web interface, over HTTPS. |
| Each computer (Mideye Agent) | Fleet | 9444/tcp | Join, policy, status, events and certificate renewal. After the join it uses mutual TLS. |
| Fleet | Mideye Server | the port in the server’s URL, usually 8443/tcp | Token management, health checks and the server test. |
| Fleet | Database server | 3306/tcp (MariaDB, MySQL) or 1433/tcp (SQL Server) | Only when you do not use SQLite. |
| Prometheus | Fleet | 9443/tcp | Only when you switch on the metrics endpoint. |
| Fleet | Your log targets | the port of each target | Only for the log targets you add. |
| Fleet | downloads.mideye.com | 443/tcp | Optional. Fleet looks for updates and can fetch the endpoint installer. Switch it off in Settings if you do not want it. |
- Fleet never connects to a computer. The agent on each computer always calls Fleet.
- The install command on the computers does not work through a proxy. Open port 9444 from the computers to Fleet.
- Fleet does not call Mideye Cloud. Computers reach Mideye Cloud or their Mideye Server themselves.
- Fleet refuses a Mideye Server at a loopback or link-local address, such as
127.0.0.1. A Mideye Server on the same host as a Fleet container needs an address that the container can reach. - With Docker, publish port 9444 only on the address that your computers use. Docker publishes on all addresses and goes around the host firewall.
DNS name and certificate
Section titled “DNS name and certificate”- Give Fleet a DNS name from day one, for example
fleet.example.com. Use it intls.hostnames, in Settings, Fleet Server URLs and so on. Moving Fleet later is then a DNS change. - Fleet makes its own certificate authority and certificate. Computers pin Fleet’s authority from the join file, so they do not need your company certificate.
- Administrators can replace the certificate of the web interface (port 9443) with their own under Fleet Server, GUI certificate. Port 9444 always uses Fleet’s own authority.
Database
Section titled “Database”Fleet uses SQLite by default. It also runs on these engines.
| Engine | Tested versions |
|---|---|
| SQLite (built in, the default) | Nothing to install. |
| MariaDB | 10.3 and 11.4 |
| MySQL | 8.0 and 8.4 |
| Microsoft SQL Server | 2019, 2022 and 2025 |
- SQL Server 2019 and 2022 run in Fleet’s automated database tests. SQL Server 2025 had a short start-up test only. SQL Server Express has not been tested with Fleet.
- PostgreSQL is not supported.
- Fleet needs its own, empty database. Never use the database of Mideye Server. One database server can host both.
- The database user needs rights to create tables at the first start and to read and write data afterwards. The exact grants are in the Fleet installation guide.
- There is no tool that moves an existing Fleet to another database engine. Choose the engine before you join many computers.
- Events are kept for 90 days by default (7 to 3,650 days). Older events are deleted every day. The audit log is never deleted.
Mideye Server
Section titled “Mideye Server”For on-premises mode, Fleet needs a Mideye Server with Fleet Provisioning on the Authentication API endpoint. Mideye Server 6.6.11, which the Docker quickstart installs, has this, and the quickstart sets it up for you. The details are in the Fleet installation guide.
Use one Authentication API endpoint for each Fleet. If two Fleets share one endpoint, they see each other’s tokens.
Computers and endpoint versions
Section titled “Computers and endpoint versions”- The computers run the Mideye endpoint. The endpoint was tested on Windows Server 2019, 2022 and 2025.
- Use endpoint 0.24.52 with Fleet 0.27.0.
- Upgrade Fleet first, then the endpoints. A new endpoint can report things that an old Fleet refuses.