If you want to create a MySQL admin user that can connect from anywhere, feel free to tweak the string below:
#create SQL Admin user
CREATE USER ‘clusterAdmin’@’%’ IDENTIFIED BY ‘YOUR_cool_password_here’;
GRANT ALL PRIVILEGES ON *.* TO ‘clusterAdmin’@’%’;
FLUSH PRIVILEGES;
If you want to limit connections to localhost, switch the “%” to “localhost”
So i just came across this problem: as i was working with a Raspberry pi, i got the following message: “Segmentation faulty tree” as i was trying to install a few packages on my raspbian jessie.
Luckily, it was a quick fix:
sudo rm /var/cache/apt/*.bin apt update && apt upgrade
So if you’re getting an error similar to this: “500 I won’t open a connection to 10.142.0.9 (only to…” if you’re trying to use FTP on a VM on Google Cloud, fear not, it’s an easy fix.
You can do this 2 ways:
1 – FTP -p remote-host
or
2 – FTP remote-host -> log in -> then type “passive” without quotes, and everything should be just fine.
Enjoy!
So there’s been a change in the way you reset the MySQL root password in MySQL 5.7 as in the “password” field got removed, so the old way of resetting the password doesn’t work anymore:
| authentication_string | text | YES | | NULL | |
So let’s go:
1 – stop the mysqld:
systemctl mysqld stop
2 – start mysqld with skip-grant so it doesn’t ask for your password:
mysqld –skip-grant-tables &
3 – change the pw:
use mysql;
update user set authentication_string=password(‘yourNewPwHere’) where user=’root’;
flush privileges;
quit
4 – stop the mysql
5 – start the mysql with the new root pw
systemctl start mysqld
Enjoy!
If you need a quick and easy fix for broken wordpress permissions - feel free to copy/paste the lines below. These will reset them to defaults.
cd /your/wordpress/folder
find . -type d -exec chmod 755 {} \; # Change directory permissions rwxr-xr-x
find . -type f -exec chmod 644 {} \; # Change file permissions rw-r--r--So if you’re having some issues with SSL connections, it’s higly likely you’re experiencing them from client version openssl 1.0.2. the fix is below and i can confirm it works on both openssl 1.0.1 and 1.0.2.
openssl s_client -connect yourdomain.com:5671 -showcerts
CONNECTED(00000003)
write:errno=104
—
no peer certificate available
—
No client certificate CA names sent
—
SSL handshake has read 0 bytes and written 305 bytes
—
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol : TLSv1.2
Cipher : 0000
Session-ID:
Session-ID-ctx:
Master-Key:
Key-Arg : None
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1484575655
Timeout : 300 (sec)
Verify return code: 0 (ok)
—
openssl s_client \
-cipher RSA \
-connect mydomain.com:5671 \
-servername mydomain.com \
-cert client/cert.pem \
-key client/key.pem \
-CAfile testca/cacert.pem \
-tls1_2
Enjoy!
So i had the weirdest issue today:
Last night, i installed vbulletin as i want to get a forum going for our new project: Dive: Frozen in time – a puzzle-driven skydiving game in Virtual Reality, made by our brand new studio: spinningBOX VR Studios and everything was fine. Went to bed and when i try to login – i can login to the website but not to the admincp. I was pretty amazed, however one really easy fix was this:
change your cookie prefix in core/includes/config.php to rewrite the cookie key.
$config['Misc']['cookieprefix'] = 'bb'; to $config['Misc']['cookieprefix'] = 'bb1'; Problem solved. Enjoy!
So i was trying to spin up a docker app in a node.js docker container but i got the error below:
npm ERR! Linux 4.4.24-boot2docker
npm ERR! argv “/usr/local/bin/node” “/usr/local/bin/npm” “install”
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! path ../rimraf/bin.js
npm ERR! code EPROTO
npm ERR! errno -71
npm ERR! syscall symlinknpm ERR! EPROTO: protocol error, symlink ‘../rimraf/bin.js’ -> ‘/root/src/node_modules/.bin/rimraf’
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>npm ERR! Please include the following file with any support request:
npm ERR! /root/src/npm-debug.log
Quite a cool fix was:
root@3180cd952569:~/src# npm install –no-bin-links
Ended up working just fine. Enjoy!
npm info lifecycle pizza-luvrs@1.0.0~install: pizza-luvrs@1.0.0
npm info lifecycle pizza-luvrs@1.0.0~postinstall: pizza-luvrs@1.0.0
npm info lifecycle pizza-luvrs@1.0.0~prepublish: pizza-luvrs@1.0.0
pizza-luvrs@1.0.0 /root/src
`– good-file@6.0.1
`– fs-extra@0.26.7
`– rimraf@2.5.4
`– glob@7.1.1
+– fs.realpath@1.0.0
+– inflight@1.0.6
`– minimatch@3.0.3
`– brace-expansion@1.1.6
+– balanced-match@0.4.2
`– concat-map@0.0.1npm info ok
root@3180cd952569:~/src#
Some of the stuff that i use more frequently and i still haven’t learned by heart yet, I will be putting them here, in this beautiful cheat sheet.
List all tracked files:
git ls-tree --full-tree -r --name-only HEAD
Untrack file in git:
echo "FILE_NAME" >> .gitignore git rm --cached FILE_NAME git add -u git commit -m "removing file from source control" git pull origin master git push origin master (replace master with the branch you're on)
If you want to easy install Node.js on Ubuntu or RHEL – based systems such as CentOS, I’m just gonna point you towards Nodesource. It’s the easiest thing to do since sliced bread.
However, if you’re into more heavy development and you would like an RVM-like setup, you can try NVM. You will be able to run multiple Node.js versions side by side and more granular control.
Enjoy!