• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Apache - error

404 error is not for "domain not found", but "resource not found" (e.g. a page, a file).

To catch all non-existent subdomains, create a subdomain with the wildard * character, for example *.mydomain.ru. Then place content into its home directory that returns the desired action, e.g. a PHP script that returns a 404 error code. Maybe you can simply choose to redirect the wildcard subdomain to an existing domain.

The question is a different topic. Maybe you can choose to create a separate thread for future add-on questions that have different topics.
The above problem occurred precisely because non-existent subdomains are sent to Plesk in a folder var/www/vhosts/default/htdocs
I deleted it and after a few days (not immediately for some reason) the server stopped working.
I believe that by default, something that does not exist should not work, and in the settings of Plesk for some reason, the reverse is done
 
That is the default behavior of the Apache web server: When a virtual host entry for a non-existing domain cannot be found, the server uses the main (server) domain to answer a request. The document root for that is /var/www/vhosts/default/htdocs. Removing that folder is definitely wrong, because then the server will complain that it is missing its document root directory and it will not be able to respond to many requests properly.
 
That is the default behavior of the Apache web server: When a virtual host entry for a non-existing domain cannot be found, the server uses the main (server) domain to answer a request. The document root for that is /var/www/vhosts/default/htdocs. Removing that folder is definitely wrong, because then the server will complain that it is missing its document root directory and it will not be able to respond to many requests properly.
But when, when accessing any non-existing (arbitrary character set) subdomain, the code 200 is returned - this subdomain falls into the database of the search engines as existing. This is fundamentally not true.
 
I have encountered exactly the same problem. I'd like to ask which configuration file should I change. Since almost all the files have an annotation that the file is auto-generated.
I have Plesk installed on Debian so my directories differs from the ones presented here: Apache and Nginx Configuration Files
I found out that they are in /etc/apache2/ instead.
I found an annotation in one of the files that I should use: /var/www/vhosts/system/[DOMAIN_NAME]/conf/vhost.conf
But I need to set up the global config to use it with all the domains and subdomains, which doesn't have a site attached yet.

Can you provide me the valid config location?
 
Back
Top