Reinstall Exim
/scripts/upcp --force
Fix rpm
/scripts/check_cpanel_rpms --fix
Reinstall Exim
/scripts/upcp --force
Fix rpm
/scripts/check_cpanel_rpms --fix
https://github.com/nodesource/distributions#rpminstall
# Node.js LTS
curl -sL https://rpm.nodesource.com/setup_lts.x | bash -
# Remove old version
yum remove -y nodejs npm
# Clear cache
yum clean all
# Install new Node.js
yum install -y nodejs
yum update
git
package:yum install git
/opt
is a common installation directory for third-party packages, so let’s install the clone to /opt/letsencrypt
:git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt
/opt/letsencrypt
directory:cd /opt/letsencrypt
systemctl stop httpd.service
--standalone
parameter. For each additional domain name requiring a certificate, add -d example.com
to the end of the command../letsencrypt-auto certonly --standalone -d example.com -d www.example.com
Let’s Encrypt does not deploy wildcard certificates. Each subdomain requires its own certificate.
IMPORTANT NOTES: - If you lose your account credentials, you can recover them through e-mails sent to somebody@example.com. - Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/example.com/fullchain.pem. Your cert will expire on 2016-03-31. To obtain a new version of the certificate in the future, simply run Let's Encrypt again. - Your account credentials have been saved in your Let's Encrypt configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Let's Encrypt, so making regular backups of this folder is ideal. - If you like Let's Encrypt, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le
.pem
) file in /etc/letsencrypt/live/example.com/
serves a different purpose:
cert.pem
and chain.pem
)./etc/httpd/conf.d/ssl.conf
or in other .conf file in /etc/httpd/conf.d/
<VirtualHost *:443> ServerName example.com ServerAlias www.example.com DocumentRoot /var/www/html/example.com/public_html SSLEngine on SSLCertificateFile /etc/letsencrypt/live/example.com/cert.pem SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem SSLCertificateChainFile /etc/letsencrypt/live/example.com/fullchain.pem </VirtualHost>
systemctl restart httpd.service
References:
If you’ve been following these posts, we now have a lovely git push to deploy setup, and can ssh into our server without constantly needing to enter our password through the use of ssh keys.
However, if you’re running on cPanel, you will probably have bumped into this error:
SoftException in Application.cpp:256: File "/home/username/public_html/index.php" is writeable by group
This is clearly a permissions error, and so the obvious thought is to chmod it. However, we don’t want to ssh in and chmod every time we push! On the testing server, the permissions are fine, but they are different once the git push has done its post-update.
The reason for this is something to do with a thing called umask. Umask is a user mask which is created for processes that are performing tasks, and affects new files and folders.
The solution to this is to edit ~/.bash_profile, and insert the following command:
umask 022
From now on you shouldn’t have the problem. With newly created files.
To sort already existing files, Chmod -R 755 any folders affected, OR just log out and in, and git pull or git reset –hard HEAD^ in order to re-fetch the files. This time they should be created without any strange permission errors!
Source: https://delboy1978uk.wordpress.com/2014/01/31/fixing-the-cpanel-softexception-writable-by-group/