Self-managed server customers control the operating system and carry broader security and administration duties.
Applies to: Service policies and customer responsibilities
This operational guidance complements Tudor Internet's formal terms and policies. Where there is a conflict, the current contract, product description and published legal terms take priority.
Before you start
- Confirm the active product or addon and the domain or user it protects.
- Record the current settings before changing them.
What you need to do
- Patch and harden the operating system and applications.
- Configure firewalls, users, monitoring and backups.
- Prevent spam, attacks and unlawful use.
- Investigate incidents and preserve required records.
Confirm the result
- The service dashboard shows the intended setting or activation state after reload.
- A live test from a separate session or device confirms that the customer-facing service works as expected.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The service does not show as active in its dashboard. | Provisioning is pending, the wrong plan is selected or the service requires an additional activation step. | Check the Customer Portal service status and order email, then open a ticket with the service ID instead of creating a duplicate order. |
| The dashboard setting is correct but the public result is not. | DNS caching, an integration token, a device cache or a second service layer still uses the old value. | Test from a separate session, check the integration and record exact timestamps before changing the setting again. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The customer account email address
- The affected invoice, service, domain or ticket number
- The exact message and the time it appeared
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Cancel an addon without losing required data or protection
- Keep a change and rollback record for production services
- Remove secrets and personal data from screenshots and logs
- Prepare safe diagnostics for a support ticket
- Report abuse or security concerns
Last reviewed: 2026-07-18.
