When to Open a Ticket
Use a support ticket for:- Technical issues with services
- Billing questions or disputes
- Service configuration help
- Account access problems
- Service cancellation requests
- General inquiries
- Sales questions →
sales@digitalfyre.com - Abuse reports →
abuse@digitalfyre.com - Network issues →
noc@digitalfyre.com
Opening a Ticket
Select a Department
| Department | Use For |
|---|---|
| Technical Support | Server issues, service configuration, technical errors, performance, security |
| Billing | Invoice questions, payment issues, refund requests, pricing, account credits |
| Sales & Upgrades | Plan selection, upgrades, product questions |
| Abuse & Security | Phishing, spam, malware, attacks |
Set Priority
| Priority | Use When |
|---|---|
| Low | General questions, feature requests, non-urgent issues |
| Medium | Service is impacting some users, with non-critical technical issues |
| High | Service is completely down, security incidents, and critical functionality is broken |
Write Your Ticket
Add a clear subject line and detailed description. See Getting Support for tips on writing effective tickets.
After Submitting
Tracking and Responding
View your tickets at any time via Support → My Tickets. When support replies, log in to the portal and respond directly in the ticket thread. Answer all questions asked, provide any requested information, and confirm once your issue is resolved.Reopening a Closed Ticket
If an issue persists after closure, reopen the ticket, click Reopen Ticket, and explain why it still exists, along with any new details.Best Practices
Do:- One issue per ticket
- Be specific — include service names, IPs, error messages, and steps to reproduce
- Attach screenshots of errors
- Use the correct priority level
- Update the ticket with new findings
- Vague descriptions (
it's broken) - Opening duplicate tickets for the same issue
- Replying multiple times without new information
- Setting High priority for non-critical issues
Ticket Examples
- Technical Issue
- Billing Issue
- Server Not Responding
Good: Clear scope, relevant details, steps already tried.Subject:
500 Internal Server Error on example.com after updating WordPress to 6.5Message: Since updating WordPress to 6.5 this morning around 9:00 AM ET, my site at example.com (hosted on VPS vps-nyc-204, IP 203.0.113.45) is returning a 500 Internal Server Error on all pages.The error log at /var/log/nginx/error.log shows:FastCGI sent in stderr: PHP message: PHP Fatal error: Cannot redeclare stripe_init()I have already deactivated all plugins via FTP and the error persists. WordPress and PHP (8.2) versions are unchanged. The site was working fine before the update.Sensitive Information
Never attach files containing passwords, private keys, credit card numbers, or other sensitive credentials. Use the Sensitive Data tab inside the ticket instead.