Change Installed Port

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
7/28/2010 10:03:24 PM
Gravatar
Total Posts 4

Change Installed Port

I have installed mojoportal on my existing webserver. My current site is of course using port 80. I didn't want to take it down yet, so when I set up the new site I set it up on port 81 so the owner could see the new site as I was setting it up. We are ready to switch over to the new site. I tried this yesterday by going into IIS and stopping both sites and going to the proerties of the new one and changed it from 81 to 80. Started the new site up. I could then reach the new site by http://www.domain.com. The page did not load all the way and I could see in the status bar that it was trying to load content from the old location. In the status bar I could see loading http://www.domain.com:81/privacy.aspx. So I obviously am missing something somewhere to change it to port 80. I have gone into the Site Settings under Administration and cannot find where else I need to change. Can someone please point me where I need to go?

Much appreciated.

Server 2003

SQL Server 2008

2.3.3.9 MSSQL

7/29/2010 5:45:20 AM
Gravatar
Total Posts 18439

Re: Change Installed Port

Maybe your browser cached the previous version of the page that had port 81 in the link urls. Clearing the browser cache may help.

7/29/2010 8:41:20 AM
Gravatar
Total Posts 4

Re: Change Installed Port

Sorry, I should have put that. I did clear the browsing cache and even tried it on a different computer and same effect.

Once I had it on the new port and opened the webpage, I went to Site Settings again and the option for the privacy page still showed domain.com:81 and then the field to put the location.

7/29/2010 11:53:00 AM
Gravatar
Total Posts 18439

Re: Change Installed Port

I have no idea, if the site is running on port 80, there is certainly nothing in mojoPortal that will try to use another port. When we run it in the Visual Studio web server it always uses a random port and that never causes any problems so I suspect some IIS configuration issue.

Maybe there is a proxy server involved complicating the matter.

7/29/2010 5:45:12 PM
Gravatar
Total Posts 4

Re: Change Installed Port

With my scenario, was I doing it the correct way? Just going into the site properties in IIS and changing the port?

If not, can I back it up and set it up again and restore all the data?

7/30/2010 9:56:07 AM
Gravatar
Total Posts 18439

Re: Change Installed Port

There is nothing in the data that stores the port so no need to restore data.

Possibly if you have more than one IIS site using the same ip address and the same port there is a conflict and IIS may revert the second site back to port 81. You can use the same ip and port for multiple sites without conflicts if you specify host headers for the domain name so that IIS knows which site is supposed to handle the request. But if you configure 2 sites with the same ip and the same port and don't use host headers there will be conflicts.

Also if you had configured some proxy server or firewall routing so that your customer could use port 80 when it was really running on port 81 then you need to undo that.

Hope it helps,

Joe

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