How hard can it be??

[cptbob123]

Right, This is getting beyond a joke...

I have been in countless chats and a very long ticket for a simple request...

Ticket ID: BFI-12988783

My requirement: To have a FTPES Server with a signed certificate (on its own IP so you don't need to have the @ to login)

I have the FTPES server for our domain setup nicely, it logs you in without a @domain and works perfectly. So I put in a ticket to get the Cert signed and put in that I want it on x.x.x.179 IP address.

A certificate is "installed". Still get a warning, I'm told the cert is for 178 not 179. When in talks, apparently because its not a web service the IP is irrelevant (I find this hard to believe but anyway).

So to make is work HG changed my DNS so the domain pointed at x.x.x.178. Ok great thanks for breaking our FTP service for all out users over the weekend...

I'm pretty sure (but not certain) that the reason the cert doesn't work is it was bought for the wrong IP address... A "supervisior" has looked at my ticket and fed my some information which I am annoyed about:

"In order for the SSL to work with ftpes the domain name ***** has to be pointed to .178 unfortunately there is no way around this and the only way to then login would be to use user@domain.com as the ftp username. This is now working and accepting the SSL when you login to ftp that way."

I need a technical reason if this is true (which I beg to differ) PLUS if this is true, cancel the SSL and we will move the Dedicated servers we have to a new provider as this is ridiculous that you can't do this!

This has been going on for toooo long!

[GatorDHanna]

You should have received a reply from Ford, who is one of our level three system administrators here with some additional information and some questions. Your ticket is assigned to Ford, so if you have any questions or concerns, reply and he’ll see it.

I'm sorry that this has been so complicated. Please let me know what other information you need and I’ll be happy to get it for you.