Managing hosting settings in Plesk helps you control how a domain or website works without touching the server directly. From the same panel, you can adjust document roots, hosting type, PHP version, SSL options, subdomains, redirects, and limits that affect performance and security. For website owners and hosting users in Europe, this is often the fastest way to keep a site online, compliant with daily operational needs, and aligned with the platform configuration set by your hosting provider.
What hosting settings in Plesk control
In Plesk, the hosting settings define how a domain is served on the web server and which resources it can use. These settings are especially important when you are working with a shared hosting plan, a managed hosting environment, or a platform where several websites are hosted under the same control panel.
Typical hosting settings in Plesk include:
- Hosting type for the domain, such as website hosting, forwarding, or no hosting.
- Document root, which is the folder where your website files are stored.
- PHP settings, including version, handler, and performance options.
- SSL/TLS support and HTTPS-related options.
- Hosting IP address, if the subscription uses a specific IP.
- Mail-related options in some hosting configurations.
- Web statistics and logging settings.
- Subdomain and alias behavior, depending on the subscription permissions.
Understanding these options is useful when you need to point a domain to a new site, troubleshoot a website issue, or adjust the environment for WordPress, Magento, Laravel, or another application running on Plesk.
Where to find hosting settings in Plesk
The exact navigation may vary slightly depending on the Plesk version and the permissions of your subscription, but the general path is similar.
Common navigation path
- Log in to Plesk.
- Go to Websites & Domains.
- Select the domain you want to manage.
- Open Hosting Settings or Apache & nginx Settings if you need web server behavior.
If you are on a managed hosting plan, some options may be locked by the provider. This is normal and helps keep the platform stable across the hosting environment.
How to change the hosting type
The hosting type tells Plesk whether the domain should serve a website, redirect visitors elsewhere, or remain inactive.
Available hosting type options
- Website hosting – the domain serves content from the server.
- Forwarding – visitors are redirected to another URL.
- No hosting – the domain exists in DNS or as a record, but no website is hosted.
Steps to update hosting type
- Open the domain in Websites & Domains.
- Click Hosting Settings.
- Find the Hosting type section.
- Select the required option.
- Save the changes.
If you switch from forwarding to website hosting, make sure the correct files are uploaded to the web root. If you switch to forwarding, confirm that your redirect target uses the correct protocol, especially if you want to preserve HTTPS.
How to change the document root
The document root is the folder where the web server looks for your website files. In many Plesk installations, this is a folder like httpdocs, but it can be changed depending on your application structure.
When you may need to change it
- You moved the site to a different folder structure.
- You are hosting a framework-based application with a custom public directory.
- You want a subdomain to point to a different folder.
- You are separating a staging site from the live site.
Steps to update the document root
- Open the domain in Plesk.
- Click Hosting Settings.
- Locate the Document root field.
- Enter the folder name or path allowed by your subscription.
- Save your changes.
After changing the document root, verify that the correct index file is present in the new directory. If the site uses PHP frameworks, confirm that routing and permissions still work as expected.
How to manage PHP settings for a domain
PHP configuration is one of the most common hosting adjustments in Plesk. Different web applications require different PHP versions or limits, and the right configuration can significantly improve compatibility and performance.
Important PHP options
- PHP version – choose the version required by your application.
- PHP handler – determines how PHP runs on the server.
- memory_limit – controls available memory for scripts.
- upload_max_filesize – limits file uploads.
- post_max_size – limits POST request size.
- max_execution_time – controls how long a script can run.
- display_errors – useful for debugging, but usually disabled on live sites.
How to adjust PHP settings
- Open the domain in Websites & Domains.
- Select PHP Settings if available, or open the hosting settings page.
- Choose the required PHP version.
- Adjust values such as memory, upload size, and execution time.
- Save the configuration.
For production websites, use settings that support stability rather than simply increasing all limits. For example, a higher memory limit may help a CMS during updates, but excessively high values can hide problems or reduce server efficiency in a shared hosting environment.
How to enable or manage SSL/TLS
SSL/TLS is essential for secure web hosting. In Plesk, you can usually enable HTTPS support and install a certificate for the domain. This protects logins, checkout pages, and contact forms, and it also improves trust and search engine compatibility.
Typical SSL-related tasks in Plesk
- Enable SSL/TLS support for the domain.
- Install a certificate.
- Assign a certificate to the website.
- Redirect HTTP traffic to HTTPS.
- Check certificate expiration.
Practical steps
- Open the domain settings in Plesk.
- Go to the SSL/TLS or hosting section.
- Upload or request a certificate if needed.
- Assign the certificate to the domain.
- Enable HTTPS redirect if the site should always use secure connections.
If you use Let’s Encrypt or another automated certificate provider, make sure the domain resolves correctly and that validation can reach the site. On managed hosting platforms, certificate management may be partially automated, but it is still good practice to check renewal status regularly.
How to configure Apache and nginx-related options
Depending on your hosting plan, Plesk may expose settings that influence how Apache and nginx handle the website. These options are useful when you need better caching, custom directives, or a specific way to serve static content.
Common options
- Additional Apache directives.
- Additional nginx directives.
- Serving static files through nginx.
- Proxy mode settings.
- Custom error handling in web server configuration.
When to use them
- You need to set redirects or rewrite rules.
- You want to optimize static file delivery.
- You are following application-specific installation instructions.
- You need to add headers or security rules.
Use these settings carefully. Incorrect directives can break the site or cause 500 errors. If you are unsure, test changes on a staging subdomain before applying them to the live domain.
How to manage subdomains and aliases
Subdomains and domain aliases are part of the same domain management workflow in Plesk. They are often used for separate site sections, application environments, or alternative hostnames.
Subdomains
A subdomain such as blog.example.com or shop.example.com can point to its own document root and have separate hosting settings. This is useful when different parts of your site run on different software or require different PHP settings.
Domain aliases
Aliases allow additional domain names to point to the same website. They are commonly used when you want both example.com and example.eu to open the same content, or when you need a secondary brand name to reach the main site.
Things to check before creating a subdomain or alias
- DNS records are pointing to the correct hosting IP.
- The document root is correct.
- SSL certificate coverage is appropriate.
- Application configuration allows the new hostname.
How to set redirects in Plesk
Redirects are commonly used when moving a site, changing domain names, or consolidating pages. In hosting environments, redirects help preserve traffic and reduce broken links.
Typical redirect scenarios
- Redirect http to https.
- Redirect a non-www domain to www, or the reverse.
- Forward an old domain to a new one.
- Send a temporary maintenance redirect.
Best practices
- Use permanent redirects only when the destination is final.
- Keep redirect chains as short as possible.
- Test both HTTP and HTTPS versions after changing settings.
- Update internal links when moving content.
If you are using forwarding instead of a standard website, confirm whether query strings should be preserved. This can matter for campaign links, tracking parameters, and application login URLs.
How hosting settings affect performance and security
Small changes in hosting settings can have a noticeable impact on how your website performs and how secure it is. That is why managed hosting providers often recommend a standard configuration unless there is a clear reason to change it.
Performance considerations
- Choose the correct PHP version for your application.
- Keep file permissions clean and minimal.
- Use nginx for static file delivery where available.
- Avoid unnecessary redirects or rewrite loops.
- Set realistic PHP limits for your workload.
Security considerations
- Enable SSL/TLS for every public website.
- Disable debugging output on live sites.
- Use separate subdomains for staging when possible.
- Review access to hosting settings if multiple users manage the account.
- Keep applications and plugins updated.
For European websites, it is also sensible to keep hosting configurations clean and documented, especially when different users or agencies manage the same panel over time.
Typical problems when changing hosting settings
Website shows a default page
This usually means the document root is wrong or the expected index file is missing. Check whether the site files are in the folder specified by the hosting settings.
Changes do not appear immediately
Browser cache, DNS propagation, and application caching can delay visible updates. Clear caches and confirm that the domain points to the current server or subscription.
PHP errors after switching version
Some applications are not compatible with older or newer PHP versions. Revert to a compatible version and review plugin or framework requirements.
SSL warning remains active
Make sure the certificate is assigned to the correct domain, the full chain is installed, and the website is forcing HTTPS consistently.
Access denied or permission errors
This can happen after changing the document root or moving files. Verify ownership, permissions, and the path structure used by the hosting subscription.
Best practices for managing domains and websites in Plesk
- Change one setting at a time and test the result.
- Keep a record of the original configuration before making edits.
- Use staging environments for major website changes.
- Review DNS, hosting, and application settings together.
- Prefer provider-recommended defaults unless your application needs custom values.
If your hosting plan includes managed support, share the exact domain name, current configuration, and the change you want to make. This helps support teams resolve issues faster and avoid unnecessary downtime.
Frequently asked questions
Can I manage hosting settings for each domain separately in Plesk?
Yes. Each domain usually has its own hosting settings, including document root, PHP configuration, SSL options, and redirect behavior, depending on your subscription permissions.
Why is the hosting settings page missing some options?
Some features may be disabled by the hosting provider, limited by the subscription, or unavailable because of the selected hosting type. In managed hosting, this is common for security and stability reasons.
What should I check first if my site stops working after a change?
Start with the document root, PHP version, and recent web server directives. These are the most common causes of website issues after changing hosting settings in Plesk.
Can I point a subdomain to a different folder?
Yes. Subdomains in Plesk can usually use a separate document root, which makes them suitable for blogs, test sites, or application areas with different structures.
Should I use forwarding or website hosting for a moved domain?
If the domain should only send visitors elsewhere, use forwarding. If the domain must serve its own content on the server, use website hosting. Choose based on the actual use case.
Do hosting settings affect email?
They can, depending on how the subscription is configured. In many cases, mail service is managed separately, but some domain settings influence whether mail is available for that domain.
Conclusion
Managing hosting settings in Plesk gives you direct control over how a domain behaves without needing shell access or server-level changes. By understanding the hosting type, document root, PHP version, SSL configuration, and web server options, you can keep websites stable, secure, and properly configured for the application in use. In a European hosting environment, this is especially helpful when you need reliable day-to-day control over multiple domains, subdomains, and site updates from one panel.
When in doubt, make small changes, test carefully, and verify both the hosting and application layers after every update. This approach reduces downtime and helps you use Plesk as an efficient control panel for domain and website management.