Server Assets

The Server assets page combines deployment records with monitoring and delivery information. It does not directly manage every file or service on the remote host.

Prerequisites

• At least one successful deployment or registered asset
• Stored SSH information for connectivity testing
• Collected delivery data for performance metrics

Find an asset

1. Open Server assets.
2. Search by IP address, domain, or hostname.
3. Filter by server type.
4. Filter by deployment batch.
5. Clear filters when the expected server is not visible.

Summary cards show total assets, type distribution, healthy assets, and assets requiring attention.

Understand asset health

The interface combines several signals:

• connectivity has not failed;
• SMTP is configured or ready;
• recent delivery rate is unknown or above the application's healthy threshold.

A gray connectivity dot means not tested, not failed. A missing delivery percentage means no data has been collected for that range.

Test connectivity

Test one server

1. Select the connectivity action on the server row or detail drawer.
2. Wait for the result.
3. Review latency or the returned error.

Test all visible assets

1. Select Test all.
2. Watch the completed/total counter.
3. Stop the test if the chosen scope is wrong.
4. Review failed rows and rows without SSH credentials separately.

Results:

• green: the SSH connectivity test succeeded;
• red: the test failed and includes an error;
• gray: not tested or no usable SSH credential.

Enable monitoring

1. Locate the server row.
2. Turn on Monitor.
3. Wait for the setting to save.
4. If saving fails, the switch returns to its previous value.

Monitoring determines whether the server participates in supported log-collection workflows. It does not repair a remote server.

Inspect details

Open the asset detail drawer to review:

• IP, hostname, and server type;
• batch name;
• SSH user and port;
• connectivity status and latency;
• SMTP status;
• recent sent, bounced, and delivery-rate totals;
• the most recent connection error.

Remove assets

1. Select one or more assets.
2. Choose Delete.
3. Review the exact IP list.
4. Confirm only after reading the impact statement.

Deleting an asset:

• removes it from MailFleet's server list, local asset table, and monitoring registration;
• preserves credential records;
• does not connect to the remote host to uninstall services;
• does not delete remote mail data.

This local deletion cannot be undone from the asset page. Re-register through an authorized deployment or recovery process if necessary.

Troubleshooting

No SSH credentials

The server can remain in the inventory, but MailFleet cannot test or collect logs until authorized connection information is available.

Connection refused or timed out

Check server power, routing, SSH port, firewall rules, source-IP restrictions, and the SSH service.

Healthy summary differs from expectation

Run connectivity tests, collect current delivery data, and inspect SMTP state. Summary health combines these signals rather than relying on one field.

Next steps

• Collect delivery logs
• Review credentials