For your security, Email Two-Factor Authentication (2FA) is now required. The first time you log in, you’ll need to set up 2FA to protect your account. This process only takes a minute and ensures that your account stays safe from unauthorised access.
Follow the steps below to complete your 2FA setup quickly and easily. Once done, you’ll enjoy a more secure and protected login experience every time.
Step 1: Login to your account, you will be taken to the Security page
Step 2: “Click Here to Enable” will take you to setup then click “Get Started”
Step 3: Check your email for the code and enter it here, press “Active Now”
Step 4: Your setup is now complete. Save your backup code.
Step 5: You can now use the Client Area and all features are enabled.
Congratulations! Your Account is Now More Secure!
By setting up Email Two-Factor Authentication (2FA), you have added an extra layer of security to your account. This means that even if someone ever gets hold of your password, they will not be able to access your account without the unique 2FA code sent to your email.
What This Means for You:
Your account is now much harder to hack.
You have better protection against phishing and unauthorised access.
Every login attempt now requires both your password and a unique security code, making it twice as secure.
What’s Next?
Always keep your email secure and never share your 2FA codes with anyone.
If you ever change your email address, update it with us to avoid login issues.
Want even stronger security? You can also explore Google Authenticator 2FA for even faster logins in the future.
If you have any questions or ever need help, our support team is always here for you.
Two-Factor Authentication (2FA) adds an extra layer of security to your account. Instead of just a password, you also need a one-time security code to log in.
Why Do I Need 2FA?
Passwords alone can be stolen or guessed. 2FA makes it much harder for hackers to access your account, even if they know your password.
How to Set Up Email 2FA (First-Time Login)
Since this is your first time logging in, you will be asked to set up Email 2FA.
Log in to your account using your email and password.
You will be redirected to the Security Settings page.
Click Enable Two-Factor Authentication.
A 6-digit code will be sent to your registered email.
Enter the code to confirm your 2FA setup.
Done! Your account is now protected.
How to Use Email 2FA (Ongoing Logins)
Every time you log in, you will:
Enter your email and password as usual.
Check your email for a 6-digit 2FA code.
Enter the code on the login page.
Access granted!
⚠️ Tip: If you don’t see the email, check your Spam/Junk folder.
Need Help?
❓ Q1: “I Didn’t Receive the 2FA Code in My Email. What Should I Do?”
A: If your 2FA email hasn’t arrived, try these steps:
✅ Check your Spam/Junk folder.
✅ Wait a few minutes, then request a new code.
✅ Ensure your email account is working properly and not full.
✅ If you still don’t receive it, contact support to verify your email address.
❓ Q2: “My Google Authenticator App is Not Working. How Can I Fix It?”
A: If your Google Authenticator codes are incorrect or not appearing, try:
✅ Sync your phone’s time (Settings → Date & Time → Enable “Automatic Time”).
✅ If the app was deleted, reinstall it and restore from your backup code.
✅ If you lost access completely, contact support to reset your 2FA settings.
❓ Q3: “I Lost My Phone and Can’t Access My 2FA. What Now?”
A: If your phone is lost or broken:
✅ Use your backup codes (provided when setting up 2FA).
✅ If Email 2FA is enabled, request a new login code via email.
✅ If you have no access at all, contact support for verification and reset.
❓ Q4: “Why is My 2FA Code Incorrect?”
A: If your 2FA code isn’t working:
✅ Enter a new code quickly before it expires.
✅ Sync your phone’s time and date settings.
✅ Double-check that you are using the correct 2FA method (Google Authenticator vs. Email 2FA).
✅ If the issue continues, reset 2FA and set it up again.
❓ Q5: “I Enabled 2FA but Now I Can’t Log In at All!”
A: If you’re completely locked out:
✅ Use the password reset option to regain access.
✅ If you set up Email 2FA, request a new code via email.
✅ If all else fails, contact support to reset your 2FA after verifying your identity.
🔒 Final Tip: Always Keep a Backup!
To avoid future issues:
✅ Save your backup codes when setting up 2FA.
✅ Use a password manager to securely store credentials.
✅ Enable Email 2FA as a fallback in case you lose access to Google Authenticator.
🚀 2FA adds an extra layer of security, and with these solutions, you’ll always have access to your account! 🔐😊
Still Need Help?
If you have any issues logging in, contact our support team.
Installing WordPress on your UK Cheapest Plesk Obsidian server is incredibly easy, even if you’re new to web hosting. With Plesk’s user-friendly interface, you can set up WordPress in just a few clicks. Follow this guide to get your WordPress site up and running!
Step 1: Log In to Your Plesk Control Panel
Start by logging into your Plesk Obsidian control panel. You’ll find the login details in the welcome email from UK Cheapest, or you can log in at:
URL:https://your-domain.com:8443
Enter your username and password to access the dashboard.
Step 2: Go to the WordPress Toolkit
Once inside the Plesk dashboard, find the WordPress Toolkit on the left-hand menu. The WordPress Toolkit makes it simple to install, manage, and update your WordPress sites.
If you don’t see the WordPress Toolkit, navigate to Extensions in the menu and install the WordPress Toolkit extension for free.
Step 3: Install WordPress
With the WordPress Toolkit open, follow these steps to install WordPress:
Click on Install WordPress in the top right corner.
Select your domain or subdomain from the dropdown where you want to install WordPress.
Choose installation path (leave blank if you want WordPress to be installed in the root directory of your domain).
Under Installation Settings, enter your site title, admin username, password, and email. These will be used to log in to your WordPress dashboard.
For security, make sure Enable HTTPS is checked if you have an SSL certificate installed. This will ensure that your site uses HTTPS.
Click Install.
The installation process will begin, and within a few moments, your WordPress site will be ready!
Step 4: Access Your WordPress Admin Dashboard
Once WordPress is installed, you can access your WordPress admin dashboard:
In the Plesk dashboard, navigate to the WordPress Toolkit.
Under the list of installed WordPress sites, find your domain.
Click on the Log in to Admin Dashboard button. This will take you directly to the WordPress admin panel.
You can also access your dashboard by going to https://your-domain.com/wp-admin and entering your WordPress admin username and password.
Step 5: Customise Your WordPress Site
Now that you’re inside the WordPress dashboard, you can start customising your site:
Choose a theme by going to Appearance > Themes.
Install plugins by navigating to Plugins > Add New.
Create pages and posts from the Pages and Posts sections.
WordPress gives you complete control over your site, and with Plesk’s toolkit, managing updates, plugins, and security is easy.
Step 6: Enable Automatic Updates (Optional)
To keep your site secure and up to date, you can enable automatic updates for WordPress core, themes, and plugins:
In the Plesk WordPress Toolkit, find your site and click Manage.
Under Updates, enable automatic updates for WordPress core, plugins, and themes if desired.
Step 7: Install SSL (Optional but Recommended)
If you haven’t already enabled SSL during the WordPress installation, you can do so now to secure your site with HTTPS:
Go to Websites & Domains in the Plesk dashboard.
Click on SSL/TLS Certificates under your domain.
Select Let’s Encrypt to issue a free SSL certificate for your site.
Once installed, Plesk will automatically configure your site to use HTTPS.
Congratulations! Your WordPress Site is Ready
That’s it! You’ve successfully installed WordPress on Plesk Obsidian. From here, you can start customising your site, installing plugins, and adding content. Thanks to Plesk’s easy-to-use interface, managing your WordPress site will be smooth and efficient.
Need further help? Don’t hesitate to reach out to our support team for assistance!
This Plesk Obisidian issue was initially handled by Plesk Support, but the solution wasn’t ideal, as it applied changes to all configuration files, including those that didn’t require it. This resulted in duplicated options being added to the files.
Symptoms
Log rotation doesn’t rotate logs, resulting in no compressed .gz files being created.
Forcing log rotation for a specific domain results in the following error:
/usr/local/psa/logrotate/sbin/logrotate -v -f /usr/local/psa/etc/logrotate.d/example.com
(...)
considering log /var/www/vhosts/system/example.com/logs/access_log.processed log
/var/www/vhosts/system/example.com/logs/access_log.processed has multiple (2) hard links.
Rotation of files with multiple hard links is not allowed for
/var/www/vhosts/system/example.com/logs/*.processed -- skipping.
(...)
Cause
This issue is due to product bugs, resolved in the following updates:
#PPPM-13562: “Fixed the issue where log rotation failed for files with two or more hard links.” Fixed in: Plesk Obsidian 18.0.60 (02 April 2024)
#PPPM-13473: “Log rotation now works correctly after updating to Plesk Obsidian 18.0.42.” Fixed in: Plesk Obsidian 18.0.43 (12 April 2022)
#PPPM-13519: “Log rotation now works correctly after updating to Plesk Obsidian 18.0.43 even if /usr/local/psa/etc/logrotate.conf was customized.” Fixed in: Plesk Obsidian 18.0.44 (24 May 2022)
Resolution
It is recommended to update your server to the latest Plesk version. For guidance, see: How to install Plesk updates.
Workaround
If updating is not possible, you can try adding the allowhardlink directive in the log rotation configuration files as a workaround.
Workaround: Adding the “allowhardlink” Directive to Log Rotation Files
If updating is not an option, you can manually add the allowhardlink directive to log rotation configuration files as a workaround. Follow these steps:
1. Create a Backup (Optional but Recommended)
Before making any changes, it’s recommended to back up the existing configuration files. Run the following command:
You can create a script that checks if the allowhardlink directive is missing in each log configuration file, and add it only if necessary.
Open your terminal and create the script:
nano /root/add_allowhardlink.sh
Paste the following script into the file:
#!/bin/bash
# Directory containing the logrotate configuration files
LOGROTATE_DIR="/usr/local/psa/etc/logrotate.d/"
# Loop through each configuration file in the directory
for config_file in "$LOGROTATE_DIR"/*; do
# Check if the file contains "allowhardlink"
if ! grep -q "allowhardlink" "$config_file"; then
# If not, append "allowhardlink" after "copytruncate"
sed -i '/copytruncate/a allowhardlink' "$config_file"
echo "Added 'allowhardlink' to $config_file"
else
echo "'allowhardlink' already exists in $config_file"
fi
done
Save and exit the file by pressing CTRL + X, then Y, and Enter.
Make the script executable by running:
chmod +x /root/add_allowhardlink.sh
Run the script to apply the changes:
/root/add_allowhardlink.sh
3. Verify the Changes
Once the script has run, you can manually check some configuration files to ensure the allowhardlink directive has been correctly added. Run the following command to check a specific file:
The Mail Autodiscover feature in Plesk Obsidian for Linux is designed to simplify the process of configuring mail clients, such as Outlook, Thunderbird, and mobile devices. It automatically detects and configures the email server settings (IMAP, POP, SMTP) for a domain’s mail accounts, reducing manual input.
Key Points about the Mail Autodiscover Feature
1. Purpose of Autodiscover
The autodiscover feature helps end-users by automatically setting up their mail clients without the need to manually enter server settings (such as the IMAP/POP and SMTP server names, ports, and security settings). It simplifies email account configuration by automatically supplying the correct mail server details based on the user’s email address.
2. How Autodiscover Works
When a user adds their email account to a mail client, the client sends an Autodiscover request (usually to autodiscover.domain.com or domain.com/autodiscover/autodiscover.xml) to fetch the server configuration. The mail client receives the necessary settings, such as:
Incoming mail server (IMAP or POP).
Outgoing mail server (SMTP).
Port numbers and security settings (SSL/TLS).
Username and other optional settings.
3. Autodiscover for Domains in Plesk
In Plesk, Autodiscover is enabled by default for email services and can be managed per domain. Plesk creates DNS records for autodiscover.yourdomain.com and related services during domain setup to enable mail autodiscovery.
4. Protocols Supported by Plesk Autodiscover
IMAP, POP3, and SMTP server settings are supplied by the Autodiscover feature. It also supports SSL/TLS settings for secure mail communication.
5. DNS and SRV Records for Autodiscover
To ensure that Autodiscover works properly, Plesk creates DNS SRV records for the domain’s mail service. These records point mail clients to the correct servers for IMAP/POP and SMTP. The typical DNS SRV records created for Autodiscover are:
_autodiscover._tcp.yourdomain.com
_imaps._tcp.yourdomain.com
_pop3s._tcp.yourdomain.com
_smtps._tcp.yourdomain.com
6. Supported Mail Clients
Autodiscover works with various popular mail clients that support this feature, such as:
Microsoft Outlook (for automatic email account setup).
Mozilla Thunderbird.
Apple Mail.
Mobile devices like Android and iOS.
7. SSL/TLS and Autodiscover
Plesk ensures that mail autodiscovery can work over secure connections. When properly configured, clients will receive SSL/TLS settings, ensuring that the email communication is encrypted.
8. Customising Autodiscover
If you need to adjust or customise the Autodiscover behavior in Plesk (for instance, for a different domain setup or custom mail server), you can modify the DNS SRV records or Autodiscover configuration.
9. Troubleshooting Autodiscover
If Autodiscover is not working correctly:
Verify that the correct DNS SRV records are in place.
Ensure that your mail server’s SSL certificates are correctly configured.
Check your firewall settings to make sure the mail ports (IMAP/POP and SMTP) are open.
Test using the Microsoft Remote Connectivity Analyser to see if Autodiscover is working for your domain.
10. Enabling/Disabling Autodiscover
In some cases, you may want to disable Autodiscover for specific domains. You can do this by removing or adjusting the DNS records in the Plesk DNS settings.
Example of an Autodiscover SRV Record in Plesk
Here is an example of how an SRV record for autodiscovery might look in Plesk:
Service
Protocol
Priority
Weight
Port
Target
_autodiscover
_tcp
0
0
443
autodiscover.yourdomain.com
_imaps
_tcp
0
0
993
mail.yourdomain.com
_smtps
_tcp
0
0
465
mail.yourdomain.com
How to Enable/Manage Autodiscover in Plesk
1. DNS Setup
Go to Domains > DNS Settings and ensure that the correct SRV and A records for Autodiscover are present.
2. Mail Server Settings
Ensure your mail server (Postfix/Dovecot) is correctly configured to support Autodiscover. You can check mail server settings in Tools & Settings > Mail Server Settings.
3. SSL Configuration
Ensure that SSL certificates for the mail server and Autodiscover domain are valid and properly set up.
Conclusion
The Mail Autodiscover feature in Plesk Obsidian for Linux simplifies the setup of email accounts by automatically detecting mail server settings and configuring mail clients accordingly. It works with popular clients like Outlook and Thunderbird and relies on DNS SRV records and proper mail server configurations. To ensure it works, ensure correct DNS, mail server, and SSL setups.