Budget-friendly, full-performance, fully equipped servers in any desired location.
ExploreBudget-friendly, full-performance, fully equipped servers in any desired location.
ExploreTo publish a new domain through the Plesk panel, first add the domain to the correct subscription, then point its DNS record to the server address and upload the site files to the relevant document root. If the domain opens but the site is not visible, check the DNS result and file location separately; proceed by changing one variable at a time instead of changing every setting at once.
This process is suitable for a Plesk administrator or a user who has permission to add domains under the relevant subscription. On a shared hosting account, you will see only the options available within your own subscription; on a managed server, some settings, such as DNS, the web server and the PHP version, may be restricted by the provider. First verify your Plesk login details, DNS management at the domain registrar, and the ready version of the files to be published.
Also determine in advance which server the domain should reach. For the main domain, an A record generally points to the server’s IPv4 address; if IPv6 is used, the appropriate AAAA record points to the relevant IPv6 address. The CNAME or A record used for the “www” subdomain should be checked separately. It is normal for DNS changes to appear at different times on different networks; therefore, adding a domain in Plesk does not mean that DNS has been updated everywhere immediately.
After saving, check whether the domain appears active in Plesk and is listed under the correct subscription. If the domain is not in the list, assume that the adding process was not completed before moving on to DNS. If the domain is listed but the browser shows a default page or a “site not found” warning, the next areas to inspect are DNS routing and the document root; uploading files at random will not help separate the problem.
In the DNS screen at the domain registrar, check that the A or AAAA record for the root domain points to the expected server address and that the “www” record matches the configuration you are using. If a DNS query does not show the server address, do not change the files in Plesk; first correct the wrong or outdated record at the registrar. If the query shows the correct address but the page still does not open, check whether the domain is defined in the Plesk subscription and whether the web service is active.
For example, suppose ornekalanadi.com has been added to Plesk and the files have been uploaded to the document root, but the domain still shows the IP address of the previous hosting provider. This observation does not prove that the file upload failed. The correct step is to point the A record in DNS to the new server address first, then open the same domain again. If the DNS query shows the new address but the Plesk default page appears, investigate whether the files were uploaded to another folder or whether the start file is missing.
Use the file manager for the relevant domain in Plesk or the configured FTP access to upload files only to that domain’s document root. Check that your home page exists under the name expected by your application, such as index.php or index.html; if the software uses a different entry file, follow its own installation instructions. If the files are visible but the application reports an error, do not simply repeat the upload; distinguish the PHP version, application configuration and new entry in the error log from one another.
The concrete decision here depends on the type of observation: if there is no file in the Plesk file manager, the target folder or upload process is wrong; if the file exists and a simple HTML page opens, DNS and basic web serving are working, so the problem should be sought at the application layer. If you see a write-permission error in the log, correct the expected ownership and permissions only for the relevant application folder according to the provider’s documentation; do not grant broad permissions to the entire site or disable security controls.
Before making a change, note the DNS record, previous document root and SSL setting; if possible, take a backup of the site files. Change only one factor in each attempt. If the symptom does not improve, undo the last change and temporarily test the domain with a basic static start page; this is a safe way to separate the issue. If the static page works, return to the application configuration; if it does not, return to the DNS or Plesk domain match. As the next step, you can review the environment options on your provider’s Turkey VDS server plans page; however, do not change plans until you are sure that the current finding genuinely indicates a resource or permission limit.
Copyright © 2026 All Rights Reserved
