We use this same setup on our 6.2 AEM instance and everything works correctly.  When I navigate to stage.site1.com/en_us/home.html the content appears on our 6.2 instances, however, when I switch our CDN (Content Delivery Network) to point to 6.3 instead of 6.2 I receive a 404 error but only have I ...

Prod Author Environment: AEM 6.2Yes, I am using dynamic media. Turning it off is not an option.  Works perfectly fine in our stage environment. All images are uploading to our author environment.  However, when I go to our pages and edit a component by adding the new image.  Nothing appears.  Then w...

Yes.  Turning off minification resolved the issue.

Thanks this was just what I was looking for.  The solution to my problem was found at the bottom of the page (link below). Https URL' resulting with 404 after in place upgrade of 6.2(6.1 to 6.2) In the dispatcher.any/clientheaders.any added "X-Forwarded-Port"

Here is the Not Found error:The requested URL /en_us/home.html was not found on this server.Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Hello,My organization is currently upgrading our AEM environment from 6.1 to 6.2.  We completed our stage setup and are experiencing zero issues.  The URLs are working without any issues.  However, when we move the same dispatcher code to PROD when we try testing the production URLs by spoofing our ...

Minify CSS and JS was being used.  I turned this functionality off which resulted in the proper CSS & JS files from being imported.

Thanks.  The code was referencing the incorrect file.  Once I updated the path everything started working.

We are currently migrating from 6.1 to 6.2.  Locally installed 6.2 on my computer and installed all packages.  The code worked without any issues.  However, after Adobe setup my new 6.2 environment, I followed the same steps but now I am getting the following error every time I try to edit a widget ...

The link you provided is not what I am trying to do.  I want to add a video to the DAM, then add a tag and on publish it uploads to YouTube.  The link you provided is creating a Video component which is something I don't want to do.