How to Open a Support Ticket That Gets Resolved Fast (What to Include)

To get a Cloudesta support ticket resolved fast, open it from the client area (Support → Open Ticket, or submitticket.php), pick the department that matches the problem, and include everything a technician needs on the first read. That means the affected domain or server IP, the exact error text with a screenshot, when it started, what changed, your public IP for connection problems, and what you already tried. Leave passwords out unless a secure field is provided or you are asked. A complete first message usually removes several rounds of back-and-forth.

This guide applies to shared hosting, Cloud VPS, dedicated server and n8n hosting customers.

Prerequisites

• Access to your Cloudesta client area account.
• The domain, service or server IP the problem affects.
• For VPS and dedicated servers: SSH access, if the server is reachable, so you can collect basic diagnostics.

1. Where do I open a Cloudesta support ticket?

Log in to the client area and go to Support → Open Ticket, or go straight to https://cloudesta.com/submitticket.php. Opening the ticket while logged in links it to your account and services, so the technician can see which plan and server you are on.

If you cannot reach the client area, email the support address published on cloudesta.com from the email address registered on your account. You can also reply directly to any ticket notification email. Your reply is added to the same ticket as long as you send it from that registered address.

2. Which support department should I choose?

Choose the department on the ticket form that is closest to your issue. Technical problems such as a site being down, email not delivering or a server you cannot reach go to technical support. Invoices, payments and renewals go to billing. Questions about new services go to sales. A ticket in the wrong department is usually moved, but that move costs time.

Some changes can only be made by Cloudesta. Open a technical ticket for each of these:

• reverse DNS (rDNS)
• rescue mode
• OS reinstall
• IP changes
• plan upgrades
• cPanel licence issues

For an rDNS request, give the IP and the hostname you want, for example 203.0.113.10 → mail.example.com.

3. What should every support ticket include?

Use a specific subject, for example "example.com shows 500 error since 14:00" rather than "Help". Then cover these points in the message:

Service / domain: example.com (shared hosting) or VPS 203.0.113.10
Exact URL or address: https://example.com/checkout
Exact error text:   (copy-paste it, and attach a screenshot)
Started at:         2025-01-15 14:00 (Cairo time)
What changed:       updated WooCommerce plugin at 13:50
Who is affected:    all visitors / only me / only one mailbox
My public IP:       198.51.100.25 (for access problems)
Already tried:      cleared cache, disabled plugin X, rebooted VPS

Always give the time zone with any time. If the problem is intermittent, list two or three exact times it happened.

4. What details do I need for each type of issue?

Website errors (shared hosting)

Give the full URL and the status code or message, such as 500, 403 or 503. In cPanel, open Metrics → Errors and paste the latest lines that match the time of the error. If you need to check response headers from your own computer, run:

curl -I https://example.com/

Cannot connect (site, cPanel, SSH, FTP or email blocked)

Connection problems are often caused by a firewall block on your IP, so your public IP is the most important detail. Find it by running:

curl -4 ifconfig.me

On Windows or a phone, visit any "what is my IP" page instead. Also say whether the site works from mobile data. If it does, the problem is likely specific to your network or IP. A route trace helps with network issues. On Ubuntu, run:

sudo apt update && sudo apt install -y mtr-tiny
mtr -rwc 50 example.com

On Windows, run tracert example.com. Paste the output as text, not as a photo.

Email problems

List the affected addresses (sender and recipient), the time you sent the message, and the full bounce message, including the error code. In cPanel, open Email → Track Delivery, search for the recipient and include the result. For DNS-related delivery issues, include the output of:

dig +short MX example.com
dig +short TXT example.com

VPS and dedicated servers

On a Cloud VPS you manage the operating system yourself. Including a quick diagnostic snapshot saves time. Replace nginx with the service that is failing:

uptime
df -h
free -h
sudo systemctl status nginx --no-pager
sudo journalctl -u nginx --since "1 hour ago" --no-pager | tail -n 50

If the server does not respond to SSH at all, say so. Also mention whether you recently changed the firewall (ufw) or SSH settings.

n8n hosting

For n8n hosting, include the workflow name, the failing node and its error message. Also attach recent container logs. First run docker ps to find the container name, then:

docker ps
docker logs --tail 100 n8n

5. What should I never put in a support ticket?

Before attaching logs, remove database passwords from config file excerpts such as wp-config.php or .env.

6. Which priority should I choose, and how fast will support reply?

Pick the priority that matches the real impact:

• High: a production site, email or server is completely down.
• Medium: something is degraded or partly broken.
• Low: questions, configuration requests and non-urgent changes.

High-priority tickets are typically handled first. Exact response times vary with queue load and the complexity of the issue. Marking everything as High does not speed things up and can delay genuine outages.

7. How do I follow up on or reopen a ticket?

Find your ticket in the client area's ticket list under Support and add a reply there, or reply to the notification email. Keep the whole issue in one ticket and do not open a new one for the same problem. If a closed ticket's issue comes back, reply to that ticket to reopen it, so the technician can see the full history. If the problem is unrelated to the old ticket, open a new one.

8. What should I do during an emergency outage?

Open one High-priority technical ticket with a subject that starts with "DOWN:" and names the domain or IP. Before sending, check whether the problem is only on your side by testing from mobile data. Include the result of ping -c 4 203.0.113.10 and your public IP. After that, add new findings as replies to the same ticket rather than opening duplicates.

Verify it works

• Your ticket appears in the client area ticket list under Support, with the correct department and priority.
• You received a confirmation email with a ticket number at your registered address.
• Reread your message and check that it answers what, where, when, what changed and what you already tried.

Common problems

• Ticket sent from an unknown email address → Messages from addresses not on your account may not be linked to your services, or may need extra verification. Resend from your registered address or open the ticket while logged in to the client area.
• Lots of back-and-forth before any fix → The first message was probably missing the URL, the exact error, the time or your IP. Reply with the full template from step 3.
• Cannot reach the client area to open a ticket → Your IP may be blocked. Try from mobile data, then open the ticket and include your home or office IP.
• Screenshot is unreadable or the attachment is rejected → Crop the image to the error, or paste the error text and logs directly into the message.
• Two tickets for the same issue → Reply in one ticket asking support to merge or close the duplicate, and continue in that ticket only.

Frequently asked questions

Can I request reverse DNS or an OS reinstall without a ticket?

No. rDNS, OS reinstalls, rescue mode, IP changes, plan upgrades and cPanel licence issues are handled by Cloudesta, so open a support ticket for each of them.

Should I send my password so support can log in?

Only if the technician asks, and only through a secure field or an agreed method. Change the password after the ticket is resolved.

Where can I look for a fix before opening a ticket?

Search the Cloudesta knowledgebase. If you tried a guide and it did not work, mention which one in your ticket.

Need help? Open a ticket at https://cloudesta.com/submitticket.php using the checklist above, and our team will pick it up.