I created a small website for a local contractor that does well drilling in Waupaca, WI. This is the same company that installed our replacement septic system in Waupaca about 6 or 7 years ago. It is surprising how many small companies still do not have a web presence. The company still shows up on […]
If you have ever ran into this issue you’ll find that you are not alone. There are a number of plugins available that supposedly fix the problem but if you’re like me you hate to install to many plugins. If you are using Nginx/PHP-FPM you can forgo the plugin route and fix this issue before
If you use GlusterFS then you are also using rpcbind. The linux man page provides the following description for rpcbind: DESCRIPTION The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine.
Not sure why but the Edward Snowden address made me chuckle. (especially as it’s tied to a Tor server address???) iptables -L -v Chain INPUT (policy ACCEPT 16471 packets, 4561K bytes) pkts bytes target prot opt in out source destination 216 12760 DROP all — any any 22.214.171.124 anywhere 21 1260 DROP all — any
If you have ever tailed your access logs (eg. tail -f /var/log/nginx/access.log) you may have seen some bad bot signs such as rapid requests for exploitable WordPress plugins or brute forcing logins on your site. The first obvious defence of course is having strong passwords and up to date WordPress files. (from the base install