Short answer: Yes.
There was a change to SSL specifications that went into effect this October, I think, that you can only certify a certificate against a DNS name, not an IP. It's for additional security and stability. There may still be some certification authorities out there using the old method (doubtful), but most now only accept a DNS name.
Thanks for the quick answer. But do I really need to put a FADN or can I keep it with the IP address? If I need to change it and I have a host name do I have to make it SSL?
If you want to use SSL securely, you need a domain. If you're happy leaving the data vulnerable to packet sniffing, then you can use a raw IP.
I wouldn't recommend it (and neither does FMI). But you can judge for yourself the level of risk you're assuming.
I See, how do I switch from IP to my Domaine name?
You need a couple of things:
1) Make sure you have a fixed IP address for the server (which your networking provider can usually help with).
2) Create the domain name and register it with someone like GoDaddy, etc., so the domain name is entered on one or more domain name servers.
There are some services out there that can provide you with the fixed IP without needing to go through your Internet provider. dnsdynamic.com is one example. They act as a forwarding service and keep up with your server's DHCP lease changes.
Sorry for the delay. I tried and everything works like a charm. Thanks for all your advice, it REALLY helped me.