Your frontend CDN (eg. Cloudflare or even your own load balancer/proxy) must be sending the X-Forwarded-For and you must be running Apache on the backend. This solves the problem where your logs and services will only see the proxy/CDN IP and not the real client IP. modremoteip is the most modern and current working solution Step 1.) Enable remoteip a2enmod remoteip Step 2.) Edit/Enable the correct config Edit t........

First we need a few extra packages: apt update apt install -y adduser libfontconfig1 musl sudo wget https://dl.grafana.com/enterprise/release/grafana-enterprise_10.3.1_amd64.deb Install / Enable Grafana dpkg -i grafana-enterprise_10.3.1_amd64.deb dpkg -i grafana-enterprise_10.3.1_amd64.deb (Reading database ... 44309 files and directories currently installed.) Preparin........

haproxy is one of the best known and widely used Open Source load balancers out there and a strong competitor to nginx. haproxy is used by many large sites per Wikipedia: HAProxy is used by a number of high-profile websites including GoDaddy, GitHub,........

This can be a real pain when automating things and you do an apt install and some packages ask a lot of questions. Make sure you set this variable when running: DEBIAN_FRONTEND=noninteractive Remember as well that if chrooting you will want to run like this: DEBIAN_FRONTEND=noninteractive apt install -y yourpackagename ........

When running cudaminer once it tries to initialize the card the entire screen freezes. The computer itself is still running but the Xorg is done for, you cannot even switch to another console window and must reboot (even an mdm or Xorg restart does not help). At first cudaminer will give you these errors: stratrum_recv_line failed ...retry after 15 seconds GPU #0: Geforce 210 with compute ca........

Iused the slightly older "304.117" version and it worked. With the newest version Icouldn't get X to start and kept getting these errors in messages/dmesg. [ 2346.083660] nvidia 0000:01:00.0: irq 44 for MSI/MSI-X [ 2350.608342] NVRM: RmInitAdapter failed! (0x12:0x2b:1831) [ 2350.608354] NVRM: rm_init_adapter failed for device bearing minor number 0 [ 2350.608369] NVRM: nvidia_frontend_open: minor 0, module->open() failed, err........

One of my test Centos 5 containers was on a partition that filled up and it threw all sorts of errors and stopped responding but now I can't boot it again anymore. All the console shows is the Linux Penguin on the top left corner and the xm console says "usbcore: registered new driver hub" and has halted there. Centos 5 Xen container stuck/frozen won't boot on "usbcore: registered new driver hub" Another great way of troubleshooting is booting fro........