Forums (Obsolete)

Installation and deployment Questions on installation, system configuration and deployment to the live server.

Version 6.x > Installation and deployment > Deployment on Amazon - CMSFormControls not functioning due port number in URL

View modes:

Member

Community Engine Service Desk - 1/17/2012 12:14:58 AM

Deployment on Amazon - CMSFormControls not functioning due port number in URL

Hi all,

We recently moved our hosting of some Kentico sites to Amazon Web Services (AWS).

We are using sites running Kentico v5.0.3715. The web servers sit behind an Amazon load balancer and these Kentico sites are mapped internally to specific port numbers on the web server.

Following deployment, several functions in the CMS Desk are no longer working correctly, that relate to the WYSIWYG editable areas.

For example, 'Insert/Edit Link', or 'Insert/Edit Media or Image'. The cause of this seems to be related to internally mapping the sites to a port at the load balancer.

The URL's that are being requested in the pop-up window when using 'Insert Link' or 'Insert Media' are referencing the URL with the port number included ...

e.g. http://www.sitename.com:6020/CMSFormControls/Selectors/InsertImageOrMedia ...

and when this happens the user is not able to see any attachments/content/images to select - i.e. they can't insert anything.

The pop-up URL is inserting the port number even though the CMSDesk was accessed using the basic site address without a port number e.g. http://www.sitename.com/CMSDesk

It appears the issue is fixed by accessing CMSDesk from the URL that includes the port number e.g. http://www.sitename.com:6020/CMSDesk

But I wondered if there is a way of fixing this without requiring the users of the CMSDesk to include the Port Number in their browser address bar.

Is this a known issue, or is there some fix or workaround using URL Rewriting ?

Many thanks for any advice.

James

Kentico Consulting

kentico_borisp - 1/17/2012 7:52:12 AM

RE:Deployment on Amazon - CMSFormControls not functioning due port number in URL

Hello,

This seems to be a an setup problem and it's not directly Kentico related. You login through the load balancer and he is during one session changing servers. You need to configure the server to be sticky, if that's an option on the server, so only one server will be requested during session.

Best regards,
Boris Pocatko


Member	Community Engine Service Desk - 1/17/2012 11:28:05 PM RE:Deployment on Amazon - CMSFormControls not functioning due port number in URL Thanks for your info Boris. Unfortunately this doesn't seem to be the cause as we are using stickyness on the Amazon load balancers. Regards,


Kentico Consulting	kentico_borisp - 1/18/2012 6:39:38 AM RE:Deployment on Amazon - CMSFormControls not functioning due port number in URL Hello, I ran this issue by our developer and this seems to be e bug in the 5.0 version of Kentico. Please upgrade to the latest version to fix this issue. Upgrade packages can be found on our homepage. Best regards, Boris Pocatko

Member

Community Engine Service Desk - 1/19/2012 12:22:41 AM

RE:Deployment on Amazon - CMSFormControls not functioning due port number in URL

Thanks for this Boris.

As noted in the original query we are running v5.0.3715.

Can you please check with the developer whether that bug was in that specific version number?

And could you also please ask what version we would need to upgrade to ? Would it need to be the latest hotfix for version 5.0 ?

Or would it need to be the latest of v 5.5 or v 5.5 R2 ?

James.

Kentico Consulting

kentico_borisp - 1/19/2012 12:55:36 AM

RE:Deployment on Amazon - CMSFormControls not functioning due port number in URL

Hello,

Regrettably, we are not able to tell you which exact hotfix it was, because there were 28 bugs fixed on the dialogs alone in the 5.5 version of Kentico. You can try at first to apply the last hotfix for the 5.0 version and if this doesn't work, you will have to upgrade. Our developer also said, that it is most likely fixed in the 5.5 version of Kentico. I would strongly suggest to upgrade up to the 6.0 version, because hotfixes are issued only for the last version and if there is a security bug, you are vulnerable until you upgrade. You should be also able to import your site to the 6.0 version without the need of applying the upgrade packages, if there are only minor customizations done to the site.

Best regards,
Boris Pocatko

Top