Using SSL on a different port than 443

If you have questions about using mojoPortal, you can post them here.

You may want to first review our site administration documentation to see if your question is answered there.

This thread is closed to new posts. You must sign in to post in the forums.
9/21/2010 10:07:58 PM
mentatx
Gravatar
Total Posts 2
View Posts

Using SSL on a different port than 443

I'm new to mojoPortal, but so far it's been a dream. Keep up the good work!

One thing I keep coming back to, however - I have two mojoPortal sites and two other regular .NET-based websites (so four Web Sites, on IIS7, Server 2008 R2) all on one IP, using host headers. My main site (mojoPortal based) uses port 443 for SSL. I'd like to use SSL on port 4433 for my other mojoPortal website. I can't seem to find a way to do this - mojoPortal always seems to use 443 when it sees https in the url.

I've tried the following web.config keys/values to no effect:

SSLIsAvailable="true"
MapAlternateSSLPort="true"
AlternateSSLPort="4433"

Any help is appreciated. Thanks!
Matt

9/22/2010 7:37:05 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Using SSL on a different port than 443

Hi Matt,

mojoPortal always seems to use 443 when it sees https in the url

mojoPortal has no control over what ports it runs on, it cannot choose ports, that is controlled by IIS.

I have not tried using an alternate port for SSL in a long time though I know for sure it worked at one point.

What I do know is that using non-standard ports on a public facing web site is a bad idea. Many corporate firewalls will only allow standard ports for their users so it will not be possible for those users to access your site on a non-standard port

Hope it helps,

Joe

9/22/2010 11:36:58 AM
mentatx
Gravatar
Total Posts 2
View Posts

Re: Using SSL on a different port than 443

Joe,

I really appreciate the response. I am not concerned with corporate network access, as this is a personal website (using 4433 for SSL) and I only need SSL to secure logins and such. I'll be the only one using SSL on this website, and it'll be on my home network (behind a pfSense firewall that I fully control).

I guess I'm disappointed in that the keys exist in the web.config file, but they don't work as intended. They don't on my installation, at any rate. I installed using the web installer. I feel like they should be removed if they don't work =)

I can manually pop in the :4433 in the browser URL for now. It's not quite a deal breaker about using mojoPortal, but I really wish this feature worked... Maybe in the next release?

Thanks,
Matt

You must sign in to post in the forums. This thread is closed to new posts.