hazelesque

ID                                                                          STATE    STARTED            CONTROLLER APP  CONTROLLER TYPE
cargo3.onyx.leicesterhackspace.org.uk-1fe918ae-f437-43ae-9010-08422cefbdd7  running  17 minutes ago     postgres        postgres
cargo1.onyx.leicesterhackspace.org.uk-ef4faf34-ddcc-43e3-ad8c-819f7a2e2690  running  17 minutes ago     postgres        postgres
cargo2.onyx.leicesterhackspace.org.uk-fb2b5a63-8691-4db7-87a2-cfd89eb2ba51  running  18 minutes ago     postgres        postgres
cargo2.onyx.leicesterhackspace.org.uk-8cf524c2-87b5-4300-9083-7f919997f67e  running  26 minutes ago     postgres        postgres
cargo3.onyx.leicesterhackspace.org.uk-505d3c7d-ecbc-4974-9fbf-33726c4c1411  done     41 minutes ago     hmis            
cargo1.onyx.leicesterhackspace.org.uk-d1ccacbf-0030-4ddf-831d-425269dcc39d  crashed  42 minutes ago     postgres        
cargo3.onyx.leicesterhackspace.org.uk-e78ebbf3-6274-4861-89f0-24103fc19547  done     About an hour ago  hmis-staging    
cargo2.on

hazelesque

# -*- mode: ruby -*-
# vim: set ft=ruby ts=8 sts=2 sw=2 et:

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

unless Vagrant.has_plugin?("landrush")
    raise 'Cannot continue, landrush is not installed! Run "vagrant plugin install landrush" and try again!'
end

hazelesque

(Re: https://feedback.rackspace.com/forums/250746-cloud-hosting/suggestions/6425206-support-the-proxy-protocol -- my comment appears to be stuck in moderation, so pasting it here)


We run an internet-facing SFTP service with Cloud Load Balancers in front of our backends, and the lack of support for PROXY Protocol is a serious pain for us.

It makes it impossible to do things like fail2ban-style realtime blacklisting in response to repeated failed authentication attempts, as we have no way to determine the IP of the actual client.

As a result, we've had to restrict the permitted authentication methods to SSH keys only, as without the ability to log (and ban) fraudulent login attempts, password authentication is just too risky.

Can this question actually get an answer?