OT: Dealing with a hosting company with it's head up it's rear end
aryeh.friedman at gmail.com
Mon Aug 17 09:37:25 UTC 2020
On Mon, Aug 17, 2020 at 4:51 AM Dave Cottlehuber <dch at skunkwerks.at> wrote:
> Get your customer’s account manager to talk with their account manager and
> explain that you’ll pull the plug and lawyer up, if std unix ssh isn’t
> allowed and point out that google and aws support it. They always cave.
> Make sure your acct manager is prepped on the tech first.
> how did anybody manage to set these boxes up? It must have been painful.
Read the entire thread to see why your idea likely will not work... I will
just start with there is no IPv6 allowed by the provider (not configured on
their firewall and they refuse to)... continuing onto the hosting company
is *WORSE* than useless in the technical arena (especially the account rep
we have)... The set up we described it what they are *ATTEMPTING* to force
us to move to from something that currently works near the standard way and
thus setting up and maintain currently is not an issue (it will be if they
insist on forcing us to move)... they really don't care about the legal
ramifications and threatened potential counter suits if we insist on the
current setup.... they also have said they consider any 3rd party
proxy/firewall to be a violation of the contract (end of story).
You will also see from our config Google/AWS/any other name brand
provider/etc. would be incapable of the level of customization needed
without a price tag many times larger than the cost of breaking the
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
More information about the freebsd-questions