Good news – VMware tools installation got way easier since Ubuntu 16.04 x64 and Debian 8 x64 😉 just do the following:
1) Install open-vm-tools from repository:
apt-get install open-vm-tools
2) Profit :), well maybe reboot first 😉
Today I had a weird problem – my X2Go Client just kept saying “Unable to create SSH tunnel for X2Go session (NX) startup”. I tried to reboot remote server but no luck. What is the solution?
It’s rather easy – reboot the local computer you are trying to connect from (yes the PC you are sitting in front of), after that it should be fine.
Setup: Ubuntu x64 server 14.04.3 LTS running XFCE as GUI. The client I was connecting from: Windows 7 Pro x64.
Well it's fairly self explanatory - you are running any service that needs customer's real IP address and now you have a problem - it shows only the proxy address of CloudFlare, this is especially painful when you do for example access restrictions (IP restrictions) via .htaccess file.
So how to fix this on Debian 7?
Btw. the # means you need to be root just fyi...
1) Check for dependencies:
# apt-get install libtool apache2-threaded-dev
2) wget the necessary files:
# wget https://www.cloudflare.com/static/misc/mod_cloudflare/mod_cloudflare.c
(Just Read more [...]
The instructions are pretty much same as for 12.04 LTS, which I described in detail here.
Though to make it complete:
1/ Bootup, login as root, click "Install VMWare tools" from your host machine
2/ mount the ISO:
mount /dev/cdrom /mnt/cdrom
you might need to make directory for it first:
3/ copy the files from there to temp:
cp /mnt/cdrom/VMwareTools-*.tar.gz /tmp
4/ unpack it:
tar -xvzf VMwareTools*.tar.gz
5/ do the installation (you can omit -d Read more [...]
I moved my WordPress from one server to another and run into "500 Internal server error", apparently this problem was connected with configuration in .htaccess file or more specifically WP Super Cache plugin that caused this problem as the data in .htaccess file were incorrect (pointing to wrong direction).
Here are the easiest instructions what to do if you have the same problem:
1) rename .htaccess to something like ".htaccess.old"
2) put there blank .htaccess which includes only following:
# Read more [...]