Events

Events in FlashPanel are background tasks that track the execution of operations performed on your servers and websites. Every action you perform through the control panel creates an event that you can monitor in real-time.

What are Events?

Events represent asynchronous operations that are executed on your servers. When you perform an action like:

• Installing an application
• Creating a website
• Updating PHP settings
• Deploying code
• Creating a database
• Installing SSL certificates

FlashPanel creates an event that tracks the progress and result of that operation. This allows you to:

• Monitor the progress of long-running operations
• Review the execution output and logs
• Troubleshoot failed operations
• Track who performed specific actions and when

Accessing Events

You can access the Events page in two ways:

1. Global Events Page: Click on "Events" in the main navigation to see all events across all your servers
2. Server Events: Navigate to a specific server and click "Events" in the server sidebar to see events for that server only

Event Information

Each event displays the following information:

Event Details

• ID: Unique identifier for the event
• Server: The server where the event was executed
• User: The user who triggered the event (with their avatar)
• Event Description: A human-readable description of what the event does
• Status: Current status of the event (Pending, Running, Success, Failed)
• Created At: When the event was created
• View Log: Button to view the detailed output/log of the event execution

Event Statuses

Events can have the following statuses:

Pending

The event has been queued and is waiting to be executed. Events are processed in order, so your event may be waiting for other events to complete first.

Indicator: Gray/neutral color

Running

The event is currently being executed on your server. You can view the live output by clicking the "View Log" button.

Indicator: Blue/info color with progress animation

Success

The event completed successfully without any errors. All operations were performed as expected.

Indicator: Green/success color

Failed

The event encountered an error and could not complete. You should check the event log to understand what went wrong.

Indicator: Red/error color

Viewing Event Logs

To view the detailed output of an event:

1. Click the "View Log" button in the event row
2. A modal will open showing the complete execution log
3. The log contains:
   • Command outputs
   • Error messages (if any)
   • Step-by-step progress information
   • Execution time details

The log is especially useful for:

• Debugging failed operations
• Understanding what changes were made to your server
• Verifying that operations completed as expected

Filtering Events

On the global Events page, you can filter events by:

By Server

Use the server dropdown in the top-right corner to show only events from a specific server. This is useful when you manage multiple servers and want to focus on one.

Event Execution Order

Events are executed in a queue system:

1. Sequential Execution: Events for the same server are executed one at a time in the order they were created
2. Parallel Servers: Events on different servers can run simultaneously
3. Priority: System-critical events may have higher priority
4. Timeout: Events have a maximum execution time to prevent hanging operations

Troubleshooting Failed Events

If an event fails, follow these steps:

1. Check the Event Log

Click "View Log" to see detailed error messages. Common issues include:

• Permission errors: The system user doesn't have required permissions
• Network errors: Cannot connect to external services (Git, package repositories)
• Disk space: Server is out of disk space
• Service conflicts: Another service is using the required port or resource
• Syntax errors: Configuration files have invalid syntax

2. Common Solutions

Permission Issues

# Check file permissions
ls -la /path/to/directory

# Fix ownership
chown -R user:user /path/to/directory

Disk Space Issues

# Check disk usage
df -h

# Clean up space (via Events page or manually)

Service Conflicts

# Check what's using a port
netstat -tuln | grep :80

# Stop conflicting service
systemctl stop service-name

3. Retry the Operation

After resolving the issue:

1. Navigate back to the feature that triggered the event
2. Try the operation again
3. Monitor the new event to ensure it succeeds

4. Contact Support

If you can't resolve the issue:

1. Copy the event log
2. Note the event ID and description
3. Contact FlashPanel support with this information

Best Practices

Monitor Critical Events

Always check the status of important operations:

• Server installations
• Application installations
• SSL certificate installations
• Database imports
• Production deployments

Review Failed Events Promptly

Don't ignore failed events, as they may indicate:

• Configuration problems
• Security issues
• Resource constraints
• Service outages

Keep Event Logs

Event logs are valuable for:

• Auditing changes
• Troubleshooting issues
• Understanding system behavior
• Compliance requirements

Don't Overwhelm the Queue

Avoid triggering too many operations simultaneously:

• Queue events intelligently
• Wait for critical operations to complete
• Spread large operations across time

Event Retention

Events are stored in your FlashPanel account with the following retention policy:

• Retention Period: Events are kept for 3 months
• Log Storage: Event logs (output) are cleared after 3 months to save storage space
• Event Data: Basic event information (ID, description, status, timestamps) is retained after log cleanup
• Important Events: Events linked to specific resources (servers, sites, databases) may retain their basic information for historical tracking
• Automatic Cleanup: Old events are automatically pruned to maintain system performance

Event Notifications

You receive notifications for events through:

• In-App Notifications: Real-time notifications in the FlashPanel interface
• Browser Notifications: Desktop notifications when events complete (if enabled)
• Status Indicators: Visual feedback on operation progress

Pro Tip

Enable browser notifications to stay informed about long-running operations even when you're working in other tabs or applications.

Understanding Event Output

Event logs contain valuable information:

Command Execution

# Commands executed
sudo apt-get update
sudo apt-get install -y nginx

# Command output
Reading package lists... Done
Building dependency tree... Done
nginx is already the newest version

Progress Indicators

Step 1/5: Downloading files...
Step 2/5: Installing dependencies...
Step 3/5: Configuring service...
Step 4/5: Starting service...
Step 5/5: Verifying installation...

Error Messages

Error: Port 80 is already in use
Failed to start nginx.service: Unit nginx.service failed to load

Success Confirmation

✓ Installation completed successfully
✓ Service started and enabled
✓ Configuration verified