Server, security and maintenance

Track load, memory and disk

Where to find: Server Panel → Server Metrics

The overview shows Server Load, Memory Usage, Disk Usage and Swap Memory, with features used and available. The graphics allow you to track trends beyond the instant value.

1. Check the Connected status and server details.
2. Compare load with the number of cores; observe duration and recurrence of increase.
3. See memory and swap in the same period. Recurrent Swap helps identify memory pressure.
4. Check the disk free space before uploads, installation and backups.
5. In Server Metrics, see Performance, Query Monitor or I/O Activity as per the investigation.
6. Link peak time with chronjobs, deploys, logs and processes.

See server logs and processes

Where to find it: Logs; Server Panel → Processes

Technical logs record events and errors. Activity Log records actions performed in the panel and has another purpose.

1. Open Logs and choose Select a Log File.
2. Mark I just want to see last N entries to limit the query to recent entries and fill in the quantity requested.
3. Click Fetch Logs.
4. Locate messages close to the time of the problem and identify service, path and error.
5. In the overview, open Processes to investigate the running activity. Do not close processes without identifying their function.
6. Repeat the operation after correcting the cause and check if new errors appear.

Manage PHP services and versions

Where to find: Services

The list presents Name, Status, CPU Usage, Memory Usage and Actions. In the revised environment there are OpenLiteSpeed, MariaDB, Postfix, SSH, UFW, Redis, Fail2ban and LSPHP versions.

1. Open Services and locate the component by checking Status.
2. Use the update button to confirm the recent state.
3. Pass the cursor over the action icon to check its purpose before clicking: start, stop, restart or reload as available.
4. For a PHP version indicated as Not Installed, use the installation action only after checking compatibility and features.
5. Wait for the result and check the status change.
6. Test the dependent applications and see the logs.

Understand the fields and options

Running

Service running.

Not Installed

Component not yet installed.

Action disabled

Operation not offered for that component or state. Do not try to play it by another icon.

Create and review firewall rules

Where to find it: Firewall → Create a Firewall

The rules define port, protocol, allow/block and source. The form informs that the rule is applied immediately.

1. Please refer to the existing rules and identify the service that needs to be accessed.
2. Click Create a Firewall.
3. Inform Port. For a range, mark Create a rule for range of ports and fill in start and end; for a single port, leave the end empty.
4. Choose Protocol: All, TCP or UDP.
5. Choose Traffic: Allow to allow or Deny to block. Check the selection: in the revised form, Deny was initially marked.
6. Report IP Address when you want to restrict the source and a Description that explains the rule.
7. Review and click Create Rule. Check the created line and test access from the authorized source.

Understand Fail2ban Protection

Where to find: Server Fail2ban; Application → Fail2ban

On the server, Fail2ban protects SSH login attempts and shows state and control Enable Fail2Ban. In the application, there are own jail editors and filter.

1. On the server, open Fail2ban and check if the protection is enabled.
2. By configuring the protection, review the duration of the block, attempts and observation period in the fields that appear in its enabled state.
3. Before unlocking a legitimate origin, correct the credentials that caused the repeated attempts.
4. In the application, open Fail2ban to review the Jail Configuration and Filter Configuration editors.
5. Modify only rules appropriate to the application logs. Check name, patterns and limits.
6. When using Save, the panel saves, tests the configuration and restarts Fail2ban if the test passes. Check out the result and test the protected flow.

Create and maintain a cron task

Where to find: Cronjobs → Create a Cronjob

Cron executes a command on a frequency. Use the application user and complete paths to avoid differences in relation to your terminal.

1. Click Create a Cronjob.
2. Inform Name and select Application User.
3. In Command to Execute, inform the full command and paths required by the application.
4. Select Schedule. For a custom routine, choose Custom and fill in the fields shown.
5. Check the server time zone and the expected run time.
6. Click Create Cronjob and check name, user, command, frequency, and Enabled on the list.
7. After the scheduled time, confirm the result in the application or log of the command. Use task editing or enable control for adjustments.

minuto hora dia-do-mês mês dia-da-semana
*/5 * * * *    # a cada 5 minutos
0 2 * * *      # diariamente às 02:00 no fuso do agendador

Maintain a process with Supervisor

Where to find: Application → Supervisors → Create a Supervisor

Supervisor accompanies continuous processes such as workers. It is different from cron, which triggers commands at times.

1. Open the application and click Create the Supervisor.
2. Fill in Name and Command. Check out Path App to identify the project directory.
3. Define Number of Processes according to the program's ability and behavior.
4. Choose User. Prefer the application user when the process does not require administrative privileges.
5. Check Auto Start for auto boot and Auto Restore for recovery after interruption if this corresponds to the desired behavior.
6. Configure Log File and Log Level. Adjust Extra Configuration only if you know the effect of directives.
7. Click Save Supervisor and see the list and processes. Check if the program remains active and if there are errors in the log.

Wipe disk and review swap

Where to find: Disk Cleaner; Server Panel → Swap Memory → Update Swap

Disk Cleaner provides manual cleaning and automatic cleaning control. The selection defines what can be removed.

1. Check the free space and the cause of consumption before cleaning.
2. In Disk Cleaner, choose only the necessary categories: Applications Access Log, Applications Error Log, Temp Files, Services Log, Auto Clean and Journal Log.
3. Preserve necessary logs for investigation and important copies.
4. Review the selection before Save and Clean up: the action removes content, not only saves preferences.
5. For automatic cleaning, check the effect and fields displayed when enabling control.
6. Update the metrics after cleaning. For swap, open Update Swap and review the size offered before confirming a change.

See the stock history

Where to find it: Activity Log

The table shows Type, Action, Activity, IP Address and Date & Time. Use it to relate panel changes to an incident.

1. Open Activity Log.
2. Update the list and use the filter when you need to limit the period or type of action.
3. Check out description, origin and time of operation.
4. Compare with technical logs and the time of the problem.
5. Only record the information necessary for assistance, protecting personal data.

Locate alerts and team resources

Where to find: Client area or environment-enabled features

The consulted panel menu did not display alert pages, notification channels or staff. Do not use old paths as if these screens were present.

Permissions and organisation of projects

Where to find: Application Users; server/application names and tags

In this panel, organize projects by name, tags and system user. Account member management is a separate procedure.

1. Use names that identify design and environment, such as shop-production and shop-test.
2. Check out the system user associated with each application.
3. Use the actions of adding tags to group items when needed.
4. Review remote accesses and user privileges when the team changes.