Hi jwvdmei,
There is no "apache2" directory in the "etc" directory.
well, "
bad luck" for you, I would say. ( sorry to be ironic!
) As a system - administrator, you should know, that Plesk
supports MULTIPLE operating systems and due to the case, that you didn't include YOUR used operating system, when asking for help, you might get paths as answers for a different OS.
( hint: the equivalent path for "apache2" ( Debian/Ubuntu - based operating systems ) is "httpd" on CentOS/RHEL - based operating systems, which you should know, as you already provided informations for the path of "welcome.conf" ! )
You might remember the ( basic ) essential informations, when you aks again for help.
This was the path to the welcome.conf file: /etc/httpd/conf.d/welcome.conf
This configuration file is not needed. Consider to rename it with the command:
Code:
mv /etc/httpd/conf.d/welcome.conf /etc/httpd/conf.d/welcome.conf.backup
( Note: ONLY files with the ending *.conf will be loaded by apache )
When you renamed that file, you might experience, that in some cases the content from "
/var/www/html/" is loaded ( which are the standard files, when no vhosts are configured on your server ). This depends on your
very own ( standard ) configuration defined at "
/etc/httpd/sites-enabled" ( existent files are symlinks to configuration files at "/etc/
httpd/
sites-available" ). Examples may be named as "default.conf", or "default-ssl.conf". Consider to REMOVE such symlinks at "
/etc/httpd/sites-enabled" to deny displaying such default - sites!
On the other hand, pls. consider to READ the file "
/etc/httpd/conf/httpd.conf", to investigate, which folders / files might be included in your apache - configuration!
...but missing theme and styles etc.
Some CMS, blog - software, forum - software, content of your domain may use "
.htaccess" - files, which
NGINX can't read. Most software provider include documentations / instructions, what you have to use as "
NGINX directives", when you use NGINX on your server. These "
NGINX directives" can be added over Plesk at for example: "
Home > Subscriptions > YOUR-DOMAIN.COM > Apache & nginx Settings" ( textbox for:
Additional nginx directives ).
Plesk offers as well a wonderfull tool called "
htaccess to nginx" - converter. You find this ( free ) Plesk - extension at the "
Extension catalog" ( "
Home > Extensions > Extensions Catalog" ), or at
=> htaccess to nginx over ext.plesk.com
Sometimes
( when you use wordpress for example and no additional plugins / themes, which might need additional NGINX directives ), it helps just to add standards as:
Code:
try_files $uri $uri/ /index.php?$args;
OR when you use PHP-FPM as PHP - handler on your (sub)domain:
Code:
if (!-e $request_filename){
rewrite ^(.*)$ /index.php break;
}
In your case, you use "
wordpress" and additional wordpress - plugins / themes. Pls. be informed about the following documentation:
Each wordpress
plugin /
theme might as well need additional NGINX rewrites, when you use NGINX. Pls. read THEIR documentation(s) and installation instructions and ask for support directly there, where you got the plugin / theme from.
Should I continue on to the “Plesk repair utility”?
Well, it wouldn't harm your system, when you use these repair options. You know now how to use them and know where the corresponding documentation is located.
Facebook
Twitter
