{"count":663,"next_page":"https://support.rebel.com/api/v2/help_center/en-us/articles.json?page=2&per_page=30&sort_order=asc","page":1,"page_count":23,"per_page":30,"previous_page":null,"articles":[{"id":57767973230619,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57767973230619.json","html_url":"https://support.rebel.com/hc/en-us/articles/57767973230619-How-to-Transfer-Your-Google-Workspace-Subscription-from-Rebel-Directly-to-Google","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":1260800045849,"created_at":"2026-10-26T20:06:23Z","updated_at":"2026-10-26T20:09:08Z","name":"How to Transfer Your Google Workspace Subscription from Rebel Directly to Google","title":"How to Transfer Your Google Workspace Subscription from Rebel Directly to Google","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-26T20:08:01Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"

If you currently subscribe to Google Workspace through Rebel as your reseller, you can transition your subscription and billing directly to Google.

Because Rebel acts as your reseller of record, transferring direct billing to Google requires our support team to decouple your domain from our Google Partner Reseller Console.
 

What Happens to Your Data?

Your data remains 100% safe.

Moving your billing from Rebel directly to Google does not erase or alter your data:

Step 1: Provide Written Confirmation from the Registered Account Owner

To protect your organization’s services against unauthorized modifications and prevent service interruptions, Rebel strictly requires written authorization originating from the primary email address on file for the Rebel.com account.

How to Submit Your Request:

    \n
  1. Locate the primary email address registered to your Rebel.com account.
     
    2. \n
  2. Send an email to service@rebel.com (or reply to an open support ticket) directly from that address.
     
    3. \n
  3. Include the following authorization details:\n
    4. \n

Note: Requests submitted from non-account email addresses, secondary contacts, or phone inquiries cannot be processed until the registered account owner provides written confirmation referencing their account username from the primary address on file.

Step 2: Rebel Reseller Decoupling

Once our support team verifies the account owner's written request:

    \n
  1. Rebel releases and unlinks your domain from our Google Partner Reseller Console.
     
    2. \n
  2. Our billing team closes out the Google Workspace subscription on your Rebel account to ensure you are not billed twice.
     
    3. \n
  3. Google automatically places your account into a standard transition grace period so your email services remain uninterrupted while you set up direct payment.
    4. \n

Step 3: Establish Direct Billing in Your Google Admin Console

As soon as Rebel releases the reseller link, you must sign in to Google to select your plan and enter your billing details.

    \n
  1. Sign in to the Google Admin Console using your Super Administrator account (e.g., admin@yourdomain.com).
     
    2. \n
  2. A billing banner will display at the top of the dashboard. Navigate to Billing > Subscriptions.
     
    3. \n
  3. Click Set up Billing (or Add or upgrade a subscription).
     
    4. \n
  4. Select your desired Google Workspace edition (e.g., Business Starter, Business Standard, Business Plus, or Enterprise).
     
    5. \n
  5. Choose your payment terms:\n
    6. \n
  6. Enter your direct payment method (credit card or business bank account) and submit the order.
    7. \n

Official Google Reference: For detailed walkthrough steps on adding payment methods directly in your admin console, review the official guide:

 Google Workspace Admin Help: Set up Google Workspace billing

Keeping Your Domain at Rebel

This process only transitions your Google Workspace subscription and software billing over to Google.

Your domain registration, nameservers, and DNS Manager can stay right here at Rebel.com without disruption. If you ever need help with DNS records, domain renewals, or additional services, our support team is available via service@rebel.com.

","user_segment_ids":[]},{"id":57763960528027,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57763960528027.json","html_url":"https://support.rebel.com/hc/en-us/articles/57763960528027-How-to-Transfer-Your-Existing-Google-Workspace-Subscription-to-Rebel-com","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":1260800045849,"created_at":"2026-10-26T19:00:50Z","updated_at":"2026-10-26T19:05:23Z","name":"How to Transfer Your Existing Google Workspace Subscription to Rebel.com","title":"How to Transfer Your Existing Google Workspace Subscription to Rebel.com","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-26T19:05:03Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you currently have an active Google Workspace subscription directly with Google or through another partner, you can transfer management and billing to Rebel.com.
 
Transferring your subscription transitions your account management to Rebel without service interruption: your emails, files in Google Drive, calendar events, user accounts, and admin settings remain completely untouched.
 
\n

Prerequisites Before You Begin

\n\n

Step-by-Step: How to Generate Your Transfer Token

\n
    \n
  1. \n
    Obtain Rebel's Public Identifier
    \n
    Contact our Support team during operating hours to receive Rebel's Reseller Public Identifier before starting the process.
     
    \n
    2. \n
  2. \n
    Access the Transfer Portal
    \n
    Open your browser and navigate directly to:
    \n
    admin.google.com/TransferToken
    \n
    \n(Alternatively, log in to your Google Admin Console, open the navigation menu, and select Account > Reseller management).
     
    \n
    3. \n
  3. \n
    Authenticate as Super Admin
    \n
    If prompted, sign in with your primary Super Administrator credentials.
     
    \n
    4. \n
  4. \n
    Enter Rebel's Public Identifier
    \n
    In the field labeled Public Identifier, paste the identifier provided to you by our Support team, then click Continue.
     
    \n
    5. \n
  5. \n
    Select Subscriptions to Transfer
    \n
    Choose the Google Workspace subscriptions and add-ons you wish to move over to Rebel.
     
    \n
    6. \n
  6. \n
    Generate the Authorization Token
    \n
    Review and accept the transfer agreement terms, then click Generate Transfer Authorization.
     
    \n
    7. \n
  7. \n
    Copy Your Token
    \n
    A unique, alphanumeric transfer token will appear on your screen. Copy this code or keep the tab open.
    \n
    8. \n
\n

Important Considerations

\n\n

Official Google Documentation

\n
For detailed information directly from Google regarding how transfer authorizations function, you can review Google's official documentation:
\n
\n\n

Finalizing the Transfer with Rebel

\n
Once you have generated your authorization token, provide it to our Support Team along with:
\n
\n\n
Submit a ticket or reach out to our team via chat through our Help Center during operating hours, and an agent will finalize the setup on Rebel's platform.
\n
","user_segment_ids":[]},{"id":57743588716571,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57743588716571.json","html_url":"https://support.rebel.com/hc/en-us/articles/57743588716571-What-SSL-Certificate-Formats-Does-Rebel-Provide-PEM-vs-PFX","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206213727,"created_at":"2026-10-26T13:41:41Z","updated_at":"2026-10-26T13:44:54Z","name":"What SSL Certificate Formats Does Rebel Provide? (PEM vs. PFX)","title":"What SSL Certificate Formats Does Rebel Provide? (PEM vs. PFX)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-26T13:44:54Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
When you purchase or renew an SSL certificate through Rebel, your certificate files are issued in standard PEM format (.crt, .cer, .pem).
 
If your web server, hosting platform, or IT administrator requests a PFX or PKCS#12 file (.pfx, .p12), this guide outlines what format Rebel supplies, why PFX files are not provided directly, and where to look if your setup requires a conversion.
 
\n

What We Deliver: Standard PEM Format

\n
Through our Certificate Authority partner (GlobalSign), all Rebel SSL certificates are issued and delivered strictly in standard PEM (Privacy-Enhanced Mail) format.
\n
\n\n

Why Rebel Does Not Supply .PFX Files

\n
Certain hosting environments—most notably Microsoft Windows Server (IIS), Microsoft Exchange, and Microsoft Azure—often request a bundled archive file format known as PFX or PKCS#12 (.pfx / .p12).
 
\n
A .pfx file is a single package that requires bundling your certificate, the intermediate chain, and your server's secret Private Key.
\nRebel Support & Security Policy: Rebel cannot generate, build, convert, or supply a .pfx file for you.
Under global CA/Browser Forum security requirements, your Private Key is created directly within your own server environment and must remain strictly confidential to you. Rebel and GlobalSign never see, store, or have access to your private key. Because we do not possess your private key, it is technically impossible for us to assemble a .pfx archive on your behalf.
\n

Third-Party Conversion & Server Support Notice

\n
\nImportant Support Scope: Rebel Customer Support provides guidance and technical assistance solely for the PEM-formatted certificates issued through our platform.
\n
We do not offer direct technical support, troubleshooting, or execution services for file format conversions, third-party software utilities, or external server environments (such as Microsoft IIS or Azure).
If your environment strictly requires a .pfx file, these steps and external resources will help point you in the right direction:
\n\n

Need the Intermediate Certificate?

\n
If your setup requires GlobalSign's intermediate certificate to complete the bundle, you can download the matching intermediate certificate directly from GlobalSign:
 
\n
https://support.globalsign.com/ca-certificates/intermediate-certificates/alphassl-intermediate-certificates
","user_segment_ids":[]},{"id":57602026512539,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57602026512539.json","html_url":"https://support.rebel.com/hc/en-us/articles/57602026512539-Urgent-PHP-Security-Update-PHP2Shell","author_id":25830905751579,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360003812693,"created_at":"2026-10-22T21:08:36Z","updated_at":"2026-10-22T21:08:40Z","name":"Urgent PHP Security Update (PHP2Shell)","title":"Urgent PHP Security Update (PHP2Shell)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T21:08:40Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
On Wednesday, October 21, 2026, the PHP project released an emergency security update addressing two critical vulnerabilities in the PHP core interpreter, tracked as CVE-2026-109618 and CVE-2026-109619 (collectively known as “PHP2Shell”)
 
Both are rated Critical (CVSS v4.0 score of 9.2) and could allow an attacker to run malicious code on a web server running an unpatched version of PHP, without needing to log in. Because details of these flaws became public before the fix was released, and attacks have been observed in the wild, we have treated this as our highest priority.
 

What this means for your domains

Domain name registrations, DNS, and email forwarding are not affected. No action is required for your domains.

 

What we have done to protect you

All PHP versions on our webhosting servers have been patched to the fixed releases: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. If your website uses PHP 8.2 or newer, it is already protected and no action is needed.
 

What you need to do

Not sure which version you’re using, or concerned your site may have been affected? Contact our support team.
","user_segment_ids":[]},{"id":57602040006427,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57602040006427.json","html_url":"https://support.rebel.com/hc/en-us/articles/57602040006427-Urgent-PHP-Security-Update-PHP2Shell","author_id":25830905751579,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360008164734,"created_at":"2026-10-22T21:08:35Z","updated_at":"2026-10-22T21:08:40Z","name":"Urgent PHP Security Update (PHP2Shell)","title":"Urgent PHP Security Update (PHP2Shell)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T21:08:40Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
On Wednesday, October 21, 2026, the PHP project released an emergency security update addressing two critical vulnerabilities in the PHP core interpreter, tracked as CVE-2026-109618 and CVE-2026-109619 (collectively known as “PHP2Shell”)
 
Both are rated Critical (CVSS v4.0 score of 9.2) and could allow an attacker to run malicious code on a web server running an unpatched version of PHP, without needing to log in. Because details of these flaws became public before the fix was released, and attacks have been observed in the wild, we have treated this as our highest priority.
 

What this means for your domains

Domain name registrations, DNS, and email forwarding are not affected. No action is required for your domains.

 

What we have done to protect you

All PHP versions on our webhosting servers have been patched to the fixed releases: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. If your website uses PHP 8.2 or newer, it is already protected and no action is needed.
 

What you need to do

Not sure which version you’re using, or concerned your site may have been affected? Contact our support team.
","user_segment_ids":[]},{"id":57601978768667,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57601978768667.json","html_url":"https://support.rebel.com/hc/en-us/articles/57601978768667-Urgent-PHP-Security-Update-PHP2Shell","author_id":25830905751579,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":51913836965403,"created_at":"2026-10-22T21:08:34Z","updated_at":"2026-10-22T21:08:40Z","name":"Urgent PHP Security Update (PHP2Shell)","title":"Urgent PHP Security Update (PHP2Shell)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T21:08:40Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
On Wednesday, October 21, 2026, the PHP project released an emergency security update addressing two critical vulnerabilities in the PHP core interpreter, tracked as CVE-2026-109618 and CVE-2026-109619 (collectively known as “PHP2Shell”)
 
Both are rated Critical (CVSS v4.0 score of 9.2) and could allow an attacker to run malicious code on a web server running an unpatched version of PHP, without needing to log in. Because details of these flaws became public before the fix was released, and attacks have been observed in the wild, we have treated this as our highest priority.
 

What this means for your domains

Domain name registrations, DNS, and email forwarding are not affected. No action is required for your domains.

 

What we have done to protect you

All PHP versions on our webhosting servers have been patched to the fixed releases: 8.5.12, 8.4.27, 8.3.36, and 8.2.35. If your website uses PHP 8.2 or newer, it is already protected and no action is needed.
 

What you need to do

Not sure which version you’re using, or concerned your site may have been affected? Contact our support team.
","user_segment_ids":[]},{"id":57596063548955,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57596063548955.json","html_url":"https://support.rebel.com/hc/en-us/articles/57596063548955-Rebel-Cloud-Email-Service-Limits-and-Specifications","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":8784743814299,"created_at":"2026-10-22T19:20:38Z","updated_at":"2026-10-22T19:24:53Z","name":"Rebel Cloud Email Service Limits and Specifications","title":"Rebel Cloud Email Service Limits and Specifications","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T19:24:52Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
When using Rebel Cloud Email, specific account and server limits are enforced to ensure optimal deliverability, account security, and server stability across all accounts.
 
Below is a summary of the standard operational specifications and limits applied to Cloud Email mailboxes.
 
\n

Cloud Email Specifications Overview

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Feature / DirectiveMaximum LimitDetails
Email Attachment Size< 25 MBTotal size limit per outgoing or incoming email message (including message headers and files).
Email Aliases50 / mailboxAdditional email addresses that route incoming mail directly into your main inbox.
Email Forwards4 / mailboxExternal or internal addresses configured to receive forwarded copies of incoming mail.

Understanding Cloud Email Limits

\n

1. Attachment Size Limit (< 25 MB)

\n\n

2. Email Aliases (50 per Mailbox)

\n\n

3. Email Forwards (4 per Mailbox)

\n\n

Contact Support

\n
If you have questions about your Cloud Email limits or need assistance configuring aliases and forwarding rules, our technical support team is here to help:
\n
","user_segment_ids":[]},{"id":57594681746843,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57594681746843.json","html_url":"https://support.rebel.com/hc/en-us/articles/57594681746843-How-to-Fix-Cannot-Send-Mail-Error-on-iPhone-Apple-Mail","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360008352053,"created_at":"2026-10-22T18:58:03Z","updated_at":"2026-10-22T19:01:47Z","name":"How to Fix \"Cannot Send Mail\" Error on iPhone / Apple Mail","title":"How to Fix \"Cannot Send Mail\" Error on iPhone / Apple Mail","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T19:01:46Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you can receive emails on your iPhone or iPad but get a \"Cannot Send Mail\" error, a bounce-back, or a message stating that an email address was rejected when sending, the issue is almost always related to your Outgoing Mail Server (SMTP) settings in Apple Mail.
 
A common cause on iOS devices is that Apple Mail labels the SMTP Username and Password fields as (Optional) during setup. However, on our mail servers, SMTP authentication is strictly required.
 
\n

How to Fix SMTP Settings in Apple Mail

\n
    \n
  1. Open Settings on your iPhone or iPad.
    2. \n
  2. Navigate to Apps > Mail (or Mail > Accounts on older iOS versions).
    3. \n
  3. Tap your email account.
    4. \n
  4. Tap Account Settings and then select SMTP under the Outgoing Mail Server section.
    5. \n
  5. Tap your Primary Server.
    6. \n
  6. \n
    Ensure the following fields are filled out completely:
    \n
      \n
    • \nUser Name: Enter your full email address (e.g., name@yourdomain.com). Do not leave this blank even if iOS says optional.
       
      • \n
    • \nPassword: Enter your email password. Do not leave this blank.
       
      • \n
    • \nUse SSL: Toggle ON.
       
      • \n
    • \nAuthentication: Select Password.
      • \n
    \n
    7. \n
  7. Confirm your Server Port and Encryption match your specific email setup (see server details below).
     
    8. \n
  8. Tap Done in the top-right corner to save your settings.
    9. \n
\n

How to Verify Your Server Settings

\n
We strongly recommend using IMAP for all mobile devices so your messages, folders, and sent items stay synchronized seamlessly across all your phones, tablets, and computers.
 
\n
\n

Option 1: Rebel Cloud Email Settings

\n
\n(Note: Always use .com for Cloud Mail server addresses—do not use .ca).\n
\n
\n\n

Option 2: Plesk Hosted Email Settings

\n
\n(Replace yourdomain.com with your actual registered domain name).\n
\n
\n\n

How to Troubleshoot Connection Issues

\n\n

How to Contact Support

\n
If you have verified your settings and are still unable to send mail, our technical support team is available to help:
\n
","user_segment_ids":[]},{"id":57593700847515,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57593700847515.json","html_url":"https://support.rebel.com/hc/en-us/articles/57593700847515-How-to-Fix-Fatal-error-Allowed-memory-size-exhausted-in-Plesk","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":47653774685979,"created_at":"2026-10-22T18:38:45Z","updated_at":"2026-10-22T18:39:23Z","name":"How to Fix \"Fatal error: Allowed memory size exhausted\" in Plesk?","title":"How to Fix \"Fatal error: Allowed memory size exhausted\" in Plesk?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T18:39:23Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
\n
When managing a website hosted on Plesk, you may occasionally encounter a white page or a PHP error message that looks similar to this:
\n
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vhosts/...
\n
\n

What Does This Error Mean?

\n
PHP applications (such as WordPress, Joomla, or custom scripts) are assigned a specific memory limit (e.g., 128M or 134217728 bytes) to execute scripts on the server.
 
\n
When a plugin, theme update, complex database query, or resource-heavy script attempts to use more memory than the allocated limit, PHP safely halts execution to protect overall server stability—resulting in the \"Allowed memory size exhausted\" error.
 
\n

How to Resolve This Issue

\n
Because websites reside on a shared hosting environment, memory directives cannot be modified directly within the Plesk control panel. This administrative setting ensures optimal performance and prevents server resource depletion for all hosted accounts.
 
\n
If your website is displaying this error, our Support Team will need to update your account's memory limit on the server level.
 
\n

Information to Provide to Support

\n
When reaching out to our team, please provide the following details so we can update your configuration promptly:
\n
\n\n

How to Contact Support

\n
Our technical support team is available to adjust your memory allocations and get your website running smoothly:
\n
","user_segment_ids":[]},{"id":57593640056731,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57593640056731.json","html_url":"https://support.rebel.com/hc/en-us/articles/57593640056731-How-to-Fix-Fatal-error-Allowed-memory-size-exhausted-in-Plesk","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360003812693,"created_at":"2026-10-22T18:38:43Z","updated_at":"2026-10-22T18:39:23Z","name":"How to Fix \"Fatal error: Allowed memory size exhausted\" in Plesk?","title":"How to Fix \"Fatal error: Allowed memory size exhausted\" in Plesk?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T18:39:23Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
\n
When managing a website hosted on Plesk, you may occasionally encounter a white page or a PHP error message that looks similar to this:
\n
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/vhosts/...
\n
\n

What Does This Error Mean?

\n
PHP applications (such as WordPress, Joomla, or custom scripts) are assigned a specific memory limit (e.g., 128M or 134217728 bytes) to execute scripts on the server.
 
\n
When a plugin, theme update, complex database query, or resource-heavy script attempts to use more memory than the allocated limit, PHP safely halts execution to protect overall server stability—resulting in the \"Allowed memory size exhausted\" error.
 
\n

How to Resolve This Issue

\n
Because websites reside on a shared hosting environment, memory directives cannot be modified directly within the Plesk control panel. This administrative setting ensures optimal performance and prevents server resource depletion for all hosted accounts.
 
\n
If your website is displaying this error, our Support Team will need to update your account's memory limit on the server level.
 
\n

Information to Provide to Support

\n
When reaching out to our team, please provide the following details so we can update your configuration promptly:
\n
\n\n

How to Contact Support

\n
Our technical support team is available to adjust your memory allocations and get your website running smoothly:
\n
","user_segment_ids":[]},{"id":57580823636379,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57580823636379.json","html_url":"https://support.rebel.com/hc/en-us/articles/57580823636379-I-Purchased-a-Registry-Premium-Domain-What-Happens-Next","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167907,"created_at":"2026-10-22T14:52:47Z","updated_at":"2026-10-22T14:56:22Z","name":"I Purchased a Registry Premium Domain—What Happens Next?","title":"I Purchased a Registry Premium Domain—What Happens Next?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T14:55:55Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
Congratulations on securing your registry premium domain! Registry premium domains are high-value TLDs (such as .science, .club, or .store) that are priced higher by the central registry due to their strong keyword value and marketability.
 
Because these domains are new registrations that require specialized authorization payloads at the registry level, our team handles the registration manually to ensure your domain is secured smoothly and correctly.
 
\n

The Post-Purchase Process: Step-by-Step

\n

1. Queue Routing & Expedited Processing

\n
Once your order is placed, it enters our fulfillment queue:
\n
\n\n

2. Written Confirmation of Terms (Required)

\n
Because registry premium domains involve binding registry fees and non-standard pricing tiers, we require written confirmation before we submit the registration to the central registry.
 
\n
Our manual processing team will send you an email requiring your explicit agreement to the following terms:
Important Policy Notice:
\n
\n
\nAction Required: You must reply directly to that email to confirm your agreement. For security and compliance, this confirmation must be in writing via email and cannot be accepted verbally over a phone call or chat.
 
\n

3. Manual Registration & Same-Day Activation

\n
Unlike aftermarket domains that require moving between registrars, registry premium domains do not have a prior registrar or owner tied to them:
\n
","user_segment_ids":[]},{"id":57580457961627,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57580457961627.json","html_url":"https://support.rebel.com/hc/en-us/articles/57580457961627-I-Purchased-an-Aftermarket-Premium-Domain-What-Happens-Next","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167907,"created_at":"2026-10-22T14:46:06Z","updated_at":"2026-10-22T14:47:18Z","name":"I Purchased an Aftermarket Premium Domain—What Happens Next?","title":"I Purchased an Aftermarket Premium Domain—What Happens Next?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T14:46:38Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
Congratulations on securing an aftermarket premium domain! Because aftermarket domains (such as .com, .net, or .org names owned by private sellers on networks like Afternic or Sedo) involve procuring the domain from an external third-party seller, the activation process requires a few administrative steps to safely transfer the domain into your account.
 
\n

The Post-Purchase Process: Step-by-Step

\n

1. Automatic Queue Routing & Priority Processing

\n
Once your order is placed, it enters our processing backlog:
\n
\n\n

2. Written Confirmation of Terms (Required)

\n
Because aftermarket domain procurements involve binding external agreements and irreversible acquisition costs with third-party networks, we require written confirmation before we buy the domain from the seller.
 
\n
Our manual processing team will send an email requiring your explicit agreement to the following terms:
Important Policy Notice:
\n
\n
\nAction Required: You must reply directly to that email to confirm your agreement. For security and audit purposes, this confirmation must be in writing via email and cannot be accepted over a phone call or chat.
\n

3. Domain Transfer & Acquisition

\n
Once we receive your written confirmation:
\n
\n
    \n
  1. Our fulfillment team pays the aftermarket network (e.g., Afternic or Sedo) and initiates the secure transfer.
     
    2. \n
  2. We obtain the official authorization (EPP) code from the seller and submit the transfer to the registry.
     
    3. \n
  3. Our team will keep you updated via email at every stage of the transfer.
    4. \n
\n

4. Final Activation & Timeline

\n
Standard registry transfer rules require a 5-day pending transfer period for existing domains moving between registrars.
\n
","user_segment_ids":[]},{"id":57575867777947,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57575867777947.json","html_url":"https://support.rebel.com/hc/en-us/articles/57575867777947-How-to-Locate-Server-Logs-for-Website-Error-in-Plesk-Hosting","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":47653774685979,"created_at":"2026-10-22T13:20:06Z","updated_at":"2026-10-22T13:39:31Z","name":"How to Locate Server Logs for Website Error in Plesk Hosting","title":"How to Locate Server Logs for Website Error in Plesk Hosting","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-22T13:39:30Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
When a website encounters an issue—such as a 500 Internal Server Error, a blank white screen, or a critical application failure—checking web server and application logs in Plesk is the fastest way to diagnose the root cause.
 
Plesk centralizes HTTP, HTTPS, Apache, Nginx, and PHP error logs into a single interface so you can quickly pinpoint broken code, missing files, or resource limitations.
 
\n

Steps to Check Logs in Plesk

\n

1. Access Your Domain Logs

\n
    \n
  1. Log in to your Plesk Control Panel.
    2. \n
  2. Go to Websites & Domains in the main menu.
    3. \n
  3. Locate your domain and click on Logs.
    4. \n
\n

2. Filter and Review Messages

\n
Use the Log Options dropdown menu (top right) to toggle specific log types:
\n
\n\n

Identifying Key Details in Log Entries

\n
When reviewing an error entry, look for these three key components:
 
\n
\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ElementExampleWhat It Tells You
Timestamp[22-Oct-2026 14:15:02 UTC]Matches the log entry to the exact time you tested or saw the error.
Error Level\nPHP Fatal error or [error]\nDistinguishes critical site-breaking failures from minor warnings.
File Path/httpdocs/wp-content/plugins/...Shows the exact file, line number, and plugin/theme causing the crash.

Common Error Examples & Fixes

\n

1. PHP Fatal Error

\n\n

2. Memory Limit Exhausted

\n\n

3. Permission Denied

\n\n
\nAdditional Resources: For technical details on log file locations, log rotation settings, and downloading raw log archives, refer to the official Plesk Log Files Documentation.
\n
","user_segment_ids":[]},{"id":57421687346459,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57421687346459.json","html_url":"https://support.rebel.com/hc/en-us/articles/57421687346459-About-DE-domain","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167987,"created_at":"2026-10-19T15:05:42Z","updated_at":"2026-10-19T15:06:41Z","name":"About .DE domain","title":"About .DE domain","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-19T15:06:41Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
What is a .DE domain?
.DE is the official country-code top-level domain (ccTLD) for Germany. It is one of the most popular domain extensions worldwide, widely used by businesses, organizations, and individuals targeting German and European audiences.
 
\nWho can register a .DE domain?
 
Anyone can register a .DE domain. There are no local residency requirements to purchase or hold the domain name. However, if a legal dispute arises, the registry requires non-resident domain holders to name a contact person in Germany to receive official documents.
 
Registration restrictions
Standard domain formatting rules apply:
\n\n
Domain requirements
\n
The registry enforces strict technical checks before completing setup. Your nameservers must be live and properly pre-configured to respond for your domain name before the registration request is submitted, or the setup will fail.
 
Additional details
\n\n
Get your .de domain with Rebel today!
\n
Note: If this domain requires manual registration, our Customer Support team will reach out to you once registration has been completed.
","user_segment_ids":[]},{"id":57201679118363,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57201679118363.json","html_url":"https://support.rebel.com/hc/en-us/articles/57201679118363-About-Si-domains","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167987,"created_at":"2026-10-14T14:28:09Z","updated_at":"2026-10-14T14:31:42Z","name":"About .Si domains","title":"About .Si domains","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-14T14:31:03Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
\n.SI is the country-code top-level domain (ccTLD) for Slovenia, operated by ARNES (Academic and Research Network of Slovenia) via register.si. It is the premier domain extension for businesses, organizations, and individuals targeting audiences in Slovenia and the European Union.
 
\n

Who Can Register a .SI Domain?

\n
Anyone worldwide—individuals or corporate entities—can register a .SI domain directly through Rebel.
\n
\n\n

Important: DNS Pre-Delegation Requirement

\n
Before a .SI domain registration or transfer request can complete, the .SI registry automatically conducts a pre-delegation DNS check to ensure proper configuration.
 
\n
\n

Requirements for Nameservers:

\n
    \n
  1. \nMinimum 2 Nameservers: You must provide at least two (2) authoritative nameservers.
     
    2. \n
  2. \nPre-Configuration Required: If you choose to use custom third-party nameservers, they must already be configured to return an authoritative answer for your domain prior to submitting your order.
     
    3. \n
  3. \nRebel Parking Servers (Easiest Option): If you are registering the domain before setting up hosting, simply select Rebel’s default DNS (dns.rebel.com / dns2.rebel.com or dns.rebel.ca / dns2.rebel.ca). Our servers are pre-configured to pass the registry check automatically.
    4. \n
\n
\nTip: If using custom DNS, you can test your nameservers beforehand using the registry's official tool: register.si DNS Check.
 
\n
\n

Key Features & Domain Management

\n

Registration Terms & Character Rules

\n\n

Domain Transfers to Rebel

\n\n

Technical Specifications

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ParameterSpecification
Registry Operator\nARNES (register.si)\n
Registry WHOIS Serverwhois.register.si
DNSSEC SupportSupported
Premium DomainsStandard pricing applies (no premium tiers)

Get your .SI domain with Rebel.com today!

\n
","user_segment_ids":[]},{"id":57201694306331,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57201694306331.json","html_url":"https://support.rebel.com/hc/en-us/articles/57201694306331-About-Si-domains","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167907,"created_at":"2026-10-14T14:28:08Z","updated_at":"2026-10-14T14:31:42Z","name":"About .Si domains","title":"About .Si domains","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-14T14:31:03Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
\n.SI is the country-code top-level domain (ccTLD) for Slovenia, operated by ARNES (Academic and Research Network of Slovenia) via register.si. It is the premier domain extension for businesses, organizations, and individuals targeting audiences in Slovenia and the European Union.
 
\n

Who Can Register a .SI Domain?

\n
Anyone worldwide—individuals or corporate entities—can register a .SI domain directly through Rebel.
\n
\n\n

Important: DNS Pre-Delegation Requirement

\n
Before a .SI domain registration or transfer request can complete, the .SI registry automatically conducts a pre-delegation DNS check to ensure proper configuration.
 
\n
\n

Requirements for Nameservers:

\n
    \n
  1. \nMinimum 2 Nameservers: You must provide at least two (2) authoritative nameservers.
     
    2. \n
  2. \nPre-Configuration Required: If you choose to use custom third-party nameservers, they must already be configured to return an authoritative answer for your domain prior to submitting your order.
     
    3. \n
  3. \nRebel Parking Servers (Easiest Option): If you are registering the domain before setting up hosting, simply select Rebel’s default DNS (dns.rebel.com / dns2.rebel.com or dns.rebel.ca / dns2.rebel.ca). Our servers are pre-configured to pass the registry check automatically.
    4. \n
\n
\nTip: If using custom DNS, you can test your nameservers beforehand using the registry's official tool: register.si DNS Check.
 
\n
\n

Key Features & Domain Management

\n

Registration Terms & Character Rules

\n\n

Domain Transfers to Rebel

\n\n

Technical Specifications

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ParameterSpecification
Registry Operator\nARNES (register.si)\n
Registry WHOIS Serverwhois.register.si
DNSSEC SupportSupported
Premium DomainsStandard pricing applies (no premium tiers)

Get your .SI domain with Rebel.com today!

\n
","user_segment_ids":[]},{"id":57005711363867,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57005711363867.json","html_url":"https://support.rebel.com/hc/en-us/articles/57005711363867-How-to-Fix-Missing-Automated-Email-Notifications-in-Plesk-Voicemail-to-Email-Fax-Application-Relays","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":42631151702427,"created_at":"2026-10-09T18:54:34Z","updated_at":"2026-10-09T18:58:30Z","name":"How to Fix Missing Automated Email Notifications in Plesk (Voicemail-to-Email, Fax & Application Relays)","title":"How to Fix Missing Automated Email Notifications in Plesk (Voicemail-to-Email, Fax & Application Relays)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-09T18:58:30Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If your business relies on automated email dispatch services—such as Shaw/Rogers Voicemail-to-Email, internet fax systems, online booking apps, or CRM notification relays—and those messages suddenly stop arriving in your inbox, your mail server or firewall may be silently dropping incoming connections at the gateway level.
 
Because transactional notifications are sent automatically by background systems, sender systems rarely display traditional bounce-back errors when a connection fails. Below is a step-by-step diagnostic guide to identifying the cause and getting those messages flowing smoothly again.
 
\n

Understanding Silent Relay Blocks

\n
When an external automated system (like a business phone provider) attempts to deliver a notification to your Plesk mailbox, the connection passes through two security checkpoints:
\n
\n
Shaw / Telecom Voicemail System\n            │\n            ▼\nServer Edge Firewall (Hardware/OS Level)\n            │\n            ├──► Check: Is sending server IP / subnet blocked? ──► YES ──► Silent Drop (No Log Created)\n            │\n            ▼ (NO)\nPlesk Postfix Mail Service\n            │\n            ├──► Check: SPF / DKIM / DMARC & Spam Rules\n            │\n            └──► RESULT: Message Delivered to Inbox\n
\n
\n
If the connection is dropped at the Edge Firewall Level, the message never reaches the mail server software (Postfix/Qmail). As a result, no standard delivery entry appears inside standard mail logs.
 
\n
\n

Common Symptoms of a Relay Block

\n\n

Step 1: Self-Service Troubleshooting Checklist

\n
Before opening a technical ticket with Support, run these quick diagnostic checks:
\n
\n
    \n
  1. \nVerify Webmail Delivery: Log directly into Plesk Webmail ([https://webmail.yourdomain.com]) to confirm whether the emails are bypassing your desktop email client (Outlook/Apple Mail) or getting routed to your Webmail Spam folder.
     
    2. \n
  2. \n
    \nPerform an External Forwarding Test: Temporarily update the email address inside your phone or application system to a secondary/external address (e.g., Gmail or Outlook.com).
    \n
    • \nIf the email arrives at Gmail instantly: This confirms the sending platform is operating correctly and the connection to your domain is getting stopped at the gateway.
    \n
    3. \n
\n

Step 2: Requesting Technical Unblocking from Support

\n
If your external test succeeds but messages still fail to reach your domain, our technical team will need to inspect the raw edge firewall logs to open up the path for your provider.
 
\n
Please submit a ticket to Support containing the following Telemetry Data Package:
\n
    \n
  1. \nRecipient Mailbox: The specific email address affected (e.g., tester@yourdomain.com).
     
    2. \n
  2. \nSender Envelope Address: The automated system email address used by your provider (e.g., noreply@shawbusiness.ca).
     
    3. \n
  3. \nExact Test Timestamp & Timezone: Trigger a fresh voicemail or test dispatch right before submitting your ticket, and note the exact minute (e.g., Today at 9:23 AM Eastern).
     
    4. \n
  4. \nOffice Network IP: Visit myip.rebel.com and provide the public IP address displayed on your screen.
     
    5. \n
  5. \nRaw Mail Headers (If Available): If you ran a successful test to a Gmail address, open the email in Gmail, click the three vertical dots next to Reply, select Show Original, and copy the text into your ticket.
    6. \n
\n

Step 3: What Our Hosting Engineers Will Do

\n
Once you submit these details, our Systems Engineering team will:
\n
","user_segment_ids":[]},{"id":57005711263899,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57005711263899.json","html_url":"https://support.rebel.com/hc/en-us/articles/57005711263899-How-to-Fix-Missing-Automated-Email-Notifications-in-Plesk-Voicemail-to-Email-Fax-Application-Relays","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360008352053,"created_at":"2026-10-09T18:54:33Z","updated_at":"2026-10-09T18:58:30Z","name":"How to Fix Missing Automated Email Notifications in Plesk (Voicemail-to-Email, Fax & Application Relays)","title":"How to Fix Missing Automated Email Notifications in Plesk (Voicemail-to-Email, Fax & Application Relays)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-09T18:58:30Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If your business relies on automated email dispatch services—such as Shaw/Rogers Voicemail-to-Email, internet fax systems, online booking apps, or CRM notification relays—and those messages suddenly stop arriving in your inbox, your mail server or firewall may be silently dropping incoming connections at the gateway level.
 
Because transactional notifications are sent automatically by background systems, sender systems rarely display traditional bounce-back errors when a connection fails. Below is a step-by-step diagnostic guide to identifying the cause and getting those messages flowing smoothly again.
 
\n

Understanding Silent Relay Blocks

\n
When an external automated system (like a business phone provider) attempts to deliver a notification to your Plesk mailbox, the connection passes through two security checkpoints:
\n
\n
Shaw / Telecom Voicemail System\n            │\n            ▼\nServer Edge Firewall (Hardware/OS Level)\n            │\n            ├──► Check: Is sending server IP / subnet blocked? ──► YES ──► Silent Drop (No Log Created)\n            │\n            ▼ (NO)\nPlesk Postfix Mail Service\n            │\n            ├──► Check: SPF / DKIM / DMARC & Spam Rules\n            │\n            └──► RESULT: Message Delivered to Inbox\n
\n
\n
If the connection is dropped at the Edge Firewall Level, the message never reaches the mail server software (Postfix/Qmail). As a result, no standard delivery entry appears inside standard mail logs.
 
\n
\n

Common Symptoms of a Relay Block

\n\n

Step 1: Self-Service Troubleshooting Checklist

\n
Before opening a technical ticket with Support, run these quick diagnostic checks:
\n
\n
    \n
  1. \nVerify Webmail Delivery: Log directly into Plesk Webmail ([https://webmail.yourdomain.com]) to confirm whether the emails are bypassing your desktop email client (Outlook/Apple Mail) or getting routed to your Webmail Spam folder.
     
    2. \n
  2. \n
    \nPerform an External Forwarding Test: Temporarily update the email address inside your phone or application system to a secondary/external address (e.g., Gmail or Outlook.com).
    \n
    • \nIf the email arrives at Gmail instantly: This confirms the sending platform is operating correctly and the connection to your domain is getting stopped at the gateway.
    \n
    3. \n
\n

Step 2: Requesting Technical Unblocking from Support

\n
If your external test succeeds but messages still fail to reach your domain, our technical team will need to inspect the raw edge firewall logs to open up the path for your provider.
 
\n
Please submit a ticket to Support containing the following Telemetry Data Package:
\n
    \n
  1. \nRecipient Mailbox: The specific email address affected (e.g., tester@yourdomain.com).
     
    2. \n
  2. \nSender Envelope Address: The automated system email address used by your provider (e.g., noreply@shawbusiness.ca).
     
    3. \n
  3. \nExact Test Timestamp & Timezone: Trigger a fresh voicemail or test dispatch right before submitting your ticket, and note the exact minute (e.g., Today at 9:23 AM Eastern).
     
    4. \n
  4. \nOffice Network IP: Visit myip.rebel.com and provide the public IP address displayed on your screen.
     
    5. \n
  5. \nRaw Mail Headers (If Available): If you ran a successful test to a Gmail address, open the email in Gmail, click the three vertical dots next to Reply, select Show Original, and copy the text into your ticket.
    6. \n
\n

Step 3: What Our Hosting Engineers Will Do

\n
Once you submit these details, our Systems Engineering team will:
\n
","user_segment_ids":[]},{"id":57004988672027,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57004988672027.json","html_url":"https://support.rebel.com/hc/en-us/articles/57004988672027-How-to-Fix-Plesk-Incoming-Email-Blocks-Caused-by-Sender-IP-Blacklists-SpamCop-DNSBLs","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":42631151702427,"created_at":"2026-10-09T18:40:36Z","updated_at":"2026-10-09T18:46:31Z","name":"How to Fix Plesk Incoming Email Blocks Caused by Sender IP Blacklists (SpamCop & DNSBLs)","title":"How to Fix Plesk Incoming Email Blocks Caused by Sender IP Blacklists (SpamCop & DNSBLs)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-09T18:46:31Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If an external sender (such as an automated service, SaaS application, or business partner) reports that emails sent to your domain are bouncing back with an error like 554 5.7.1 Service unavailable; Client host [IP] blocked using bl.spamcop.net, your mail server is rejecting traffic from a flagged sender IP address.
 
This occurs when the sending company's email server IP address is listed on a global DNS Blocklist (DNSBL) such as SpamCop, Spamhaus, or Sorbs.
 
\n

Understanding the Bounce Error

\n
When an external sender tries to deliver an email to your mailbox hosted on Plesk, our mail server performs an automated security lookup against global threat intelligence databases:
\n
\n
Sender Server (e.g., Sprout Social / Amazon SES)\n       │\n       ▼\nIncoming Mail Server (Plesk Server)\n       │\n       ├──► Checks SpamCop/DNSBL Database\n       │\n       └──► RESULT: Sender IP is listed on SpamCop ──► Mail REJECTED (554 5.7.1)\n
\n

Common Error Messages Received by Senders:

\n\n

Step-by-Step Resolution Process

\n
Because the block is triggered by the sender's server reputation rather than your domain settings, resolving the issue involves actions by both the sender and your hosting team.
 
\n
\n

Step 1: Actions Required by the Sending Organization

\n
    \n
  1. \nNotify the Sender: Inform the sending company (or their technical support) that their outbound sending IP address is listed on SpamCop or another DNSBL.
     
    2. \n
  2. \nRequest Delisting: The sending provider must clean their outbound mail queue and submit a delisting request directly to SpamCop or the relevant blocklist operator.
     
    3. \n
  3. \nTemporary Bypass (If Applicable): For critical one-time passcodes or authentication emails, request that the sending service temporarily bypass or send via an alternate channel while their IP reputation is restored.
    4. \n
\n

Step 2: What Our Support Team Can Do for Your Plesk Account

\n
If you need to receive emails from the flagged sender immediately, our support team can inspect server logs and configure an IP-level exemption on the mail server.
 
\n
Please contact Support with the following details:
\n
    \n
  1. \nRecipient Mailbox: The full email address on your domain attempting to receive the message (e.g., user@yourdomain.com).
     
    2. \n
  2. \nSender Email / Domain: The email address or domain of the sender (e.g., noreply@service.com).
     
    3. \n
  3. \nSender IP Address (If known): Found in the bounce-back report (e.g., 54.240.9.36).
     
    4. \n
  4. \nApproximate Timestamps: Date and time window when the email or passcode was requested.
    5. \n
\n

Technical Actions We Take on Plesk

\n
When you submit these details, our hosting administrators will:
\n
","user_segment_ids":[]},{"id":57003579619355,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/57003579619355.json","html_url":"https://support.rebel.com/hc/en-us/articles/57003579619355-How-to-Change-Your-Website-s-Document-Root-Directory-in-Plesk","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360003812693,"created_at":"2026-10-09T18:14:09Z","updated_at":"2026-10-09T18:22:33Z","name":"How to Change Your Website's Document Root Directory in Plesk","title":"How to Change Your Website's Document Root Directory in Plesk","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-09T18:21:57Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
Your Document Root is the specific folder on your web hosting server where your website's primary files (such as index.html or index.php) are stored and served to visitors.
 
Changing your Document Root allows you to switch your live domain to point to a new directory—for example, if you have built a temporary static page (e.g., yourdomain.ca-static), created a redesign staging folder, or uploaded a new application directory.
 
\n

Key Things to Keep in Mind Before You Begin

\n\n

Step-by-Step Guide: How to Change Your Document Root in Plesk

\n
    \n
  1. \nLog into your Plesk Hosting Control Panel.
     
    2. \n
  2. Navigate to Websites & Domains in the left-hand navigation menu.
     
    3. \n
  3. Locate your domain name, click on the Hosting & DNS tab, and select Hosting Settings.
     
    4. \n
  4. Scroll down to the Web space section and find the Document root field.
     
    5. \n
  5. Enter the exact name of the folder you want your site to load from (e.g., change yourdomain.ca to yourdomain.ca-static).
     
    6. \n
  6. Click OK or Apply at the bottom of the page to save your changes.
    7. \n
\n

Step 3: Verifying Your Changes

\n
After clicking OK, test your site to make sure the new directory is serving properly:
\n
\n
    \n
  1. Open a new browser window in Incognito / Private Browsing Mode (this prevents your browser from loading an older cached version of your site).
     
    2. \n
  2. Visit your domain name (e.g., [https://yourdomain.ca]).
     
    3. \n
  3. Verify that your new page content loads as expected.
    4. \n
\n
\nNeed to switch back? If you see an error, simply go back to Hosting Settings, re-enter your original folder name into the Document root field, and click OK to restore your site immediately.
\n
","user_segment_ids":[]},{"id":56998077525275,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56998077525275.json","html_url":"https://support.rebel.com/hc/en-us/articles/56998077525275-How-to-Fix-Spamhaus-Domain-Blacklist-Plesk-Email","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360008352053,"created_at":"2026-10-09T16:33:29Z","updated_at":"2026-10-09T16:44:48Z","name":"How to Fix Spamhaus Domain Blacklist (Plesk Email)","title":"How to Fix Spamhaus Domain Blacklist (Plesk Email)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-09T16:44:17Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If your outgoing emails suddenly bounce back with delivery errors explicitly mentioning Spamhaus, your domain name or email server IP address has been flagged on a Spamhaus Blocklist (such as the Spamhaus DBL - Domain Blocklist or Spamhaus SBL/XBL/ZEN).
 
Spamhaus is an international threat-tracking database used by major email service providers (Gmail, Outlook, Yahoo, and private mail servers) to reject traffic originating from flagged domains or shared web hosting IP ranges.
 
\n

Common Spamhaus Email Bounce Error Messages

\n
When your domain or mail server IP is flagged by Spamhaus, your email client (Outlook, Thunderbird, Apple Mail, Webmail, or Plesk) will receive an immediate Non-Delivery Report (NDR).
 
\n
Look for bounce-back codes containing any of the following Spamhaus triggers:
\n\n

Step 1: Check Your Exact Spamhaus Listing Status

\n
If you receive any of the Spamhaus error messages above, verify your exact listing details using these official security diagnostic tools:
\n
\n\n

Step 2: Self-Service Delisting vs. Hosting Provider Removal

\n
Spamhaus categorizes listings into two distinct resolution paths based on where the block originates:
\n
\n
    \n
  1. \n
    Individual Domain Listings (Self-Service Removal):
    \n
    If Spamhaus flags a standalone domain reputation issue without network-level locks, you can request an immediate removal yourself. Follow the prompts on check.spamhaus.org, submit your contact email address, and click the confirmation link sent to your inbox.
     
    \n
    2. \n
  2. \n
    Shared Plesk Hosting / Provider Network-Level Listings (Spamhaus DBL):
    \n
    Because Plesk Web and Email Hosting operates on shared server IP infrastructure, Spamhaus frequently places a Provider/Network Hold. In these cases, Spamhaus explicitly restricts end-user self-service requests and requires your web hosting provider to audit server node health and submit the official provider delisting request.\n
    \n
    3. \n
\n

Step 3: How to Submit a Provider Delisting Request to Support

\n
If Spamhaus indicates that your hosting provider must initiate the removal, our technical support team will step in to clear the block on the infrastructure level.
 
\n
Please submit a ticket to Support containing:
\n
    \n
  1. \nAffected Domain Name: (e.g., yourdomain.com)
     
    2. \n
  2. \nFull Spamhaus Bounce Text: (Paste the exact 550 or 554 Spamhaus error code received)
     
    3. \n
  3. \nSpamhaus Lookup Results: (A screenshot or direct link from check.spamhaus.org)
    4. \n
\n
Our Hosting & Systems Operations team will inspect the underlying shared Plesk server node, verify outbound mail hygiene, and submit the formal provider-level delisting request directly to Spamhaus on your behalf.
\n
","user_segment_ids":[]},{"id":56861548581787,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56861548581787.json","html_url":"https://support.rebel.com/hc/en-us/articles/56861548581787-How-to-Fix-Exceeding-Plesk-Disk-Space-and-Stop-Automated-Account-Suspensions-Plesk-Hosting","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360003812693,"created_at":"2026-10-06T21:24:30Z","updated_at":"2026-10-14T20:54:32Z","name":"How to Fix Exceeding Plesk Disk Space and Stop Automated Account Suspensions (Plesk Hosting)","title":"How to Fix Exceeding Plesk Disk Space and Stop Automated Account Suspensions (Plesk Hosting)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-14T20:54:32Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If your website or email service goes offline due to a Disk Space Exhaustion or Account Suspended alert, your hosting account has exceeded its allocated plan storage.
 
When your hosting plan reaches 100 percent or more of its capacity, background server scripts automatically trigger a safety suspension to protect shared server stability. While support can manually unsuspend your account to grant temporary access, the background system will automatically re-lock the site (often overnight around 3:00 AM) if total usage remains over 100 percent.
 
Follow this step-by-step guide, ordered from easiest to most advanced, to clear space and permanently stop the auto-suspension loop.
 
\n

Step 1: Check Where Space Is Being Used

\n
Before deleting anything, identify where your storage is hiding:
\n
\n
    \n
  1. Log into your Plesk Control Panel.
    2. \n
  2. Click Statistics in the left sidebar.
    3. \n
  3. Plesk displays a visual breakdown across Mail, Web Files, Databases, Logs, and Backups.
    4. \n
\n

Step 2: Clean Up or Archive Email Data

\n
Email accounts are usually the safest place to clear space without affecting website functionality.
 
\n
\n

A. Empty Trash, Junk, and Spam Folders

\n
    \n
  1. Log into Webmail (webmail.yourdomain.com) or your desktop email client such as Outlook, Apple Mail, or Thunderbird.
     
    2. \n
  2. Open the Trash or Deleted Items folder and purge all contents.
     
    3. \n
  3. Open the Junk or Spam folder and purge all contents.
     
    4. \n
  4. Check your Webmail quota indicator to verify that it shows reduced usage immediately.
    5. \n
\n

B. Delete Old Emails and Large Attachments

\n
    \n
  1. Go to your Inbox and Sent Items folders.
     
    2. \n
  2. Delete very old emails going back years or decades that are no longer needed.
     
    3. \n
  3. \nSort messages by Size (largest first) and delete old emails containing heavy attachments like PDFs, videos, or ZIP files.
     
    4. \n
  4. \nEmpty the Trash folder again to permanently free up that server space.
    5. \n
\n

C. Archive Emails Locally

\n
If you need to keep historical emails but want them removed from the hosting server:
\n
\n
    \n
  1. Open any desktop email application like Outlook, Apple Mail, or Thunderbird.
     
    2. \n
  2. Move old messages from your server IMAP folders into a Local Folder or On My Computer folder inside your app.
     
    3. \n
  3. If your app supports exports, you can save them to an archive file on your hard drive, such as PST for Outlook or MBOX for Apple Mail and Thunderbird. If your app does not support PST or MBOX files, simply dragging and dropping emails into a local folder on your computer keeps them safe on your device while removing them from the server.
     
    4. \n
  4. Delete the archived emails from your server folders and empty the Trash.
     
    5. \n
  5. Log into Webmail at webmail.yourdomain.com to confirm server space was freed while your local desktop copy remains saved.
    6. \n
\n

Step 3: Clear Temporary Website Files and Local Backups

\n
If email cleanup is not enough, inspect your website files using Plesk File Manager:
 
\n
\n

A. Empty Plesk Trash

\n
In Plesk File Manager, click Empty Trash to permanently purge previously deleted files sitting in the recycler.
 
\n
\n

B. Remove Backup Plugin Archives

\n
If you use WordPress backup plugins such as UpdraftPlus, All in One WP Migration, or BackupBuddy, look inside your domain folder:
\n
\n\n
Keep one recent backup copy (downloading it to your computer first if needed), then select and delete older archive files (like ZIP or TAR.GZ) from previous months or years.
 
\n
\n

C. Clear Image Optimizer Originals

\n
Plugins like ShortPixel or Smush store original uncompressed images in folders like yourdomain.com > wp-content > uploads > ShortPixelBackups. Since your live site uses the optimized versions, you can safely delete the contents of these backup folders.
 
\n
\n

Step 4: Disable Debug Logs and Identify Hidden Files

\n
If WordPress debugging is left enabled, every minor error or bot attack records a line of text, causing a single debug.log file to swell to tens of gigabytes.
 
\n
\n

How to Disable Debugging in Plesk (No Code Required):

\n
    \n
  1. Log into your Plesk Control Panel.
     
    2. \n
  2. Go to WordPress in the left sidebar to open the WordPress Toolkit.
     
    3. \n
  3. Under your domain's dashboard, look for the Debugging toggle in the Tools section.
     
    4. \n
  4. \nToggle Debugging to OFF. (This automatically updates your site configuration without needing to edit wp-config.php manually).
     
    5. \n
  5. Open Plesk File Manager, navigate to yourdomain.com > wp-content, and delete the debug.log file.
    6. \n
\n

Example of an Audited Directory Over Quota:

\n
4.0K    advanced-cache.php\n16K     ai1wm-backups\n806M    cache\n80GB    debug.log            (Runaway error log file!)\n2.8M    index.php\n355M    plugins\n139M    themes\n12M     updraft\n6.4GB   uploads\n12K     wflogs
\n
Important Notice Regarding Website File Cleanups:
\n
Modifying or deleting core website files, theme files, databases, or active uploads inside yourdomain.com > wp-content > uploads can break your live website if done incorrectly.
Rebel is responsible for hosting platform infrastructure and cannot directly manage, edit, or selectively delete custom website code and plugin data on your behalf.
If you are unsure which website files are safe to delete, we strongly recommend contacting your web developer, IT professional, or site administrator to perform the cleanup.
 
\n

Step 5: Next Steps: Technical Escalation or Hosting Upgrade

\n
If you have completed all the steps above and are still exceeding your storage limit:
 
\n
\n

Option A: Escalate to Our Hosting Engineering Team

\n
If you have cleared all visible files but your account remains over quota, contact Rebel Support. Our team can generate an escalation ticket to our Hosting Engineering Team. They can run deep server-level audits to locate hidden system logs, temp files, or orphaned database files and safely remove them for you.
 
\n
\n

Option B: Upgrade or Explore Larger Storage Solutions

\n
If your business needs to store larger volumes of data, you can upgrade to our higher-tier Business Web Hosting plans, which support up to 200 GB of storage.
 
\n
If your storage needs far exceed standard shared web hosting limits (for example, hundreds of gigabytes or terabytes of media assets, backups, or archives), you may want to look into specialized cloud infrastructure or dedicated hosting environments. Some popular options outside our platform include:
\n\n

Why Dashboard Meters Take Time to Update

\n
After deleting files, your Plesk dashboard visual meter might still display high usage because statistics recalculate during nightly maintenance runs.
 
\n
As long as physical files are deleted from File Manager or Webmail, your account is safe from automated re-suspension even if the dashboard visual meter takes up to 24 hours to sync.
 
\n

Need Extra Assistance?

\n
Start a live chat on our website during business hours or email our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
","user_segment_ids":[]},{"id":56857476433691,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56857476433691.json","html_url":"https://support.rebel.com/hc/en-us/articles/56857476433691--AU-Domain-Transfers-Expiry-Status-and-ABN-Compliance-Requirements","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167987,"created_at":"2026-10-06T20:11:35Z","updated_at":"2026-10-06T20:23:16Z","name":".AU Domain Transfers: Expiry Status and ABN Compliance Requirements","title":".AU Domain Transfers: Expiry Status and ABN Compliance Requirements","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T20:23:15Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
Transferring an Australian domain name (.au, .com.au, .net.au, .org.au, .id.au) between registrars is governed by strict rules set by auDA (.au Domain Administration).
 
If your .au domain is expired or if the linked business entity details (such as an ABN or ACN) are inactive or out of date, the domain cannot be transferred or recovered until compliance requirements are fulfilled.
 
\n

Why Can't an Expired or Non-Compliant .AU Domain Be Transferred?

\n
Under auDA policy, two critical criteria must be met to transfer a domain to another registrar:
\n
\n
    \n
  1. \nActive Registrant Entitlement (Valid ABN/ACN): The domain owner must hold an active, valid ABN, ACN, or Australian trademark that directly matches the registrant record. If an ABN has been cancelled or deregistered with the Australian Taxation Office (ATO) / Australian Business Register (ABR), the domain loses its underlying eligibility and is marked non-compliant.
     
    2. \n
  2. \nUnexpired Domain Status: Domain transfers require an active registration status.
    3. \n
\n

What Happens When a .AU Domain Expires?

\n
Unlike gTLDs (such as .com or .net) which pass through standard grace periods, .au domains enter an Expired Hold / Expired Pending Purge (RGP) state immediately or shortly after missing their renewal deadline:
\n
\n\n

How to Fix Transfer Blocks for .AU Domains

\n
If you need to update your business details or transfer your .au domain to Rebel:
\n
    \n
  1. \nReactivate or Update Your ABN/ACN: If your business entity changed, lapsed, or was re-registered under a new entity, update your legal eligibility details.
     
    2. \n
  2. \n
    \nSubmit a Change of Registrant (Trade) Request & Internal Details: Under auDA rules, updating the ABN/ACN on a .au domain requires a formal Change of Registrant / Trade process. To process this update:
    \n
      \n
    • Enter your new eligibility details directly into the official auDA Change of Registrant documentation provided by our team.
       
      • \n
    • In addition, send an email to service@rebel.com providing these new details in writing so we can update our internal database. Please complete and paste the following template into your email:
      • \n
    \n
    3. \n
\n
\n
    \n
  1. \nRenew the Domain First: If the domain is within 30 days of expiry or already expired, it must be renewed with your current registrar before attempting a transfer.
     
    2. \n
  2. \nInitiate the Transfer: Once the domain status is active and the ABN is verified as valid on the Australian Business Register, obtain your EPP / Transfer Key to proceed.
    3. \n
\n

Need Assistance?

\n
You can start a live chat on our website during business hours or email our support team at service@rebel.com. \n
\n
","user_segment_ids":[]},{"id":56856259143195,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56856259143195.json","html_url":"https://support.rebel.com/hc/en-us/articles/56856259143195-Email-Sending-Limits-Bulk-Mailing-Risks-and-Hourly-Rate-Adjustments-Plesk-Email","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":42631151702427,"created_at":"2026-10-06T19:51:42Z","updated_at":"2026-10-06T19:53:56Z","name":"Email Sending Limits, Bulk Mailing Risks, and Hourly Rate Adjustments (Plesk Email)","title":"Email Sending Limits, Bulk Mailing Risks, and Hourly Rate Adjustments (Plesk Email)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T19:53:56Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you use Plesk Email Hosting with Rebel, your email service is optimized for business communications, billing, and standard transactional messages.
 
This guide explains our platform email sending limits, why bulk mailing poses significant risks to your domain's inbox reputation, and how to request a temporary hourly limit adjustment.
 
\n

Understanding Our Email Sending Limits

\n
To protect shared server IP addresses and ensure optimal delivery for all hosted businesses, Rebel enforces strict outbound email rate limits across both Classic and Plesk hosting servers:
\n
\n\n
\nWhy Limits Exist: Allowing unlimited or unmonitored outbound email streams risks server IP blacklisting across major providers like Gmail, Outlook, and Yahoo. Furthermore, excessive volume will trigger automatic outbound blocking by MailChannels or upstream filtering networks, which can halt all email delivery for your domain.
\n
\n

The Risks of Bulk Mailing on Shared Email Hosting

\n
Standard web hosting servers are not designed for mass email marketing or newsletter blasts. Attempting to send high-volume campaigns (e.g., thousands of emails at once) through Plesk email carries major risks:
\n
\n
    \n
  1. \nMailChannels Spam Filtering & Blocks: MailChannels continuously monitors sending velocity and content patterns. Rapid bursts of similar emails—even legitimate newsletters—are frequently flagged as spam, causing outbound messages to be rejected or deferred.
     
    2. \n
  2. \nDomain & IP Reputation Damage: High bounce rates or recipient spam reports damage your domain's reputation, making future regular business emails land in your recipients' spam folders.
     
    3. \n
  3. \nDelivery Failures: Sending more than 100 emails within a single hour causes remaining messages to queue up or bounce back with sending limit errors.
    4. \n
\n

Best Practices for Sending Larger Batches

\n
If you need to send routine announcements or monthly updates to a moderate subscriber list (e.g., 500 to 1,000 recipients):
\n
\n\n

How to Request an Hourly Rate Limit Increase (Up to 300/hour)

\n
If your business requires a higher hourly throughput (up to a maximum of 300 emails per hour) for legitimate operational needs:
\n
\n
    \n
  1. Contact our support team by submitting a ticket or starting a chat.
     
    2. \n
  2. Provide your domain name and a brief explanation of your email use case (e.g., monthly billing notices or customer updates).
     
    3. \n
  3. Our team will generate an escalation ticket for our Hosting Engineering team to adjust the outbound limit on your Plesk server configuration.
     
    4. \n
  4. You will receive an email update as soon as the configuration update is complete.
    5. \n
\n

Need Extra Assistance?

\n
You can start a live chat on our website during our business hours or email our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
","user_segment_ids":[]},{"id":56854841695643,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56854841695643.json","html_url":"https://support.rebel.com/hc/en-us/articles/56854841695643-What-is-MailChannels-and-Why-is-it-Used-for-Your-Plesk-Email-Hosting","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":42631151702427,"created_at":"2026-10-06T19:27:01Z","updated_at":"2026-10-06T19:27:01Z","name":"What is MailChannels and Why is it Used for Your Plesk Email Hosting?","title":"What is MailChannels and Why is it Used for Your Plesk Email Hosting?","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T19:27:01Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you use Plesk Email Hosting with Rebel.com./ca, your outbound emails rely on an enterprise delivery network called MailChannels.
 
This guide explains what MailChannels does, why it protects your email delivery reputation, and how to properly configure your domain’s SPF (Sender Policy Framework) DNS record when sending email through Rebel or third-party services.
 
\n

What is MailChannels?

\n
MailChannels is a specialized outbound email filtering and delivery service integrated directly into our Plesk hosting servers.
 
\n
When you send an email from your desktop client, mobile app, or webmail using your domain name, your message routes through MailChannels before reaching the recipient’s inbox.
 
\n

Why Does Rebel Use MailChannels for Plesk Email?

\n
    \n
  1. \nGuaranteed Inbox Delivery: MailChannels automatically detects and stops outbound spam, compromised mailboxes, or phishing attempts before they leave the server. This prevents our shared hosting IP addresses from getting blacklisted by major email providers like Gmail, Yahoo, and Microsoft Outlook.
     
    2. \n
  2. \n
    \nAutomatic IP Reputation Protection: If a single account on a server gets compromised, MailChannels isolates that specific account without affecting the email delivery of other businesses hosted on the same server.
    \n

     

    \n
    3. \n
  3. \nAdvanced Security Filtering: It scans outbound mail for malware, malicious attachments, and spam signatures to ensure your domain maintains a high sender reputation.
    4. \n
\n

The MailChannels SPF Record Requirement

\n
Because MailChannels delivers outbound emails on behalf of your domain, your domain’s DNS records must authorize MailChannels as a legitimate sender. This is done through an SPF (Sender Policy Framework) TXT record in your Advanced DNS settings.
 
\n
\n

1. Standard Rebel Plesk Email SPF Record

\n
If you only send emails through your Rebel Plesk email hosting (Webmail, Outlook, Apple Mail, mobile apps):
 
\n
\nv=spf1 a mx include:relay.mailchannels.net -all
 
\n

2. Combining MailChannels with Third-Party Email Providers

\n
If you also send emails using third-party marketing or transactional platforms (such as Mailchimp, SendGrid, Constant Contact, or Google Workspace), you must include all senders within a single SPF record.
\n
\n\n
\nImportant: Never create more than one SPF record for a single domain name. Having multiple SPF records will cause authentication failures and result in your emails landing in spam folders or bouncing back. Always merge external providers into one single v=spf1 record.
\n
\n

Need Extra Help?

\n
You can start a live chat on our website during our business hours or email our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
","user_segment_ids":[]},{"id":56846892412059,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56846892412059.json","html_url":"https://support.rebel.com/hc/en-us/articles/56846892412059-Contested-au-Direct-Domain-Applications-Priority-Holds","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167987,"created_at":"2026-10-06T17:17:21Z","updated_at":"2026-10-06T17:17:21Z","name":"Contested .au Direct Domain Applications & Priority Holds","title":"Contested .au Direct Domain Applications & Priority Holds","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T17:17:21Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you applied for a .au Direct domain (e.g., yourname.au) during the official launch in 2022 and notice that the domain is not active in your account or is listed as \"Priority Hold\" / \"Reserved by Registry\", your application is governed by the official auDA Priority Allocation Process.
 
This guide explains how contested .au Direct applications work under auDA policy, how annual renewals are handled, and what steps you need to take to maintain your claim.
 
\n

1. What is a Contested .au Direct Application?

\n
When .au Direct domain names launched in March 2022, auDA (the .au Domain Administration) created a priority window for existing holders of 3rd-level .au domains (such as .com.au, .net.au, or .id.au) to claim the exact matching .au Direct name.
 
\n
Under the auDA Rules: .au Direct Priority Implementation:
\n\n
When multiple parties apply, auDA assigns applicants a Priority Category based on the creation date of their underlying 3rd-level domain:
\n
\n\n
If applicants fall into competing categories or multiple Category 1 applicants exist, auDA places the domain into Priority Hold status. The domain remains locked in a registry-managed state until the applicants negotiate, one party withdraws, or priority rules trigger allocation.
 
\n
\n

2. Maintaining Your Claim (Annual Application Renewals)

\n
To maintain your priority claim to a contested .au Direct domain, your application must remain active with the registry.
\n
\n\n
\nImportant: If an applicant fails to renew their priority application or allows their underlying 3rd-level domain registration to lapse, their claim is forfeited, and the domain may be allocated to the remaining applicant.
\n
\n

3. Common Misconceptions

\n\n

4. Official auDA Rules & Status Tools

\n
You can review official auDA policy rules or check the real-time status of any contested .au Direct domain using these tools:
\n
\n\n

Need Assistance?

\n
If you have questions about your active priority application or need assistance confirming your annual renewal, please contact our support team at service@rebel.com during business hours.
\n
 
","user_segment_ids":[]},{"id":56845781945243,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56845781945243.json","html_url":"https://support.rebel.com/hc/en-us/articles/56845781945243-How-to-Locate-Missing-Emails-and-Folders-in-Microsoft-Outlook-Plesk-Email","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":42631151702427,"created_at":"2026-10-06T17:01:46Z","updated_at":"2026-10-06T19:54:38Z","name":"How to Locate Missing Emails and Folders in Microsoft Outlook (Plesk Email)","title":"How to Locate Missing Emails and Folders in Microsoft Outlook (Plesk Email)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T19:54:38Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you updated your email settings or migrated servers (such as on canada18.rebel.com or canada2.rebel.ca) and notice that specific subfolders or older messages appear to be missing—while other folders remain intact—your emails may not actually be lost from the server.
 
In most cases, Microsoft Outlook has moved these messages into a local AutoArchive data file (.pst or .ost) on your computer, or stored them in a local offline data cache that is no longer syncing with the server.
 
This guide explains how to locate your local Outlook data files, retrieve missing messages, and prevent Outlook from automatically archiving or hiding your folders in the future.
 
\n

Why Do Folders Go Missing in Outlook?

\n
    \n
  1. \nMicrosoft Outlook AutoArchive: Outlook has a built-in feature called AutoArchive that automatically moves older emails (e.g., messages older than 6 months or 1 year) out of your online mailbox and into a local .pst file saved on your computer's hard drive. When this happens, those folders vanish from both webmail and other devices.
     
    2. \n
  2. \nLocal OST/PST File Separation: When switching server settings or re-configuring an IMAP account in Outlook, Outlook creates a fresh .ost cache file. Your older messages may still reside in the previous .ost or .pst file stored locally on your hard drive.
     
    3. \n
  3. \nIMAP Folder Root Path / Subscribed Folders: Outlook may sometimes fail to subscribe to or display deeply nested subfolders (such as Accounting > Receivables > 2025) until folder synchronization is refreshed.
    4. \n
\n

Step-by-Step Recovery & Fix Guide

\n

\nStep 1: Check Webmail First (webmail.yourdomain.tld)\n

\n
Before searching your computer, log into your Webmail portal directly via your browser. Your Webmail address is always webmail.yourdomain.tld (for example, webmail.yourdomain.com or webmail.yourdomain.ca):
\n
\n\n

\nStep 2: Locate Local .pst and .ost Data Files on Your PC\n

\n
Microsoft Outlook stores archived emails in local data files on your computer. You can check if your missing folders are sitting inside one of these local files:
\n
\n
    \n
  1. Open Microsoft Outlook on your computer.
    2. \n
  2. Click File in the top-left corner > Account Settings > Account Settings...\n
    3. \n
  3. Select the Data Files tab.
    4. \n
  4. Look for files named Archive.pst, Outlook.pst, or secondary account files.
    5. \n
  5. Highlight a data file and click Open File Location... to view the folder on your computer's hard drive.
    6. \n
\n
How to Open an Archive File in Outlook:
\n
Go to File > Open & Export > Open Outlook Data File (.pst). Select your archive file. It will appear in your left-hand Outlook sidebar under a separate section called Archives or Outlook Data File, where you can drag and drop your missing folders back into your main inbox.
 
\n

Step 3: Review & Disable Outlook AutoArchive (Prevent Future Missing Folders)

\n
To prevent Outlook from automatically stripping older emails out of your online mailbox in the future:
\n
\n
    \n
  1. In Outlook, click File > Options.
    2. \n
  2. Click Advanced in the left sidebar.
    3. \n
  3. Under the AutoArchive section, click AutoArchive Settings...\n
    4. \n
  4. \nUncheck the box that says Run AutoArchive every X days.
    5. \n
  5. Click OK to save your settings.
    6. \n
\n

Step 4: Server Restore Options & Important Warnings

\n
If you have searched local .pst/.ost files and cannot locate the missing messages, our technical support team can perform a server-side mailbox restoration from a previous backup date (subject to backup availability).
\n
CRITICAL BACKUP WARNING BEFORE SERVER RESTORATIONS:
Restoring a mailbox from a previous backup date reverts the mailbox back to its exact state on that date. Any new emails sent or received after the backup date will be overwritten and permanently lost.\n
Before requesting a server restoration:
\n
    \n
  1. You must export a backup of your current mailbox locally (File > Open & Export > Import/Export > Export to a file (.pst)).
     
    2. \n
  2. Confirm in writing to our support team that you have backed up your current data and authorize the restoration.
    3. \n
\n

Need Extra Assistance?

\n
You can start a live chat on our website during our business hours or email our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
","user_segment_ids":[]},{"id":56843639247899,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56843639247899.json","html_url":"https://support.rebel.com/hc/en-us/articles/56843639247899-How-to-Fix-Delayed-IMAP-Email-Syncing-on-Samsung-Android-Devices-All-Mail-Apps","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360008352053,"created_at":"2026-10-06T16:26:24Z","updated_at":"2026-10-06T16:27:20Z","name":"How to Fix Delayed IMAP Email Syncing on Samsung Android Devices (All Mail Apps)","title":"How to Fix Delayed IMAP Email Syncing on Samsung Android Devices (All Mail Apps)","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T16:27:20Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you use a Samsung Galaxy smartphone or tablet and notice that incoming emails—especially self-sent messages, folder moves, or new inbox alerts—are taking hours to appear on your phone, your email account settings are likely fine. Instead, Samsung’s built-in Power Saving and Background App Optimization settings are freezing your email app when it runs in the background.
 
This issue affects standard mail applications on Samsung One UI, including:
\n\n
\nNote on Mail App Compatibility: We strongly recommend using Outlook, Samsung Mail, Gmail, or Thunderbird Mobile. Certain older or third-party email apps (like Spark or BlueMail) may fail to connect or sync properly if they do not support current SSL/TLS encryption standards (TLS 1.2+).
\n
\n

Why Do Sync Delays Happen on Samsung Devices?

\n
    \n
  1. \nSamsung Battery Optimization (\"Sleeping Apps\"): To extend battery life, Samsung automatically puts background apps into a \"paused\" or \"sleeping\" state, stopping your mail app from fetching new messages until you open it manually.
     
    2. \n
  2. \nSystem Master Sync Toggled Off: Android’s master Auto Sync feature may be disabled in your phone’s system settings.
     
    3. \n
  3. \nApp Background Data Restrictions: Background network access or internal sync polling intervals may be restricted inside the app's settings.
    4. \n
\n

Step-by-Step Resolution Guide

\n

Step 1: Set Your Mail App Battery Usage to \"Unrestricted\" (Crucial for Samsung)

\n
This prevents Samsung One UI from putting your mail app to sleep when your phone is locked or idle.
\n
\n
    \n
  1. Open your phone's main Settings app.
    2. \n
  2. Scroll down and tap Apps.
    3. \n
  3. Scroll down and select your mail app (Outlook, Samsung Mail, Gmail, Thunderbird, etc.).
    4. \n
  4. Tap Battery.
    5. \n
  5. Change the selection from Optimized to Unrestricted.
    6. \n
\n

Step 2: Verify Master \"Auto Sync Data\" is Enabled

\n
Ensure your phone’s master synchronization switch is active.
\n
\n
    \n
  1. Open your phone's main Settings app.
    2. \n
  2. Tap Accounts and Backup.
    3. \n
  3. Tap Manage Accounts at the top.
    4. \n
  4. Scroll down to the very bottom of your accounts list.
    5. \n
  5. Ensure the toggle switch for Auto sync data (or Auto sync personal data) is switched ON (Blue).
    6. \n
\n
\nNote for Samsung Users: Apps like Microsoft Outlook manage accounts internally within the app rather than as system-level phone accounts. Your email address may not appear directly in Samsung's system list unless you use Samsung Mail, but the master Auto sync data switch at the bottom must be ON for any mail app to receive background updates.
\n
\n

Step 3: Check Internal App Sync Settings

\n
Depending on which mail client you use, confirm that automatic background fetching is turned on:
\n
\n\n

Step 4: Use \"Reset Account\" or Clear App Cache for Quick Repairs

\n
If email folders ever become stuck or stop updating, you can refresh the app without removing your account:
\n
\n\n

Official Reference Documentation

\n
For additional official guides, consult these resources:
\n
\n\n

Need Extra Help?

\n
You can start a live chat on our website during our business hours or email/chat our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
","user_segment_ids":[]},{"id":56842513145115,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56842513145115.json","html_url":"https://support.rebel.com/hc/en-us/articles/56842513145115-How-to-Fix-Connection-Timed-Out-or-ERR-SSL-PROTOCOL-ERROR-When-Accessing-Your-Website-or-WordPress-Admin","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167947,"created_at":"2026-10-06T16:07:36Z","updated_at":"2026-10-06T16:09:23Z","name":"How to Fix \"Connection Timed Out\" or \"ERR_SSL_PROTOCOL_ERROR\" When Accessing Your Website or WordPress Admin","title":"How to Fix \"Connection Timed Out\" or \"ERR_SSL_PROTOCOL_ERROR\" When Accessing Your Website or WordPress Admin","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T16:09:23Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If you are trying to visit your website or log into your WordPress admin dashboard and encounter errors such as \"The connection has timed out\" or \"ERR_SSL_PROTOCOL_ERROR\" (This site can't provide a secure connection), it means traffic between your web browser and the hosting server is being interrupted.
 
These errors occur when a security filter, network block, or firewall drops the secure HTTPS connection (TLS handshake) before the server can load your site.
 
\n

Common Causes

\n
    \n
  1. \nISP or Smart Router Security Shield Blocks: ISP-provided routers and security features (such as Secured by Cogeco, Rogers Xfinity Security, Bell Wi-Fi App, or Xfinity xFi) often use automated security filters (e.g., Trend Micro or Guard24) that incorrectly flag clean domain names or IP addresses as \"Phishing\" or \"Malware.\"
     
    2. \n
  2. \nServer Security / WAF (Imunify360) IP Blocks: Automated server security layers temporarily block your IP address if background applications, browser extensions, or FTP/email clients send multiple failed login attempts using incorrect credentials.
     
    3. \n
  3. \nStale DNS or Local Browser Socket Cache: Your computer or web browser cached a failed route or temporary IP block from a previous connection attempt.
    4. \n
\n

Step-by-Step Troubleshooting Guide

\n

Step 1: Perform the Mobile Hotspot Test (Isolate Your Network)

\n
The quickest way to pinpoint the issue is to test from a different network connection:
\n
\n
    \n
  1. Disconnect your phone or laptop from your home Wi-Fi network.
     
    2. \n
  2. Turn on your mobile phone's Cellular Hotspot and connect your computer to it.
     
    3. \n
  3. Open a Private / Incognito browser window and navigate to your website or WordPress login page (https://yourdomain.ca/wp-admin).
    4. \n
\n\n

Step 2: Check Your ISP App or Smart Router Security Shield

\n
Modern home routers (especially those provided by ISPs like Cogeco, Rogers, or Bell) run built-in network security software that blocks domain names at the modem level.
\n
\n
    \n
  1. Open your ISP’s mobile app on your smartphone (e.g., the Cogeco App, Rogers Xfinity App, or MyBell App).
     
    2. \n
  2. Navigate to Security, Protected Browsing, or Notification Center.
     
    3. \n
  3. Check if your domain name or hosting IP was flagged under Blocked Threats or Phishing Warnings.
     
    4. \n
  4. Select the blocked event and choose Allow Site or Unblock Domain.
    5. \n
\n
Note: In many cases, unblocking the domain inside your ISP app resolves the connection timeout within seconds.
\n
\n

Step 3: Flush Your Local DNS & Clear Browser History

\n
If a temporary network block occurred previously, your operating system and web browser may still have cached the failed route.
\n
\n\n

Step 4: Audit Saved Credentials & Password Managers

\n
If your IP address gets blocked repeatedly by our server's security layer (Imunify360), a saved login setting in your password manager, FTP client, or email app may be repeatedly firing incorrect credentials (e.g., an old username or password) in the background.
\n
\n\n

Still Unable to Connect?

\n
If you have checked your ISP app and verified that your domain is not blocked on your modem, our technical support team is happy to check our server-side firewall logs and whitelist your IP address.
 
\n
When reaching out to our support team, please provide:
\n
    \n
  1. Your current public IP address (found by visiting myip.rebel.com).
     
    2. \n
  2. Whether the website loaded when tested on a mobile cellular hotspot.
     
    3. \n
  3. A screenshot of any error messages displayed in your browser.
    4. \n
\n
You can start a live chat on our website during our business hours or email our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
 
","user_segment_ids":[]},{"id":56841179090203,"url":"https://rebelsupport.zendesk.com/api/v2/help_center/en-us/articles/56841179090203.json","html_url":"https://support.rebel.com/hc/en-us/articles/56841179090203-How-to-Fix-a-WordPress-Site-Redirecting-to-a-Plesk-Preview-URL","author_id":22385318074523,"comments_disabled":false,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":206167947,"created_at":"2026-10-06T15:46:40Z","updated_at":"2026-10-06T15:46:58Z","name":"How to Fix a WordPress Site Redirecting to a Plesk Preview URL","title":"How to Fix a WordPress Site Redirecting to a Plesk Preview URL","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-06T15:46:57Z","user_segment_id":null,"permission_group_id":1926814,"content_tag_ids":[],"label_names":[],"body":"
If visitors trying to access your domain (e.g., yourdomain.ca) are being redirected to a Plesk preview address (like (http://198.57.27.128/plesk-site-preview/yourdomain.ca/)...), your WordPress database is still configured to use the temporary preview path as its primary site address.
 
This typically occurs when WordPress is installed, cloned, or previewed using the temporary server path before the internal WordPress database settings refresh to the primary domain URL.
 
Follow the quick steps below to update your WordPress Site URL directly from your Plesk Control Panel without needing to log into the WordPress admin dashboard.
 
\n

How to Update Your Site URL via WordPress Toolkit

\n

Step 1: Log in to Plesk

\n
Log into your Rebel Control Panel and access Plesk for your hosting subscription.
 
\n
\n

Step 2: Open WordPress Toolkit

\n
In the left-hand navigation menu, Click on WordPress.
 
\n
\n

Step 3: Access Instance Settings

\n
Locate your WordPress installation card in the WordPress Toolkit dashboard. In the top-right corner of your site's card, click the three vertical dots (⋮) menu icon.
 
\n
\n

Step 4: Update Site URL

\n
    \n
  1. Select Update Site URL from the dropdown menu.
     
    2. \n
  2. The toolkit will detect your live domain name (e.g.,(https://yourdomain.ca)).
     
    3. \n
  3. Click Update to apply the changes.
    4. \n
\n
\nWhat happens next: Plesk will automatically rewrite the siteurl and home values in your WordPress database from the IP-based preview address to your primary domain name.
\n
\n

Verification & Troubleshooting

\n
    \n
  1. \nClear Your Web Browser Cache: After running the update, open a new Incognito / Private browsing window and navigate to your domain name directly.
     
    2. \n
  2. \nPermanent Redirects (301 Cache): If your browser still redirects you to the preview page, clear your browser's history and cookies, as web browsers aggressively cache 301 redirects.
    3. \n
\n
Need extra assistance? You can start a live chat on our website during our business hours or email/chat our support team at service@rebel.com (or service@rebel.ca for Rebel.ca account holders).
\n
","user_segment_ids":[]}],"sort_by":"position","sort_order":"asc"}