to 127.0.0.1 ::1 localhost or you will probably receive a 403 Forbidden Error.Īs always make sure you restart Apache so your changes take effect.Īnd you should be good to go.
#PLESK MAILLOG CODE#
Then find and uncomment the following code in that file.Ĭhange. Don't forget to back up that file first.Ĭp -a /etc/httpd/conf/nf This just means you need to uncomment the /server-status location in Apache's configuration file. The requested URL /server-status was not found on this server.
#PLESK MAILLOG INSTALL#
Simply install links or if that is not available, elinks should work as well.įrom here you may receive a 404 ~]# /etc/init.d/httpd fullstatus The 'links' package is required for this functionality. First you may need to install the links package or something ~]# /etc/init.d/httpd fullstatus There are some changes you may need to make. Some servers do not allow you to view Apache's status by default. This is very similar to the cPanel /scripts/rebuildhttpdconf script. usr/local/psa/admin/bin/httpdmng -reconfigure-all If for any reason you find that these files have been corrupted, or were not removed after a domain/webspace was, and Apache will no longer start, you can run the following: These local configuration files are similar to cPanel's main nf, as they are automatically generated, and should not be edited manually.
rw-r-r- 1 root root 2 Feb 3 03:26 stat_ttl.conf Lrwxrwxrwx 1 root root 10 Jan 30 17:50 last_nf -> nf If one were to ls -lah this directory, one would see something similar to the following:
var/In older versions of Plesk, the files were located under /var/www/vhosts/$DOMAIN.TLD/ The domain vhosts are located in the following configuration file: Plesk's /etc/httpd/conf/nf is what you would expect to see on a core-managed server.
One of the first things that you will likely notice when trying to troubleshoot Apache on Plesk, is that it does not structure it's domain configurations/vhosts like cPanel/EA3 does. So please, save yourself (and SysRes) the time and headache: check your version and add that information to your phone log/ ticket note/ admin note for the account. You should always be checking this account when entering SSH, and it is strongly encouraged to make this a habit just like checking 'who' when you first login:ĭue to the amount of customization that a user can place on a Plesk control panel, it is not uncommon to see a Plesk 9, Plesk 10, and Plesk 11 installation look very similar to an inexperienced or new technician. Please be careful when beginning to work on a Plesk on Linux server. This means that while some command-line activity is ok, some activities - such as DNS edits and updates to the form or function of a domain - can only be performed from within the control panel environment failure to observe this process will likely cause the server to behave erratically (in rare cases) or suffer catastrophic failure (much more likely to happen). One of the most important things to keep in mind when working on an account that uses the Plesk control panel is that Plesk is (essentially) a single, giant database.
0 kommentar(er)
