| Server IP : 167.235.224.122 / Your IP : 216.73.216.110 Web Server : Apache/2.4.58 (Ubuntu) System : Linux newplayground 6.8.0-136-generic #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:33:11 UTC 2026 aarch64 User : deploy ( 1000) PHP Version : 8.4.23 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : OFF Directory : /var/www/html/emajiwallet/ |
Upload File : |
# 500 Error Handling Setup
**Date:** January 5, 2026
**Status:** ✅ Complete
## Overview
Implemented custom 500 error page with automatic email notifications to the development team when server errors occur in production.
## Components Created
### 1. Custom 500 Error Page
**File:** `resources/views/errors/500.blade.php`
**Features:**
- Beautiful, user-friendly error page with modern design
- Animated error icon
- Environment-aware messaging:
- **Production:** Shows ticket creation notice
- **Development:** Shows development mode notice
- Return to home button
- Support contact link
### 2. Exception Handler
**File:** `app/Exceptions/Handler.php`
**Features:**
- Automatically sends email notifications for 500 errors
- **Only sends emails in production environment**
- Skips notifications for common non-critical errors:
- Authentication errors (401)
- Validation errors (422)
- Not found errors (404)
- Other HTTP exceptions
- Includes comprehensive error details in email
- Falls back to logging if email sending fails
### 3. Error Notification Email Template
**File:** `resources/views/emails/error-notification.blade.php`
**Includes:**
- High priority indicator
- Error message
- File and line number
- Request details (URL, method, IP, user agent, user ID)
- Full stack trace
- Timestamp
## Configuration
### Email Recipient
Errors are sent to: **jm@emaji.net**
To change the recipient, edit line 75 in `app/Exceptions/Handler.php`:
```php
$message->to('jm@emaji.net')
```
### Environment Detection
The system automatically detects the environment:
- **Production:** Sends emails and shows "ticket created" message
- **Development/Local:** No emails sent, shows development notice
## How It Works
1. **User encounters a 500 error** → Custom error page is displayed
2. **In production only:**
- Exception handler captures the error
- Email notification is sent to jm@emaji.net
- Error is logged
- User sees "ticket created" message
3. **In development:**
- User sees development mode notice
- No email sent
- Error details visible in logs/debug mode
## Email Notification Contains
- **Error Message:** What went wrong
- **Location:** File path and line number
- **Request Details:**
- Full URL
- HTTP method
- IP address
- User agent
- Logged-in user ID (if authenticated)
- Timestamp
- **Stack Trace:** Full error stack for debugging
## Testing
### Test in Development (No Email Sent)
```php
// Add to any route temporarily
throw new \Exception('Test 500 error');
```
### Test in Production (Email Will Be Sent)
```bash
# Set environment to production in .env
APP_ENV=production
```
Then trigger an error. You'll receive an email at jm@emaji.net.
## Mail Configuration Required
Ensure your `.env` has proper mail configuration:
```env
MAIL_MAILER=smtp
MAIL_HOST=your-smtp-host
MAIL_PORT=587
MAIL_USERNAME=your-username
MAIL_PASSWORD=your-password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=noreply@emaji.net
MAIL_FROM_NAME="${APP_NAME}"
```
## Customization
### Change Error Page Styling
Edit `resources/views/errors/500.blade.php` CSS variables:
```css
:root {
--ios-red: #FF3B30;
--ios-blue: #007AFF;
--ios-gray: #8E8E93;
}
```
### Add More Recipients
Edit `app/Exceptions/Handler.php` line 75:
```php
$message->to(['jm@emaji.net', 'another@email.com'])
```
### Change Email Priority
Edit `app/Exceptions/Handler.php` line 77:
```php
->priority(1); // 1 = High, 3 = Normal, 5 = Low
```
### Skip Additional Exception Types
Add to `$skipExceptions` array in `app/Exceptions/Handler.php` (line 48):
```php
$skipExceptions = [
\Illuminate\Auth\AuthenticationException::class,
\Your\Custom\Exception::class, // Add here
];
```
## Benefits
1. **User Experience:** Clean, professional error page instead of default Laravel error
2. **Immediate Notification:** Dev team knows about issues immediately
3. **Detailed Context:** All info needed to debug is in the email
4. **Environment Aware:** No spam emails during development
5. **Automatic Ticket:** Users feel reassured that the issue is tracked
## File Structure
```
emajiwallet/
├── app/
│ └── Exceptions/
│ └── Handler.php # Exception handler with email logic
└── resources/
└── views/
├── emails/
│ └── error-notification.blade.php # Email template
└── errors/
└── 500.blade.php # Custom error page
```
## Notes
- The exception handler only sends emails for true server errors (500-level)
- 404 errors and validation errors do NOT trigger emails (by design)
- If email sending fails, the error is logged but the app continues
- The custom error page is automatically used by Laravel when a 500 error occurs