Problem with Back Office after deploying to AWS (BitBucket)
I am deploying a new site with Umbraco 7.4.0 to an Elastic Beanstalk application. This is just a container for a regular Amazon EC2 instance (windows server 2012 R2 Core)
I made a simple "Web Deployment Package" deployment using the Visual Studio.
After deployment my site works, but the back office will not load. On inspecting the HTTP requests in the browser, there is an attempt to load this URL resulting in a 404:
/Application?umb__rnd=1636f0a4
In working environments, the equivalent request starts with /umbraco:
/umbraco/Application?umb__rnd=ffffffffc6b5475c
I have employed the exact same package to a local IIS instance and a regular AWS windows instance and it works as expected (the above GET starts with /umbraco). So it seems this issue is specific to the beanstalk environment.
Has anyone experienced this before or have any idea why umbraco would try and request /Application instead of /umbraco/Application ?
Problem with Back Office after deploying to AWS (BitBucket)
I am deploying a new site with Umbraco 7.4.0 to an Elastic Beanstalk application. This is just a container for a regular Amazon EC2 instance (windows server 2012 R2 Core)
I made a simple "Web Deployment Package" deployment using the Visual Studio.
After deployment my site works, but the back office will not load. On inspecting the HTTP requests in the browser, there is an attempt to load this URL resulting in a 404:
In working environments, the equivalent request starts with /umbraco:
I have employed the exact same package to a local IIS instance and a regular AWS windows instance and it works as expected (the above GET starts with /umbraco). So it seems this issue is specific to the beanstalk environment.
Has anyone experienced this before or have any idea why umbraco would try and request /Application instead of /umbraco/Application ?
Just a quick bump as this post was originally detected as spam and when approved ended up buried :)
is working on a reply...