Before building your site, better take a look at this section.

Extract the zipped package downloaded from ThemeForest to your desktop, in the extracted package you will find the charles.zip file which is the WordPress theme.

You can install the theme in two ways:

FTP: Extract charles.zip file and upload the extracted folder to /wp-content/themes/ folder on your server.

WordPress: Navigate to Appearance -> Add New Themes -> Upload page. Select charles.zip file. Press the Install Now button to upload and install the theme.

After uploading the theme, you have to activate it. Navigate to Appearance -> Themes page to activate the theme.

We are strongly recommended to install “Envato Toolkit” plugin for ease of use. Once necessary plugin installed and activated “Envato Toolkit” menu will be available at your admin side.

Important : If you have missing plugins or having issues to install any of them, all the related could be found under “recommended-plugins” folder within the downloaded package.

User Account Information

To obtain your API Key, visit your “My Settings” page on any of the Envato Marketplaces. Once a valid connection has been made any changes to the API key below for this username will not effect the results for 5 minutes because they’re cached in the database. If you have already made an API connection and just purchase a theme and it’s not showing up, wait five minutes and refresh the page. If the theme is still not showing up, it’s possible the author has not made it available for auto install yet.

Marketplace Username: Enter your Envato marketplace username.

Secret API Key: Enter your Envato marketplace Secret API Key (http://themeforest.net/user/[your-username]/api_keys/edit, Login to your Themeforest account, Settings > API Key)

Backup Information

This plugin will automatically save your theme as a ZIP archive before it does an upgrade. The directory those backups get saved to is wp-content/envato-backups. However, if you’re experiencing problems while attempting to upgrade, it’s likely to be a permissions issue and you may want to manually backup your theme before upgrading. Alternatively, if you don’t want to backup your theme you can check the box below.

Skip Theme Backup: Strongly recommended keep unchecked.

Alternative Way

You can also update the theme by replacing the old theme folder. First go to your theme directory then delete the theme folder and paste the new version of the theme.

In the Header settings section, you will get a lot of header customization options. In this section, you can change the logo and set the menu button, navigation bar settings etc.

Optimizing your images will helps your WordPress site load faster.

Download and activate WP Smush.it This plugin will optimize every image you upload and you can use the Bulk Smush.it feature to smush all of your uploaded images.

Alternatives to WP Smush.it include EWWW Image Optimizer, CW Image Optimizer, Imsanity and Hammy and Compress JPEG & PNG images

Many WordPress users prefer using these plugins as they do not rely on an external server to process your images.

Sometimes, your website may break when you update the new version of the theme.

You have to delete the Charles core plugin before installing the updated theme in this case. Then install the plugin again from Appearance > Install plugins after installing the new version.

What is an Extension?

For editing menu navigation settings go to  Theme Options Header Top of Header . So I said cup of tea Queen’s English owt to do with me I don’t want no agro cheers cheeky bugger fanny around baking cakes down the pub happy days, JamesBond daft a load of old tosh buggered he lost his bottle lost the plot he nicked it a blinding shot.

[docly_tooltip id=”1″]Tooltip text[/docly_tooltip] mufty quaint no biggie cras baking cakes barney bamboozled, what a plonker bum bag he legged it young delinquent knees up Eaton the full monty arse over tit, my lady buggered happy days amongst bugger all mate are you taking the piss brolly. [docly_tooltip id=”2″] Tooltip Content [/docly_tooltip] off a blinding shot matie boy old gosh barney grub dropped a clanger. And for styling menus go to  Theme Options Header Top of Header Menu Styles of this Row

Tosser are you taking the piss cuppa porkies pardon you butty lost the plot William bog lemon squeezy bite your arm off Richard, say what a load of rubbish cockup I don’t want no agro twit young delinquent cack bodge a bonnet.

Unordered list items

Ordered List Items

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your Mautic installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

4. Important Notes:

• Mail Sending Restrictions:
  AWS imposes restrictions on sending emails from EC2 instances by default. To remove this limitation, you may need to submit a request to AWS to lift the email sending blockage before you can use Mautic for email campaigns.

Instance Configuration

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

4. Important Notes:

• Mail Sending Restrictions:
  AWS imposes restrictions on sending emails from EC2 instances by default. To remove this limitation, you may need to submit a request to AWS to lift the email sending blockage before you can use this instance as SMTP server or for email campaigns.

This article is released for AWS solution, “OsTicket with Alma Linux“.

Elyxia Global Limited presents a robust and efficient solution with its pre-configured and hardened AMI with AlmaLinux, a trusted and stable platform. This ready-to-deploy package includes a fully configured stack, with any additional charges clearly specified in the pricing information section, ensuring that your business operations are up and running in no time.

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

This article is released for AWS solution(s),

• Elyxia Support Cloud (ESC) – Your AI Support Team, Ready in Minutes

ESC: Your Own AI Support Team, Live in Under 15 Minutes

Elyxia Support Cloud gives your business a fully managed, AI-powered helpdesk without any infrastructure work. Subscribe through AWS Marketplace, configure your brand and knowledge base, and your AI agents are answering real customer questions – on your own domain – in under 15 minutes.

Unlike shared, multi-tenant helpdesk platforms, every ESC customer gets a dedicated, isolated instance. Your customer conversations are never co-mingled with anyone else’s, and your configuration and performance are yours alone. This matters for regulated industries, for data-residency requirements, and for anyone who would simply rather not have their customers’ data sitting in a stranger’s database.

AI is not a premium add-on here. Every plan – starting at $199/month, flat, for your whole team – includes AI agents that answer web chat and email tickets automatically from your own uploaded documents, escalating to your human team when they should. There are no per-agent fees.

Included in Every Plan

• Dedicated, isolated instance: Your own helpdesk, your own data. No co-mingling, no noisy neighbours.
• AI support agents: Answer web chat and email tickets automatically from your knowledge base, with confidence controls and clean handoff to your human team.
• Knowledge base: Upload PDF, Word, Excel, PowerPoint, TXT, CSV or Markdown – indexed automatically and answering within seconds. No tagging, no formatting.
• Web chat widget: One HTML snippet, embedded on any website, fully styled to your brand.
• Customer support portal: A branded self-service portal where your customers submit and track their tickets.
• Agent workspace: A full admin site for your human team to review, respond, and collaborate on escalated tickets.
• True white-label: Your domain, your logo, your colours, your AI agent names. Third-party names and infrastructure menus are swept out before you ever log in.
• Free SSL: Auto-provisioned and auto-renewed on your custom domain.
• Nightly backups: 30-day retention, with all data encrypted in transit.
• Full conversation history: Every conversation recorded and searchable, for audit and continuous improvement.
• Fully managed: There are no servers for you to run. Provisioning, SSL, nightly backups, scaling on upgrade, security patching, and platform updates are all handled for you. You manage your brand, your agents, and your knowledge – we manage everything underneath.

Free 15-day trial. Spin up your fully branded AI helpdesk, train it on your own documents, and put it through its paces before you commit. No credit card lock-in.

Available regions: Ireland, London, Singapore, and US East (N. Virginia) – with further regions in progress.

This article is released for AWS solution(s),

• Elyxia Support Cloud (ESC) – Your AI Support Team, Ready in Minutes

ESC: Your Own AI Support Team, Live in Under 15 Minutes

Elyxia Support Cloud gives your business a fully managed, AI-powered helpdesk without any infrastructure work. Subscribe through AWS Marketplace, configure your brand and knowledge base, and your AI agents are answering real customer questions – on your own domain – in under 15 minutes.

Unlike shared, multi-tenant helpdesk platforms, every ESC customer gets a dedicated, isolated instance. Your customer conversations are never co-mingled with anyone else’s, and your configuration and performance are yours alone. This matters for regulated industries, for data-residency requirements, and for anyone who would simply rather not have their customers’ data sitting in a stranger’s database.

AI is not a premium add-on here. Every plan – starting at $199/month, flat, for your whole team – includes AI agents that answer web chat and email tickets automatically from your own uploaded documents, escalating to your human team when they should. There are no per-agent fees.

Included in Every Plan

• Dedicated, isolated instance: Your own helpdesk, your own data. No co-mingling, no noisy neighbours.
• AI support agents: Answer web chat and email tickets automatically from your knowledge base, with confidence controls and clean handoff to your human team.
• Knowledge base: Upload PDF, Word, Excel, PowerPoint, TXT, CSV or Markdown – indexed automatically and answering within seconds. No tagging, no formatting.
• Web chat widget: One HTML snippet, embedded on any website, fully styled to your brand.
• Customer support portal: A branded self-service portal where your customers submit and track their tickets.
• Agent workspace: A full admin site for your human team to review, respond, and collaborate on escalated tickets.
• True white-label: Your domain, your logo, your colours, your AI agent names. Third-party names and infrastructure menus are swept out before you ever log in.
• Free SSL: Auto-provisioned and auto-renewed on your custom domain.
• Nightly backups: 30-day retention, with all data encrypted in transit.
• Full conversation history: Every conversation recorded and searchable, for audit and continuous improvement.
• Fully managed: There are no servers for you to run. Provisioning, SSL, nightly backups, scaling on upgrade, security patching, and platform updates are all handled for you. You manage your brand, your agents, and your knowledge – we manage everything underneath.

Free 15-day trial. Spin up your fully branded AI helpdesk, train it on your own documents, and put it through its paces before you commit. No credit card lock-in.

Available regions: Ireland, London, Singapore, and US East (N. Virginia) – with further regions in progress.

Instance Configuration

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

4. Important Notes:

• Mail Sending Restrictions:
  AWS imposes restrictions on sending emails from EC2 instances by default. To remove this limitation, you may need to submit a request to AWS to lift the email sending blockage before you can use this instance as SMTP server or for email campaigns.

If you want your site to look like exactly the ‘Charles’ demos then you have to import the demo content successfully.

We integrated the One Click Demo installation feature to ‘Charles’ WordPress theme. You can import all demo content just by a click only.

OneClick Demo Installation Process

• Install the theme and active it. Then install all required plugins. Make sure all the required plugins are activated.
• After activating all the required plugins navigate to Appearance > ‘One Click Demo Import’ menu from the WordPress dashboard.

Note: If the option data do not import then you have to import it manually. Navigate to ‘Theme Settings > Backup’. Then copy-paste the backup string here and click on the Import a Backup button. You will find the backup string in the options.txt file.

The recommended method to import the demo content.

If you failed to import the demo content by one click then you have to follow the below steps to import the demo content manually.  You will get all demo content data with the theme package. You will find the demos in ‘charles>inc/demo{disired-demo-number} this path.

• Navigate to Tools > Import then install the WordPress plugin and click on the ‘Run Importer’. Upload here the ‘theme_content.xml’ file.
• Install the ‘Widget Importer & Exporter‘ plugin to import the demo widgets. Then navigate to Tools > Widget Importer & Exporter and upload here the ‘widget_data.wie’ file.
• Now you have to import the Dental Options as like the demo. Navigate to ‘Theme Settings > Backup’. Then copy-paste the backup string here and click on the Import a Backup button. You will find the backup string in the options.txt file.

Harum proident? Volutpat sint. Dicta. Eleifend, distinctio placeat nec commodo asperiores posuere fusce illo, adipiscing leo velit ipsum. Mauris enim itaque penatibus, consectetur fermentum, vel temporibus interdum

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your Mautic installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

4. Important Notes:

• Mail Sending Restrictions:
  AWS imposes restrictions on sending emails from EC2 instances by default. To remove this limitation, you may need to submit a request to AWS to lift the email sending blockage before you can use Mautic for email campaigns.

Go to Appearance > Customize > Site Identity. Then Select an image as site icon. It’s recommended to use a .ico image as the site icon (favicon).

Plans & Allowances

Every ESC plan includes the full platform. The tiers differ in capacity, not capability.

No per-agent fees. Your monthly price covers your whole team.

Allowances are per helpdesk

This is worth being clear about, especially if you run more than one helpdesk.

Each helpdesk has its own allowances. Its own AI responses, its own agents, its own domains, its own knowledge storage. They are not pooled across your account. If one helpdesk exhausts its monthly AI responses, your other helpdesks are unaffected.

AI responses

One AI response = one genuine answer from your AI agent. Automatic acknowledgements and canned replies do not count against your allowance.

Your allowance reloads monthly and does not roll over. You can see usage on each helpdesk’s Overview and on your Billing page.

If a helpdesk runs out, its AI agents hand conversations to your human team instead of answering. Nothing breaks and nothing is lost – the helpdesk keeps running, tickets keep arriving, and your team keeps working them in the agent workspace. You simply lose the automatic answers until the allowance reloads.

Running out of AI responses

You have two options.

Upgrade the helpdesk to a larger plan, on AWS Marketplace. This raises its monthly allowance permanently. See Upgrading Your Plan.

Or buy a one-time AI response pack. These are optional top-ups, bought from the Plans & Billing page in your portal:

• Never expire. Unused responses stay on the helpdesk indefinitely.
• Used only after that month’s plan allowance is spent. Your plan allowance always goes first, so a top-up is never wasted.
• Applied to one helpdesk. You choose which.
• Paid by card, in the portal. This is a one-time purchase and is not part of your AWS subscription – your subscription and your AWS billing are unaffected.

Which should you choose? If you’re consistently running out, upgrade – the monthly allowance is far better value. Top-up packs are for one-off spikes: a product launch, a busy season, an incident.

Additional helpdesks

You are not limited to one helpdesk. From the Plans & Billing page, Buy a New Instance on any tier to add another – useful if you run several brands, or if you’re an agency deploying a helpdesk per client.

Each additional helpdesk is purchased through AWS Marketplace and appears on your AWS bill. Each is fully independent: its own dedicated instance, its own domain, its own branding, its own AI agents, its own knowledge base, and its own allowances. They do not share data.

You can mix tiers freely – a Growth helpdesk for one brand and a Starter for another.

The other limits

• AI agents – the roster limit for that helpdesk. Upgrading expands it automatically.
• Custom domains – how many domains you can point at that helpdesk.
• Knowledge storage – the total size of documents uploaded to that helpdesk. A live meter on the Knowledge tab shows where you stand.

Enterprise

If your volumes, your structure, or your contractual requirements don’t fit the published tiers, Enterprise is available via private offer on AWS Marketplace. Contact [email protected].

Your Domain & SSL

Putting your helpdesk on your own domain is the single highest-value setup step. It’s what turns a working helpdesk into your helpdesk.

What it unlocks

• Your customer support portal at your own address.
• Your agent workspace at your own address.
• A branded support email address ([email protected]).
• Your AI agents can share your real contact details when handing off a conversation. Until a domain is verified, they stay silent on contact details rather than quoting an address that isn’t yours.
• Free SSL, provisioned and renewed automatically.

How to add a domain

1. Open your helpdesk in the portal and go to the Access & Domains tab.
2. Click Add Domain and enter your domain (for example, support.yourcompany.com).
3. The portal shows you an IP address. In your domain’s DNS settings, add an A record pointing your domain to that IP.
4. Wait for DNS to propagate. ESC verifies the domain automatically.
5. Once verified, SSL is provisioned automatically. When the status reads Active, your https:// address is live.
6. Optionally, set the domain as Primary so it becomes your default access address.

CloudFlare users, read this. Set the record to DNS-only (grey cloud), not proxied (orange cloud). Proxy mode prevents domain verification and blocks the SSL certificate from being issued. This is the most common reason a domain gets stuck.

Don’t sit and wait

DNS propagation takes time, and nothing else in your setup depends on it. Add the domain, set the A record, then carry straight on with branding, agents and knowledge. It will complete in the background.

Your access links

The Access & Domains tab always shows you how to reach your helpdesk:

• Before your domain is active: a direct address is shown, so you can always get in.
• Once SSL is Active: your branded https:// links appear – one for your agent workspace, one for your customer support portal.

How many domains?

Your plan sets the limit: Starter 1, Growth 2, Pro 3, Enterprise unlimited.

If something isn’t working

• Domain stuck on pending: check the A record points to the exact IP shown in the portal, and that CloudFlare proxy is off.
• SSL not activating: SSL can only be issued once the domain verifies, so fix verification first.
• Chat isn’t sharing your support email: that’s this page’s job – the domain isn’t verified yet. Once it is, it fills in automatically.

What is an Extension?

For editing menu navigation settings go to  Theme Options Header Top of Header . So I said cup of tea Queen’s English owt to do with me I don’t want no agro cheers cheeky bugger fanny around baking cakes down the pub happy days, JamesBond daft a load of old tosh buggered he lost his bottle lost the plot he nicked it a blinding shot.

[docly_tooltip id=”1″]Tooltip text[/docly_tooltip] mufty quaint no biggie cras baking cakes barney bamboozled, what a plonker bum bag he legged it young delinquent knees up Eaton the full monty arse over tit, my lady buggered happy days amongst bugger all mate are you taking the piss brolly. [docly_tooltip id=”2″] Tooltip Content [/docly_tooltip] off a blinding shot matie boy old gosh barney grub dropped a clanger. And for styling menus go to  Theme Options Header Top of Header Menu Styles of this Row

Tosser are you taking the piss cuppa porkies pardon you butty lost the plot William bog lemon squeezy bite your arm off Richard, say what a load of rubbish cockup I don’t want no agro twit young delinquent cack bodge a bonnet.

Unordered list items

Ordered List Items

Associating Your Domain with OsTicket

Overview:

To successfully associate your domain with the OsTicket hosted on an AWS instance, follow the steps outlined below. This process involves editing the Apache configuration file to link your domain with the server’s IP address and enforce HTTPS redirection.

Step 1: Access Your Server

1. Log in via SSH

• Use SSH to access your AWS instance:

2. Switch to the Root User

• Elevate your permissions by switching to the root user:

Step 2: Modify the Apache Configuration File

1. Edit the Configuration File

• Open the Apache configuration file:

2. Update Domain Information

• Replace the placeholder yourdomain.com with your actual domain name in the configuration. Ensure that both the non-www and www versions of your domain are included. Also, modify the RewriteRule directives to enforce HTTPS redirection.

Below is the updated configuration you need to apply:

<VirtualHost *:80>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/osticket
ErrorLog /var/www/osticket/log/error.log
CustomLog /var/www/osticket/log/requests.log combined

<Directory /var/www/osticket>

Options +FollowSymLinks
AllowOverride All
Require all granted

</Directory>

</VirtualHost>

<VirtualHost *:443>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/osticket
ErrorLog /var/www/osticket/log/error.log
CustomLog /var/www/osticket/log/requests.log combined

 <Directory /var/www/osticket>

Options +FollowSymlinks
AllowOverride All
Require all granted

</Directory>

</VirtualHost>

3. Save and Exit

• After making the necessary changes, save the file by pressing Ctrl + O, then press Enter to confirm. Exit the editor by pressing Ctrl + X.

Step 3: Refresh Symbolic Links & Restart Apache

• For the changes to take effect, recreate the symbolic links and then restart the Apache web server:

Additional Notes:

• Ensure that you have an SSL certificate installed for HTTPS to work. You may use services such as Let’s Encrypt to obtain a free SSL certificate.
• You might need to adjust firewall rules or security group settings in AWS to allow traffic on ports 80 (HTTP) and 443 (HTTPS).
• Important: Request AWS to lift any email sending restrictions if you’re using the application’s email features.

All of our Themes are able to be translated into any language. The process of translating the theme is a user responsibility. The following instructions are given as guidance.

1. Open wp-config.php and replace this: define ('WPLANG', ''); with this (substitute the language string (bg_BG) with your own!): define ('WPLANG', 'bg_BG');
2. Download and install POEDIT
3. Connect to your site -> open your theme/languages directory
4. Download the default.pot file and open it with POEDIT.
5. Translate file and save it as bg_BG (the file name must match with the string you inserted into wp-config.php)
6. Two files will be generated after save. bg_BG.pot and bg_BG.mo
7. Upload the .mo and .pot files into wp-content/themes/your-theme/languages folder

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

t3a.small or t3.small (recommended) – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

What is an Extension?

For editing menu navigation settings go to  Theme Options Header Top of Header . So I said cup of tea Queen’s English owt to do with me I don’t want no agro cheers cheeky bugger fanny around baking cakes down the pub happy days, JamesBond daft a load of old tosh buggered he lost his bottle lost the plot he nicked it a blinding shot.

[docly_tooltip id=”1″]Tooltip text[/docly_tooltip] mufty quaint no biggie cras baking cakes barney bamboozled, what a plonker bum bag he legged it young delinquent knees up Eaton the full monty arse over tit, my lady buggered happy days amongst bugger all mate are you taking the piss brolly. [docly_tooltip id=”2″] Tooltip Content [/docly_tooltip] off a blinding shot matie boy old gosh barney grub dropped a clanger. And for styling menus go to  Theme Options Header Top of Header Menu Styles of this Row

Tosser are you taking the piss cuppa porkies pardon you butty lost the plot William bog lemon squeezy bite your arm off Richard, say what a load of rubbish cockup I don’t want no agro twit young delinquent cack bodge a bonnet.

Unordered list items

Ordered List Items

Instance Configuration Requirements

Overview:

When setting up your AWS instance, you’ll need to configure a few key options. Here’s a detailed guide on the recommended configurations and selections.

1. Instance Type

For optimal performance, we recommend using the following instance types:

• t3a.small – 2 virtual CPUs and 2 GB memory. 
• t3.small – 2 virtual CPUs and 2 GB memory. 

However, you can choose an instance type based on your specific workload and traffic needs. Here’s a quick reference table to help you decide:

For more details on different instance types and configurations, refer to the AWS Instance Types documentation.

2. Storage Space

The default allocated storage size for our AMI. You may specify the necessary storage size when launching a new instance or change it after deployment.

20 GB (recommended)

3. Ports Configuration

To ensure smooth operation of your Mautic installation, it’s important to open the appropriate inbound and outbound ports. Below are the recommended port settings, though you may configure them based on your specific security group requirements:

Inbound Ports:

Outbound Ports:

4. Important Notes:

• Mail Sending Restrictions:
  AWS imposes restrictions on sending emails from EC2 instances by default. To remove this limitation, you may need to submit a request to AWS to lift the email sending blockage before you can use for email sending.

Odoo 19 Initialization:

Overview:

This guide will walk you through initializing Odoo 19 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip>:8069 (port 8069) :

• You will be greeted by the welcome screen.

3. Login:

• Use the credentials provided during the installation process to log in.

• If login is successful, then you will be able to see the screen below.

4. Disable “Manage Database”:

• Recommended Step: To DISABLE “Manage Databases” link at login page, you will need to add the line below to Odoo configuration file /etc/odoo/odoo.conf

“list_db = False”

• Go to your instance SSH command prompt and run the following command at root

• Then add the line below to the file and save the file.

list_db = False

• Restart odoo and apache to reflect the changes

UVDesk Initialization:

Overview:

This guide will walk you through initializing UVDesk on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> :

• You will be greeted by the welcome screen.

Step 3: Finalizing Installation  

1. Welcome:

• Click Let’s Begin to start.

2. System Requirement:

• The installer will auto-detect all the requirement is met. You shall see all requirement are ticked as we pre-configured the instance for you. Click “Proceed” to go to next step.

3. Database Configuration:

• Get the database credentials from the summary of initialization script earlier and fill up the database settings, as below.

Server: 127.0.0.1
Port: 3306
Server Version: 11.5
Username: root
Password: (the root credential generated in Step 1)
Database: uvdeskdb

• Once done, press ‘Proceed‘.

4. Admin Details:

• Fill up all fields accordingly as per your business needs.
• Take note of the email and password as you will use them to log into UVDesk Admin Panel.

5. Installation:

• Click “Install Now” to start the installation. Once installation is done, you will be welcomed with the links to your knowledgebase and admin panel.

• Once the setup is complete, you will see the final “Congratulations” screen as below.

• Navigate to http://<your-public-ip>/scp/login.php and login with the Administrator credentials you entered in the “Admin User” section earlier.

Step 4: Post Installation – Recommended by UVDesk

1. Set APP_ENV to Prod

• Go to your instance SSH command prompt and run the following command at root

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

Mautic 5 Initialization:

Overview:

This guide will walk you through initializing Mautic 5 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the Mautic installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session.

Step 2: Access Mautic After Installation

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes your Mautic admin credentials.

2. Access the Mautic Interface:

• Open your web browser and navigate to:

• You will be greeted by the Mautic login screen.

3. Login:

• Use the credentials provided during the installation process to log in.
• You can then update your account details in the settings as needed.

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using Mautic for email campaigns, submit a request to AWS to lift the restriction on outbound email traffic.

ISPConfig 3.2 Initialization:

Overview:

This guide will walk you through initializing ISPConfig 3.2 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to:

• You will be greeted by the welcome screen.

3. Login:

• Use the credentials provided during the installation process to log in.
• You can then update your account details in the settings as needed.

Important Notes:

• Your Connection is Not Private:
  If you encounter “Your connection is not private” warning due to SSL requirement. You may click “Advanced” button and then click the link, “proceed to your-ip-address (unsafe)” to bypass.
• This warning will be automatically resolved when your instance is installed with a SSL

OpenCart Initialization:

Overview:

This guide will walk you through initializing OpenCart on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted. 

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> :

• You will be greeted by the welcome screen.

Step 3: Finalizing Installation  

1. Welcome:

• Click Continue to agree and start the setup.

2. Pre-Installation:

• The installer will auto-detect all the requirement is met. You shall see all requirement are ticked as pre-configured the instance for you. Click “Continue” to go to next step.

3. Database Configuration:

• Get the database credentials from the summary of initialization script earlier and fill up the database settings, as below.

Section 1: Database Details

DB Driver: MySQLi
Hostname: localhost
Username: (the DB username generated in Step 1)
Password: (the DB credential generated in Step 1)
Database: opencartdb
Prefix: (anything, you may leave it as it is)
Port: 3306

Section 2: Administration

Username: (anything, this will be admin login username)
Password: (anything, this will be admin login password)
Email: opencartdb

• Once done, press ‘Continue‘.

4. Installation Complete:

• Congratulation! OpenCart application is installed on your server.
• Next, we need to clean up and tighten the security of your installation.
• Once the setup is complete, you will see the final “Congratulations” screen as below.

Step 4: Post Installation – Recommended by OpenCart

• According to OpenCart’s security recommendations, the following additional steps are essential to harden your OpenCart installation:

• • ✅ Set correct file and folder permissions to prevent unauthorized access.
  • ✅ Remove the ‘install’ folder to eliminate potential security risks.
  • ✅ Update all configuration files to reflect the changes.

• No need to worry—we’ve got you covered! 🎯 Our automated installation script already perform all these actions exactly as recommended by OpenCart.
• Once the script is done running, you may proceed to login.

• Enter the username and password you set in Step 4 and press “Login“.

http://<your-public-ip>/admin

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

Odoo 17 Initialization:

Overview:

This guide will walk you through initializing Odoo 17 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip>:8069 (port 8069) :

• You will be greeted by the welcome screen.

3. Login:

• Use the credentials provided during the installation process to log in.

• If login is successful, then you will be able to see the screen below.

4. Disable “Manage Database”:

• Recommended Step: To DISABLE “Manage Databases” link at login page, you will need to add the line below to Odoo configuration file /etc/odoo/odoo.conf

“list_db = False”

• Go to your instance SSH command prompt and run the following command at root

• Then add the line below to the file and save the file.

list_db = False

• Restart odoo and apache to reflect the changes

OrangeHRM Initialization:

Overview:

This guide will walk you through initializing OrangeHRM on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> :

• You will be greeted by the welcome screen.

Step 3: Finalizing Installation  

1. Welcome:

• Click Next to start.

2. License Acceptance:

• Check the “I accept …” box to agree to the terms and click Next to proceed.

3. Database Configuration:

• Select “Existing empty database” as our initialization script already created the database for you.
• Get the database credentials from the summary of initialization script earlier and fill up the configuration as below.

Server: localhost
Port: 3306
Username: dbadmin
Password: (the root credential generated in Step 1)
Database: orangehrmdb

• Check the “Enable Data Encryption“
• Once done, press ‘Next‘.

4. System Check:

• You shall see all requirement are ticked as we have pre-configured the instance for you. Click “Next” to go to next step.

5. Instance Creation:

• Fill up all fields accordingly as per your business needs. Click “Next” to proceed when done.

6. Admin User Creation:

• Fill up all fields accordingly as per your business needs.
• Take note of the Admin username and password as you will use them to log into Admin Panel.

7. Confirmation:

• Confirm all details on this screen. Click “Back” to edit them otherwise click “Install“.

8. Installation:

• If everything goes well, you will the progress bar reaching 100% as shown. Click Next.

9. Installation Complete:

• Once the installation is complete, you will see the final “Congratulations” screen as shown.
• Click “Launch OrangeHRM” to proceed to login.

10. OrangeHRM Dashboard:

• Use the Admin credentials you created earlier to login and OrangeHRM panel will be waiting for you. 

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

Bagisto Initialization:

Overview:

This guide will walk you through initializing Bagisto on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> :

• You will be greeted by your Bagisto ecommece frontend.

Step 3: Access to Bagisto Admin Panel  

1. Log into Admin Panel:

• Get the admin login path from the summary of initialization script earlier (in Step 2.1).
• Open your web browser and navigate to the login http://<your-public-ip>

• Login with the credentials from the summary of initialization script earlier (in Step 2.1)
• You may change the admin path by changing “APP_ADMIN_URL” value of the environment file (.env) file inside /var/www/bagisto.

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

Zammad Initialization:

Overview:

This guide will walk you through initializing Zammad on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> :

• You will be greeted by Zammad welcome screen. Click “Set up a new system” to proceed with installation.

Step 3: Finalizing Installation  

1. Administrator Account:

• Fill up all fields accordingly as per your business needs. Click “Create” to proceed when done.
• Take note of the email and password as you will use them to log into Zammad panel.

2. Organization:

• Fill up all fields accordingly as per your business needs.
• System URL: <your public ip> (auto detected, you may leave it as default).   
• Click “Next” to proceed.

3. Email Notification:

• You may choose “Local MTA” or “SMTP“.
• If you choose “Local MTA” you may need to contact (send them a ticket) AWS to allow SMTP port. By default it is barred, unless otherwise requested to be lifted. Our advice is to “SMTP” setting to configure your own outgoing SMTP setting.
• Alternatively, you may click “Skip” and perform the setting later in Zammad panel. When inside the panel, go to Settings > Channels > Email then look for Outbound.

4. Connect Channels:

• You may click “Email” to fill up the channel. Or press “Skip” to set them inside Zammad panel.

5. Dashboard:

• Congratulations! You have successfully installed and logged into Zammad.

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

ERPNext Initialization:

Overview:

This guide will walk you through initializing ERPNext on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to:

• You will be greeted by the login screen.

Step 3: Finalizing Installation  

1. Welcome – General Information 

• Enter relevant details and click Next to proceed.

3. Account Details  

• This will be a new login credentails apart from your Administrator details provided earlier.
• Enter Next to proceed.

4. Organization Details

• Enter the details and click Complete Setup to complete the final step.

• Wait until the setup process is complete.

5. Dashboard

• Once the setup is complete, you will automatically be logged into Dashboard.
• The bundle is pre-installed with ERPNext apps: HRMS, Helpdesk and Payments.

Important Notes:

• Your Connection is Not Private:
  If you encounter “Your connection is not private” warning due to SSL requirement. You may click “Advanced” button and then click the link, “proceed to your-ip-address (unsafe)” to bypass.
• This warning will be automatically resolved when your instance is installed with a SSL

Matomo 5 Initialization:

Overview:

This guide will walk you through initializing Matomo 5 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).

• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to:

• You will be greeted by the welcome screen.

Step 3: Finalizing Installation  

1. Welcome Screen

• Click Next to proceed to system check.

2. System Check

• Hit Next since critical errors has been cleared by our initialization script. (You may ignore the optional warnings  “Forced SSL Connection” and “PHP SAPI” for now.)

3. Database Setup:

• Get the database credentials from the summary of initialization script earlier and enter here.
• Ensure “MariaDB” is selected as the Database Engine. Leave the rest as its default values.
• Enter Next to start the set up.
• You will see the green screen “Tables created“, when the database is setup successfully.
• Enter Next again.

3. Administrator Account (SuperUser):

• Fill up the Administrator (superuser) form.
• You will use these credentials to access Matomo later.
• Enter Next when it is done.

4. Set up a Website:

• Fill up the website form accordingly.
• We strongly recommend to use AWS IP for the “Website URL” field like http://<your-aws-public-ip>/ 
• Note: It is http:// and not https://.

5. Login to Matomo:

• Enter Next at the “Tracking code for Any Website” screen.
• And the final “Congratulations” screen is waiting for you.

• Enter “Continue to Matomo” to login.
• Use the credential you created in the SuperUser section to log into Matomo.
• Once logged in, get ready for the final touch up’s.

Step 4: Post Installation – Recommended by Matomo

1. Start the CRON

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• While our initialization script has already set up CRON, you will need to initiate the job and change to your preferred email address.
• Run the following command to change email address for the report. Replace the [email protected] with the actual email address.

• After that, run this command to start the CRON job:

2. Disable Archiving for Performance

• Log into Matomo at http://<your-aws-public-ip>/
• Go to Admistration, click Gear icon on the top right corner of the sreen.
• Select System > General Settings on the left panel.
• Set “Archive reports when viewed from the browser” to No
• Set “Archive reports at most every X seconds” to 3600
• Hit the “Save” button

• Now, your Matomo system is ready for medium to high traffic handling.
• You may follow this link to associate a domain with your IP. address.
• Use Let’s Encrypt to set up SSL and https:// when you have the domain associated.

Important Notes:

Required Private Directories False Alarm:

To resolve occasional false alerts for the critical issue related to the tmp/cache/tracker/matomocache_general.php file, you can safely delete this cache file.
Afterward, restart Apache to ensure any changes take effect.

This should clear the alert. If the file reappears without issues, it’s simply Matomo regenerating its cache, which is expected behavior.

Mail Sending Blockage:

AWS may have email-sending restrictions in place by default. If you wish to use AWS as SMTP server for email campaigns or sending, submit a request to AWS to lift the restriction on outbound email traffic.

Choosing Your Plan

ESC has three published plans plus a custom Enterprise tier. Every plan includes the same core platform – a dedicated instance, AI agents, knowledge base, web chat, email channel, customer support portal, agent workspace, free SSL, and nightly backups. The tiers differ in capacity, not capability.

There are no per-agent fees. The monthly price covers your whole team.

Which plan?

AI responses is usually the figure that decides it. One AI response = one genuine answer from your AI agent. Automatic acknowledgements and canned replies don’t count against it.

• Starter – small teams, a single brand, modest ticket volume.
• Growth – the common choice: a busier helpdesk, more agents, a second domain.
• Pro – high volume, a larger human team, and priority support when you need us.
• Enterprise – multiple helpdesks, custom volumes, or specific contractual requirements. Available via private offer: contact [email protected].

Changing your mind later

You aren’t locked in. Same-tier upgrades take effect instantly. Larger-tier upgrades are handled via secure snapshot-restore – your data carries over, and your domain and address stay the same. Your AI agent roster automatically expands to the new tier’s limit.

Cockpit (https://cockpit-project.org/) is a web-based graphical interface for servers management and administration. This particular AMI is pre-installed with Cockpit to ease administration. To start using Cockpit, follow the steps below.

• Step 1: Get the Cockpit credentials output from execution of “usr/local/bin/egl_init.sh.x”
• Step 2: Go to http://<your-public-ip>:9090/ and enter the credentials.

• Step 3: You may see “limited access” and may be prompted to authenticate. Click “Turn on administrative access“, key in once again the credential from Step 1.

Uploading File with Cockpit 

• Step 1: Login to Cockpit.
• Step 2: Go to “navigator“.
• Step 3: To upload files to server using Cockpit, simply navigate to your path and just drag-and-drop into the folder.

SuiteCRM 8.x Initialization:

Overview:

This guide will walk you through initializing SuiteCRM 8.6 – 8.9 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> (port 80) :

• You will be greeted by the login screen.

3. Login:

• Use the credentials provided during the installation process to log in.
• You can then update your account details in the settings as needed.

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

After installing the theme you most have to install the ‘Charles Core’, ‘Elementor’ and ‘Piklist’ plugins to import the demo content as well and work the theme correctly.

You will find all required and recommended plugins at Appearance > Install Plugins.

ESC Client Portal

Where: https://esc.elyxia.uk/awslogin

Who: you, the account owner.

This is your control room. You’ll do nearly everything here.

Signing in

Sign in with the email and password you created when you set up your account after subscribing on AWS Marketplace. There’s no billing to manage here – your subscription is handled by AWS.

What’s in it

Your Dashboard lists your helpdesk. Open it, and you get a set of tabs:

Changes you save here flow to your live helpdesk automatically. There’s no redeploy, no downtime, and nothing to restart.

This is where “fully managed” shows up in practice. There is no server for you to log into and no infrastructure to tune. If a setting isn’t in the portal, it’s something we handle for you.

Mautic 6 Initialization:

Overview:

This guide will walk you through initializing Mautic 6 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the Mautic installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session.

Step 2: Access Mautic After Installation

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes your Mautic admin credentials.

2. Access the Mautic Interface:

• Open your web browser and navigate to:

• You will be greeted by the Mautic login screen.

3. Login:

• Use the credentials provided during the installation process to log in.
• You can then update your account details in the settings as needed.

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using Mautic for email campaigns, submit a request to AWS to lift the restriction on outbound email traffic.

Please make sure you have generated and set menus on “Appearance > Menus”.

“Main Menu” menu locations have to be filled to make the menus work as expected.

Upgrading Your Plan

You are not locked into the plan you started on.

How to upgrade

Upgrades are purchased through AWS Marketplace, the same way your original subscription was. The Plans page in your ESC portal will hand you to AWS to complete it.

What happens to your helpdesk

This is the part people worry about, so here it is plainly: you keep everything.

• Same-tier upgrades take effect instantly, with no downtime.
• Larger-tier upgrades are handled by a secure snapshot-restore. Your data carries over in full.
• Your domain and your address do not change. Your customers and your team notice nothing.
• Your AI agent roster automatically expands to the new tier’s limit, with ready-to-use agents.
• Your branding, knowledge base, channels and history all carry over untouched.

There is nothing for you to rebuild, re-upload, or reconfigure.

Downgrading

If you need to move to a smaller plan, contact [email protected] first. Your current usage may exceed the smaller plan’s limits – more agents than it allows, or more knowledge storage than it permits – and we’d rather help you land that safely than have you discover it afterwards.

Create a new page

1. On the top left side of the WordPress dashboard, click Pages > Add New
2. Click Edit with Elementor to enter Elementor Page Builder.

The website editing screen is located on the right side. This is your workspace, where you can add sections and templates.

The panel is located on the left side of the screen and contains creative tools called widgets, that allow you to add elements to your page.

Some of the most commonly used widgets include Button, Image, text, and more.

To find a specific widget, use the search field.

What is an Extension?

For editing menu navigation settings go to  Theme Options Header Top of Header . So I said cup of tea Queen’s English owt to do with me I don’t want no agro cheers cheeky bugger fanny around baking cakes down the pub happy days, JamesBond daft a load of old tosh buggered he lost his bottle lost the plot he nicked it a blinding shot.

[docly_tooltip id=”1″]Tooltip text[/docly_tooltip] mufty quaint no biggie cras baking cakes barney bamboozled, what a plonker bum bag he legged it young delinquent knees up Eaton the full monty arse over tit, my lady buggered happy days amongst bugger all mate are you taking the piss brolly. [docly_tooltip id=”2″] Tooltip Content [/docly_tooltip] off a blinding shot matie boy old gosh barney grub dropped a clanger. And for styling menus go to  Theme Options Header Top of Header Menu Styles of this Row

Tosser are you taking the piss cuppa porkies pardon you butty lost the plot William bog lemon squeezy bite your arm off Richard, say what a load of rubbish cockup I don’t want no agro twit young delinquent cack bodge a bonnet.

Unordered list items

Ordered List Items

Branding

ESC is true white-label. Your customers and your team see your brand, not ours.

What you can set

On the Brand tab:

• Logo – PNG or SVG.
• Favicon – the small icon in the browser tab.
• Primary brand colour – applied across your helpdesk.

Save, and it’s applied to your live helpdesk immediately. No redeploy, no downtime.

Where your branding appears

• Your customer support portal – what your customers see.
• Your agent workspace – what your team sees.
• Your web chat widget – though the chat header logo can be set separately if you want a different one there. See Web Chat Widget.

What we’ve already done for you

Before you ever log in, we run a full brand sweep on your helpdesk: third-party product names and infrastructure menus are removed. What’s left is a clean workspace that looks like part of your own product. You don’t need to hunt for someone else’s logo to replace – it’s already gone.

Tip: use an SVG logo if you have one. It stays crisp at any size, on any screen.

AI Support Agents

Your AI support agents are who your customers appear to be talking to. They answer web chat and email tickets automatically, drawing on your knowledge base, and hand off to your human team when they should.

Creating agents

On the Agents tab:

• Add an agent with a first and last name and a department.
• Upload an avatar photo for each agent. It’s stored with your brand assets and is shown in live chat replies.
• Edit or remove agents at any time. Changes flow to your live helpdesk automatically.

How many agents?

Your plan sets the limit: Starter 2, Growth 8, Pro 16, Enterprise unlimited.

There are no per-agent fees. Your monthly price covers your whole roster.

On upgrading: when you move to a larger plan, your agent roster automatically expands to the new tier’s limit with ready-to-use agents. You don’t have to rebuild it.

Giving them a personality

Names and departments aren’t cosmetic. They’re what your customers see in every reply, so pick names and departments that fit your brand and your team’s structure. An agent named for a real department (“Billing”, “Technical Support”) sets the right expectation for the conversation.

What your AI agents can and can’t do

They answer from your knowledge base. That’s the point – replies are grounded in your own documents and policies, not a generic model’s guesses. If the answer isn’t in your knowledge, they hand off to your human team rather than inventing one.

How confident they must be before answering is something you control. See Knowledge Base.

What is an Extension?

For editing menu navigation settings go to  Theme Options Header Top of Header . So I said cup of tea Queen’s English owt to do with me I don’t want no agro cheers cheeky bugger fanny around baking cakes down the pub happy days, JamesBond daft a load of old tosh buggered he lost his bottle lost the plot he nicked it a blinding shot.

[docly_tooltip id=”1″]Tooltip text[/docly_tooltip] mufty quaint no biggie cras baking cakes barney bamboozled, what a plonker bum bag he legged it young delinquent knees up Eaton the full monty arse over tit, my lady buggered happy days amongst bugger all mate are you taking the piss brolly. [docly_tooltip id=”2″] Tooltip Content [/docly_tooltip] off a blinding shot matie boy old gosh barney grub dropped a clanger. And for styling menus go to  Theme Options Header Top of Header Menu Styles of this Row

Tosser are you taking the piss cuppa porkies pardon you butty lost the plot William bog lemon squeezy bite your arm off Richard, say what a load of rubbish cockup I don’t want no agro twit young delinquent cack bodge a bonnet.

Unordered list items

Ordered List Items

OsTicket Initialization:

Overview:

This guide will walk you through initializing OSTicket on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip> :

• You will be greeted by the welcome screen.

Step 3: Finalizing Installation  

1. Prerequisites

• Click Contine to proceed if all system checks are ticked. If not, contact our support immediately.

2. System Settings:

• Get the database credentials from the summary of initialization script earlier and fill up the database settings, as below.

Table Prefix: ost_ (your preference) 

Hostname: localhost

Database: osticketdb

Username: (the values provided per the output of egl_init.sh.x)

Password: (the values provided per the output of egl_init.sh.x)

• You may fill up all other fields accordingly per your preference or business need.
• Once completed, press ‘Install Now‘.

3. Installation Complete:

• Once the setup is complete, you will see the final “Congratulations” screen.

• Navigate to http://<your-public-ip>/scp/login.php and login with the Administrator credentials you entered in the “Admin User” section earlier.

Step 4: Post Installation – Recommended by OsTicket

1. “Setup” folder removal

Option 1: rename “setup” folder

• Go to your instance SSH command prompt and run the following command at root

Option 2: delete “setup” folder

• Go to your instance SSH command prompt and run the following command at root

Important Notes:

• Mail Sending Blockage:
  AWS may have email-sending restrictions in place by default. Before using the instance for email sending, submit a request to AWS to lift the restriction on outbound email traffic.

Non aptent facere unde placeat habitant minus numquam, cubilia orci accusantium laoreet vel, illum! Mauris placerat. Nibh fuga, luctus dignissim cursus, exercitationem, viverra ratione similique aut, culpa tellus. Turpis fusce, eos cupiditate, turpis? Pede leo repudiandae, praesent laborum dolore eum consequatur provident ullamco praesent, officia! Ipsam nam auctor repudiandae laoreet diamlorem possimus aptent? Mollis iure laudantium ratione malesuada facilis vivamus nec ullamcorper sapiente pharetra nisl tempora cras doloremque, nihil ligula ut reprehenderit? Eiusmod? Egestas fermentum aliqua, occaecat mollis pulvinar sapien! Ab suscipit morbi rhoncus magnam maxime. Officia facilisis, curae odio, rhoncus egestas iure venenatis quidem! Veritatis magnam commodo magnis qui.

Magnam rutrum pretium inventore ridiculus netus. Ducimus cursus facilis eleifend, congue odit venenatis conubia mi provident exercitationem dictumst aenean vel, eleifend mi lacinia porttitor. Incidunt nisl laoreet, suspendisse nam nemo suspendisse luctus, donec parturient necessitatibus itaque tempora beatae eos non ratione ornare consequat consequat cursus hac deleniti esse natus ridiculus. Ultricies alias, cum sociosqu error praesent, nonummy vero optio, aute, nec natoque! Excepteur, saepe, magnam assumenda non cursus, at sociis, nihil ridiculus! Egestas non omnis, gravida nonummy eligendi? Sapien do totam mollis blandit iure, rerum vestibulum hymenaeos explicabo, purus dolore? Habitant consequatur. Curae incididunt sem minim. Explicabo morbi, corporis. Malesuada.

Odoo 18 Initialization:

Overview:

This guide will walk you through initializing Odoo 18 on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

• Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
• Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

• Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
• Run the following SSH command:

• When prompted for the login, enter:
  

3. Run the Initialization Script:

• To initiate the installation, run the following command:

• Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

• Once the installation is finished, you will see a summary on the screen that includes all credentials.

2. Access the Web Interface:

• Open your web browser and navigate to http://<your-public-ip>:8069 (port 8069) :

• You will be greeted by the welcome screen.

3. Login:

• Use the credentials provided during the installation process to log in.

• If login is successful, then you will be able to see the screen below.

4. Disable “Manage Database”:

• Recommended Step: To DISABLE “Manage Databases” link at login page, you will need to add the line below to Odoo configuration file /etc/odoo/odoo.conf

“list_db = False”

• Go to your instance SSH command prompt and run the following command at root

• Then add the line below to the file and save the file.

list_db = False

• Restart odoo and apache to reflect the changes

What is an Extension?

For editing menu navigation settings go to  Theme Options Header Top of Header . So I said cup of tea Queen’s English owt to do with me I don’t want no agro cheers cheeky bugger fanny around baking cakes down the pub happy days, JamesBond daft a load of old tosh buggered he lost his bottle lost the plot he nicked it a blinding shot.

[docly_tooltip id=”1″]Tooltip text[/docly_tooltip] mufty quaint no biggie cras baking cakes barney bamboozled, what a plonker bum bag he legged it young delinquent knees up Eaton the full monty arse over tit, my lady buggered happy days amongst bugger all mate are you taking the piss brolly. [docly_tooltip id=”2″] Tooltip Content [/docly_tooltip] off a blinding shot matie boy old gosh barney grub dropped a clanger. And for styling menus go to  Theme Options Header Top of Header Menu Styles of this Row

Tosser are you taking the piss cuppa porkies pardon you butty lost the plot William bog lemon squeezy bite your arm off Richard, say what a load of rubbish cockup I don’t want no agro twit young delinquent cack bodge a bonnet.

Unordered list items

Ordered List Items

This section provides comprehensive instructions on managing the deployed application/image and its services. It covers essential tasks such as starting and stopping instances, managing key services like Cockpit, PGAdmin4, and SSL, and resolving common issues.

Cockpit (https://cockpit-project.org/) is a web-based graphical interface for servers management and administration. This particular AMI is pre-installed with Cockpit to ease administration. To start using Cockpit, follow the steps below.

• Step 1: Get the Cockpit credentials output from execution of “usr/local/bin/egl_init.sh.x”
• Step 2: Go to http://<your-public-ip>:9090/ and enter the credentials.

• Step 3: You may see “limited access” and may be prompted to authenticate. Click “Turn on administrative access“, key in once again the credential from Step 1.

Uploading File with Cockpit 

• Step 1: Login to Cockpit.
• Step 2: Go to “navigator“.
• Step 3: To upload files to server using Cockpit, simply navigate to your path and just drag-and-drop into the folder.

Associate Your Domain with OrangeHRM

To associate your domain with the application and the AWS IP address, you will need to edit the following files;

File 1: /etc/httpd/sites-available/orangehrm.conf

Log on via SSH,

$ ec2-user

$ sudo -i

$ nano /etc/httpd/sites-available/orangehrm.conf

then modify these lines with your domain. Replace yourdomain.com with your domain name; and RewriteRule http to https

<VirtualHost *:80>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/orangehrm

RewriteEngine on
RewriteCond %{SERVER_NAME} =www.yourdomain.com [OR]
RewriteCond %{SERVER_NAME} =yourdomain.com
RewriteRule ^ http://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

<Directory /var/www/orangehrm>

AllowOverride All
Order allow,deny
allow from all

</Directory>

</VirtualHost>

<VirtualHost *:443>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/orangehrm

RewriteEngine on
RewriteCond %{SERVER_NAME} =www.yourdomain.com [OR]
RewriteCond %{SERVER_NAME} =yourdomain.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

<Directory /var/www/orangehrm>

AllowOverride All
Order allow,deny
allow from all

</Directory>

</VirtualHost>

Associating Your Domain with Mautic 5

Overview:

To successfully associate your domain with the Mautic 5 hosted on an AWS instance, follow the steps outlined below. This process involves editing the Apache configuration file to link your domain with the server’s IP address and enforce HTTPS redirection.

Step 1: Access Your Server

1. Log in via SSH

• Use SSH to access your AWS instance:

2. Switch to the Root User

• Elevate your permissions by switching to the root user:

Step 2: Modify the Apache Configuration File

1. Edit the Configuration File

• Open the Apache configuration file:

2. Update Domain Information

• Replace the placeholder yourdomain.com with your actual domain name in the configuration. Ensure that both the non-www and www versions of your domain are included. Also, modify the RewriteRule directives to enforce HTTPS redirection.

Below is the updated configuration you need to apply:

<VirtualHost *:80>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/mautic
ErrorLog /var/www/mautic/log/error.log
CustomLog /var/www/mautic/log/requests.log combined

<Directory /var/www/mautic>

Options +FollowSymLinks
AllowOverride All
Require all granted

</Directory>

</VirtualHost>

<VirtualHost *:443>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/mautic
ErrorLog /var/www/mautic/log/error.log
CustomLog /var/www/mautic/log/requests.log combined

 <Directory /var/www/mautic>

Options +FollowSymlinks
AllowOverride All
Require all granted

</Directory>

 ## Include SSL settings
## Uncomment the below lines if you have SSL with LetsEncrypt
# Include /etc/letsencrypt/options-ssl-apache.conf
# SSLCertificateFile /etc/letsencrypt/live/yourdomain.com/fullchain.pem
# SSLCertificateKeyFile /etc/letsencrypt/live/yourdomain.com/privkey.pem

</VirtualHost>

3. Save and Exit

• After making the necessary changes, save the file by pressing Ctrl + O, then press Enter to confirm. Exit the editor by pressing Ctrl + X.

Step 3: Refresh Symbolic Links & Restart Apache

• For the changes to take effect, recreate the symbolic links and then restart the Apache web server:

Additional Notes:

• Ensure that you have an SSL certificate installed for HTTPS to work. You may use services such as Let’s Encrypt to obtain a free SSL certificate.
• You might need to adjust firewall rules or security group settings in AWS to allow traffic on ports 80 (HTTP) and 443 (HTTPS).
• Important: Request AWS to lift any email sending restrictions if you’re using the application’s email features.

OVERRIDING PARENT THEME FILES

You can not only target individual style declarations via the style sheet but also override entire components of the parent theme.

For every theme file present in the parent directory, WordPress will check whether a corresponding file is present in the child theme and if so, use that one instead. This means that a header.php file in the child theme will override its equivalent in the parent folder.

So, if you don’t like something about a page’s layout, just copy the respective file, implement your changes, and upload it to the child theme’s folder. The modifications will then appear in the child theme, while the original file will remain untouched.

WORKING WITH TEMPLATE FILES

We’ve learned that we can overwrite any file in the parent theme by placing a copy in the child theme’s folder and customizing it. However, using files that exist only in the child theme is also possible. Template files are a good example of this.

Let’s say we want to build a full-width page template for our child theme. Our theme does not lend itself to the full-screen presentation, but let’s do it anyway for demonstration purposes, shall we?

To create a full-width page in Chaoz you have to create a custom page template. Let’s start with the page template.

For our custom page template, we simply copy page.php from the parent theme, rename it to page-full-width.php and place it in the Child theme’s root folder.

PGAdmin 4 (https://www.pgadmin.org/) is the most popular and feature rich Open Source administration platform for PostgreSQL database. This particular AMI is pre-installed with PGAdmin to ease administration. To initialize PGAdmin 4, follow the steps below.

• Step 1: Login via SSH

$ ec2-user

$ sudo -i

$ sudo /usr/pgadmin4/bin/setup-web.sh

Follow the prompt to enter initial login details;

Your email 

Your password 

Retype password 

Wait for the installation to complete.

Enter Y (yes) to restart Apache.

• Step 2: Go to http://<your-public-ip>/pgadmin4 and enter the credentials from step 1 to login.

This section provides comprehensive instructions on managing the deployed application/image and its services. It covers essential tasks such as starting and stopping instances, managing key services like Cockpit, PGAdmin4, and SSL, and resolving common issues.

Cockpit (https://cockpit-project.org/) is a web-based graphical interface for servers management and administration. This particular AMI is pre-installed with Cockpit to ease administration. To start using Cockpit, follow the steps below.

• Step 1: Get the Cockpit credentials output from execution of “usr/local/bin/egl_init.sh.x”
• Step 2: Go to http://<your-public-ip>:9090/ and enter the credentials.

• Step 3: You may see “limited access” and may be prompted to authenticate. Click “Turn on administrative access“, key in once again the credential from Step 1.

Uploading File with Cockpit 

• Step 1: Login to Cockpit.
• Step 2: Go to “navigator“.
• Step 3: To upload files to server using Cockpit, simply navigate to your path and just drag-and-drop into the folder.

Associate Your Domain with Bagisto

To associate your domain with the application and the AWS IP address, you will need to edit the following files;

File 1: /etc/httpd/sites-available/bagisto.conf

Log on via SSH,

$ ec2-user

$ sudo -i

$ nano /etc/httpd/sites-available/bagisto.conf

then modify these lines with your domain. Replace yourdomain.com with your domain name; and RewriteRule http to https

<VirtualHost *:80>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/bagisto/public

RewriteEngine on
RewriteCond %{SERVER_NAME} =www.yourdomain.com [OR]
RewriteCond %{SERVER_NAME} =yourdomain.com
RewriteRule ^ http://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

<Directory /var/www/bagisto/public>

AllowOverride All
Order allow,deny
allow from all

</Directory>

</VirtualHost>

<VirtualHost *:443>

ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/bagisto

RewriteEngine on
RewriteCond %{SERVER_NAME} =www.yourdomain.com [OR]
RewriteCond %{SERVER_NAME} =yourdomain.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

<Directory /var/www/bagisto/public>

AllowOverride All
Order allow,deny
allow from all

</Directory>

</VirtualHost>

Before You Begin

ESC is fully managed. There is no server for you to launch, access, or maintain – no SSH, no patching, no scaling. Your helpdesk runs on a dedicated instance that we provision and operate for you. That keeps the prerequisites short.

What You Need

An AWS account – ESC is subscribed and billed through AWS Marketplace, so you’ll need an AWS account to subscribe. Nothing is deployed into your account.

A domain and DNS access (optional, but recommended) – If you want your helpdesk on your own address (e.g. support.yourcompany.com), you’ll need a domain you control and the ability to add a DNS record for it. You can start without one and add it later, but a custom domain is what unlocks your branded customer support portal, your branded support email address, and your AI agent’s ability to share contact details with visitors.

A support mailbox (optional) – To turn incoming customer emails into tickets, you’ll need a mailbox with standard incoming and outgoing mail settings. You can add this at any time.

Your knowledge documents (optional at launch, but bring them) – Your AI agents answer from documents you upload. Supported formats are PDF, Word (DOC/DOCX), Excel (XLS/XLSX), PowerPoint (PPTX), TXT, CSV and Markdown, up to 50 MB per file.

Two things that catch people out. Legacy PowerPoint (.ppt) isn’t supported – re-save as .pptx or PDF. And a scanned PDF won’t work: if it’s just page images with no selectable text, there’s nothing for the AI to read. Use a text-based PDF, or convert it first.

Choose Your Region

Your helpdesk runs in the AWS region you select when you launch it. ESC is currently available in:

• Ireland (eu-west-1)
• London (eu-west-2)
• Singapore (ap-southeast-1)
• US East — N. Virginia (us-east-1)

Further regions are in progress.

Choose deliberately. Your region is set when your helpdesk is created and can’t be changed afterwards without rebuilding it. Pick the region closest to your customers, or the one your data-residency requirements point to.

What You Don’t Need

No servers. No infrastructure experience. No developers. No per-agent licences. No third-party helpdesk subscription. Everything your helpdesk needs is included in your plan.

This section provides comprehensive instructions on managing the deployed application/image and its services. It covers essential tasks such as starting and stopping instances, managing key services like Cockpit, PGAdmin4, and SSL, and resolving common issues.

Cockpit (https://cockpit-project.org/) is a web-based graphical interface for servers management and administration. This particular AMI is pre-installed with Cockpit to ease administration. To start using Cockpit, follow the steps below.

• Step 1: Get the Cockpit credentials output from execution of “usr/local/bin/egl_init.sh.x”
• Step 2: Go to http://<your-public-ip>:9090/ and enter the credentials.

• Step 3: You may see “limited access” and may be prompted to authenticate. Click “Turn on administrative access“, key in once again the credential from Step 1.

Uploading File with Cockpit 

• Step 1: Login to Cockpit.
• Step 2: Go to “navigator“.
• Step 3: To upload files to server using Cockpit, simply navigate to your path and just drag-and-drop into the folder.

Associating Your Domain with Matomo 5

Overview:

To successfully associate your domain with the Matomo 5 hosted on an AWS instance, follow the steps outlined below. This process involves editing the Apache configuration file to link your domain with the server’s IP address and enforce HTTPS redirection.

Step 1: Access Your Server

1. Log in via SSH

• Use SSH to access your AWS instance:

2. Switch to the Root User

• Elevate your permissions by switching to the root user:

Step 2: Modify the Apache Configuration File

1. Edit the Configuration File

• Open the Apache configuration file:

2. Update Domain Information

• Replace the placeholder yourdomain.com with your actual domain name in the configuration. Ensure that both the non-www and www versions of your domain are included. Also, modify the RewriteRule directives to enforce HTTPS redirection.

Below is the updated configuration you need to apply:

<VirtualHost *:80>
ServerName yourdomain.com
ServerAlias www.yourdomain.com
DocumentRoot /var/www/matomo
ErrorLog /var/www/log/error.log
CustomLog /var/www/log/requests.log combined