port for secure server

[Stephen]

Can anyone confirm for me that 443 is the port for the secure community server https://secure.futurequest.net

I figure it must be, but wanted to make sure. (I also realize that I don't have access to it yet--I'm still weighing my options.)

Thanks.

[Justin]

Yes, 443 is the default SSL port - you don't need to specify the port on any SSL enabled browser (and any non-SSL browser wouldn't be able to access the site anyway). The HTTPS:// prefix identifies it as SSL, port 443 unless otherwise specified.

Now our own secure pages are located on port 611, but that won't affect the shared certificate, just our internal SSL area.

Note that on the NINE server, the URL would be https://secure09.futurequest.net/, and on SIX it is simply https://secure.futurequest.net/.

HTH

------------------
Justin Nelson
FutureQuest Support

[Stephen]

OK. But this begs the next question.

Since I'm on TAZ does this mean I'll be moved onto another server when I buy into shared ssl? Would I be required to move onto NINE and use that ugly URL you guys chose (really, you could have come up with something better--like secure.nine.futurequest.net or secure.blue.futurequest.net or *anything* lacking digits)? Too late to add an alias?

Stephen

[Deb]

Yes, the account would be moved to the NINE server and the URL does need to be https://secure09.FutureQuest.net

To be able to have a URL that is consistent with your own domain name like https://secure.yourdomain.tld/ then obtaining your own Secure Certificate is the key.

Deb

[Stephen]

I can live with that ugly URL for now (until the nickels and dimes start rolling in). But since yesterday I have been unable to successfully request the shared secure server. This page:

http://www.FutureQuest.net/Order/vas.php?service=1

gives me an error (something about improper formatting, but I cannot figure out what the exact problem is).

Could you take a look? Thanks. If the page is functioning right, perhaps it could do with some extra instructions?

[Deb]

Was the error you received: The domain name you have given is not formatted properly or is otherwise invalid. ?

If so the error is saying that where it asked for Domain Name you put in something that it believes to be incorrect.[nbsp][nbsp]Try putting in only <font color=#FF0000>yourdomain.com</font> without any slashes or the http: part or any other parts whatsoever.

Adding extra parts of an address that are not technically part of the domain name and tld itself can cause this error.

Deb

[Stephen]

OK, problem solved.

It turns out that the domain name field on that form is case sENsiTIvE which I wasn't expecting. Apparently lower case is what is required (at least in my case).

Stephen