Plesk 12.x / Linux :: Nginx Does Not Recognize Changes (Document Root)
Nov 12, 2014
There is a bug in the current Plesk version 12, which was encountered on many of our Plesk 12 server until now. I do have Plesk 12.0.18 Update #23 with CentOS 6.
When a customer changes for example the document root of a domain nginx does not recognize it and the administrator of the server do have to restart nginx manually.
This issue is serious because CSS, JS and images are not working on such a page where a customer changed the document root. Nginx is throwing 404 error until nginx is restarted manually.
Other customers do have the same issue: [URL] .....
i am relatively new to Plesk, i ordered a vserver with Plesk a couple of months ago and spend a lot of time setting everything up and developing several new websites. I am used to developping new websites on a hidden adress (sth like domain.com/dev/ instead of the top level) and then switch the document root to point to the hidden directory when all is done. This practice has served me and my clients well for the last 10 years.
Using the Plesk features like built-in applications seemed like a good idea at the time but wanting to switch the new websites live i have now found out that Plesk won't let me do this since..It is impossible to change document root because there are web applications installed on this website.
I had read somewhere on the interweb that the v12 would let me do this so i just spent the better part of today updating to v12 .. but alas no luck, the limitation is still there. Is there a way to remove this limitation ?
Basic question: does it matter where I set the document root for apache on a Linux system? I've googled this but haven't found a good answer.
This is for a VPS server running the Ubuntu (Debian) server os that I'm configuring. I'd prefer to simply create a new directory off the root and set that as the document root in the apache config file. Would this present any kind of security issue?
If that's no good, what's the best choice -- stick to the default?
I bought a new plesk and created new domains. For some odd reason, all the domains are looking at the default document root.
/var/www/vhosts/default/htdocs/ Rather than going to the domains document root /var/www/vhosts/domain.com/conf
I checked the /var/www/vhosts/domain.com/conf/httpd.include, the document root and all are fine.
I also tried creating vhost.conf and assigning the document root there. /usr/local/psa/admin/sbin/websrvmng --reconfigure-vhost --vhost-name=domain.com -v
I installed a centos4.7 with ISPCONFIG2 control panel, but any account I create it points to the documentroot of apache.
I am running my server behind a router.
On the /etc/httpd/conf/vhosts/Vhosts_ispconfig.conf the document roots are : Document Root /var/www/web11/web for xxx1.com Document Root /var/www/web10/web for xxx2.net
but when i type ant site, it goes to : Document Root /var/www/
I am running a LAMP server, working to get everything configured and as secure as I can make it. I have been trying to decide weather to change the document root to a different directory, or if it would be better/worse or more/less secure to chown and chmod the current directory.
Any input would be helpful, I just don't want to overlook some small detail as this is my first time handling a server on my own.
And I think everything is working. When openingen 127.0.0.1 I see the apache message that the server is running and when executing phpinfo() it displays the PHP info.
My problem is that I'm trying to change the document root.
After this I did a reboot of the apache server using the CMD httpd -k restart. I even tried restarting using the apachemonitor and rebooted the whole server. But apache still loads the files from c:/Apache24/htdocs
I can't find any more entries with htdocs to change. What am I missing?
I've done some manual change of document root in httpd.conf for a user. I know that now, I don't need to to manual change since user can set there own folder!
Now, If I rebuild Apache, he will re-do all the configuration to the original one. Where can I find the settings for domain document root so I can change it and EasyApache will rebuild the httpd.conf correctly?
I don't want to remove the domain since I'll lost all email account!
However, I plan on running multiple website (not linked whatsoever) on the server. I have LXAdmin and HyperVM. Is it possible to get additional files, such as:
/home/site2/public_html/
then etc..
/home/site3/public_html/
Is this possible? Because, would each need its own IP for the DNS?
Today at 12.50 pm my (ubuntu 14.04.1 LTS) server running plesk 12.0.18 suddenly stopped serving websites. Any attempts to access a webpage on any vhost returned the 502 bad gateway using Nginx error messsage.When I looked at the nginx logs, I found messages like:
Connection refused) while connecting to upstream, client: m.m.m.m, server: , request: "GET /server-status HTTP/1.0", upstream: URL....
Restarting apache & nginx (/etc/init.d/apache2 restart & /etc/init.d/nginx restart) made no difference and I had to reboot to restore http access.
Strangely if I browsed with port 7080 specified (i.e. http://n.n.n.n:7080), this worked fine for all vhosts, so apache (which I believe is listening on this port while nginx listens on port 80) is working fine - nginx is just not able to pass stuff to it?
My current version of nginx in plesk 11.5.44 is 1.5.0 and i would like to update it to the latest stable version which is 1.6.0. However, i cannot seem to manage to do so. I tried with yum update nginx but i receive Package(s) nginx available, but not installed.
this is a fresh Plesk 12 installation on a Dedicated Server, on Debian 6. I haven't installed a License key yet.When i tried to run MIgration Manager, the loading was taking forever. Also, when i try to enter Webserver Configurations Troubleshooter, i get 502 Bad Gateway nginx error.In the /var/log/sw-cp-server/error_log i get this error:
Code: 2015/06/17 11:42:47 [error] 3918#0: *52 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: A.B.C.D, server: , request: "GET /modules/configurations-troubleshooter/index.php/index/list HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "X.X.X.X:8443", referrer: "https://X.X.X.X:8443/admin/module/list?context=modules" When i try to insert a Plesk License, i also get this error:
My server admin already upgraded my OpenSSL to version 1.0.1m 19 Mar 2015 and he also upgraded Nginx to 1.6. I'm also running CentOS v5.11 and Plesk v11.5.
However, he tells me that he still can't get TLS 1.2 to work because he noticed that my server uses a different version of Nginx (sw-nginx), which he believes is part of Plesk. How we can get TLS 1.2 working on the Plesk copy of Nginx (sw-nginx)?
Plesk 12 will not do it and if you reinstall it you get errors after installation. Maybe a bug but seems nobody is interested in answering my question before.
I tried to remove by
apt-get remove --purge sw-nginx dpkg -r sw-ningx
Both of them display that is removed but after a new installation are the folders not created and maybe old files not overwritten if not deleted.
how is it possible that after an update my main site is down? This site: www.orderhosting.it has plesk Panel and I have 20 sites. They work perfectly but my main site is off. I think there is an error in the configuration because:
This is strange.Error log does not report any errors, only this: [warn] RSA server certificate CommonName (CN) `Parallels Panel' does NOT match server name!?
i went to server setting and checked manage php with nginx then start getting 404 Not Found nginx. It was clear that it s a problem with the wordpress permanent links so i went in wordpress back-end and switched to default links then it start working but when i switched to permanent link againi got the previous error again
I searched for a while on internet and i found . URL.... So the problem that i have is that i added this piece of code manually in : /var/www/vhosts/system/domaine.com/conf/nginx.conf....Since it s mentioned above
#ATTENTION! # #DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY, #SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
I have installed the nginx on my server and want to activate it for all my domains, to do this, i have to do it manually for each domains. But there should be an easier way. Apache uses too much ram.
