404 pages when using Dispatcher

[DKWilliams]

I have just finished configuring Dispatcher and have apparently made a configuration error that I can't see m to fin.  I have a server with Author, Publisher, and IIS installed on it, and I have configured Dispatcher to work with IIS (AEM 5.6.1, Dispatcher-iis-windows-x64-4.1.4).  I have activated teh Publish agent from my Author instance and that is working fine, I see page changes when made.   When I go to the Publisher URL (http://localhost:4505/content/geometrixx/en.html) I get the correct page view.  When I go to http://localhost/content/geometrixx/en.html I get a 404 error.  My dispatcher log shows the following:

[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Dispatcher initializing (build 4.1.4)
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] farms[website].homepage = /geometrixx/en.html
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] farms[website].cache.docroot = C:\inetpub\wwwroot
[Mon Feb 24 15:04:42 2014] [I] [3704(6024)] Dispatcher initialized (build 4.1.4)
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Found farm website for (my server IP address)
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] checking []
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] no cache due to missing extenson in uri:
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] cache-action for []: NONE
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] connected to render publish1 (localhost:4505)
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: host
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: accept-language
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: user-agent
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: dnt
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: accept
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: accept-encoding
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: APPL_MD_PATH
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: APPL_PHYSICAL_PATH
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: CONTENT_LENGTH
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: HTTPS
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: INSTANCE_ID
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: INSTANCE_META_PATH
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: REMOTE_ADDR
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: REMOTE_HOST
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: REQUEST_METHOD
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: SCRIPT_NAME
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: SERVER_NAME
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: SERVER_PORT
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: SERVER_PORT_SECURE
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: SERVER_PROTOCOL
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: SERVER_SOFTWARE
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Spooling request header: URL
[Mon Feb 24 15:04:42 2014] [D] [3704(6024)] Content length: -1, written: 101
[Mon Feb 24 15:04:42 2014] [I] [3704(6024)] "GET " 404 ~ 0ms

At this point, I have stripped my dispatcher.any file down to the bare bones, trying to sort out the problem.  Here is the content of it:

# name of the dispatcher
/name "test"

# Each farm configures a set of load balanced renders (i.e. remote servers)
/farms
  {
  # First farm entry
  /website
    {
    
    /homepage "/geometrixx/en.html"
    /clientheaders
      { "*"  }
    /virtualhosts
      { "*"  }
    /renders
      {
      /publish1
        {
        /hostname "localhost"
        /port "4505"
        # /timeout "0"
        }
      }
            
    /filter
      {
          /0001  { /glob "*" /type "allow" }
      }

    /cache
      {
       /docroot "C:/inetpub/wwwroot"

       /rules
        {
        /0000
          {
          /glob "*"
          /type "allow"
          }
        }
    }
 
    /statistics
      {
      /categories
        {
        /html
          {
          /glob "*.html"
          }
        /others
          {
          /glob "*"
          }
        }
      }
    }
  }

I would appreciate any advice on where I've gone wrong on configuring this.

Diana W.

[basitsh]

Hi @marcussick Cell Phone Chargers
Happy to help! Feel free to reach out if you have any further questions or need assistance. I'm here to support you. Just drop me a message anytime! 

[marcussick]

Hi @basitsh eHallPassInsider
Absolutely! Your expertise is invaluable. I'll be sure to keep you in mind for any future advice or assistance needed. Thank you once again for your help!

[PareshDy]

Looking to streamline your business operations with cutting-edge technology? Look no further than our Certified Microsoft Dynamics 365 Partner services. With unparalleled expertise and a proven track record, we specialize in implementing Dynamics 365 solutions tailored to your specific needs. Whether you're seeking seamless CRM integration, efficient ERP solutions, or robust business analytics, our team of certified professionals is dedicated to delivering excellence every step of the way. Trust in our knowledge, experience, and commitment to elevate your business to new heights with Microsoft Dynamics 365.

[JackWi1]

To address the 404 error you're experiencing, let's fine-tune your Dispatcher configuration with these specific changes:

Virtual Hosts Configuration:

Your existing virtual host setup is broadly configured to accept all hosts, as indicated by "*". It's essential to ensure that this aligns with your IIS configuration. If your IIS is set to handle requests for a specific virtual host only, you need to adjust this section to match the exact virtual hostname(s) you are using.

Homepage Configuration:

It appears your homepage configuration, noted as "/homepage", is generally correct. However, make sure this configuration accurately reflects your AEM site's path structure. For instance, if your homepage actually resides at "/content/geometrixx/en.html" on your Publisher instance, you should update this setting accordingly.

Filter Configuration:

Your current filter setup ("/filter") allows all requests to pass through. While this may be suitable for general testing, it's important to tailor this configuration to your specific needs for enhanced security and performance. If no special filtering rules are necessary for your environment, it may already suffice for preliminary testing.

Cache Configuration:

The cache configuration you've noted ("/cache") seems straightforward and functional. Ensure the specified docroot path is correct and that the Dispatcher can access this path without any problems.

Render Configuration:

In the "/renders" section, verify that the details match those of your AEM Publisher setup exactly. The specified port (4503) must be accurate and should be free from any network or firewall restrictions that could hinder communication.

Dispatcher Log Review:

Since the logs show a 404 error, it's important to compare the URL you are requesting with the actual structure and setup of your AEM site, paying special attention to the properly configured homepage.

Once you've made these detailed checks and adjustments, try accessing the URL again and monitor the Dispatcher logs for any changes or new insights. If problems persist, delve into both the IIS and AEM logs to uncover more detailed information about the cause of the 404 error.

[JackWi1]

To address the 404 error you're experiencing, let's fine-tune your Dispatcher configuration with these specific changes:

Virtual Hosts Configuration:

Your existing virtual host setup is broadly configured to accept all hosts, as indicated by "*". It's essential to ensure that this aligns with your IIS configuration. If your IIS is set to handle requests for a specific virtual host only, you need to adjust this section to match the exact virtual hostname(s) you are using.

Homepage Configuration:

It appears your homepage configuration, noted as "/homepage", is generally correct. However, make sure this configuration accurately reflects your AEM site's path structure. For instance, if your homepage actually resides at "/content/geometrixx/en.html" on your Publisher instance, you should update this setting accordingly.

Filter Configuration:

Your current filter setup ("/filter") allows all requests to pass through. While this may be suitable for general testing, it's important to tailor this configuration to your specific needs for enhanced security and performance. If no special filtering rules are necessary for your environment, it may already suffice for preliminary testing.

Cache Configuration:

The cache configuration you've noted ("/cache") seems straightforward and functional. Ensure the specified docroot path is correct and that the Dispatcher can access this path without any problems.

Render Configuration:

In the "/renders" section, verify that the details match those of your AEM Publisher setup exactly. The specified port (4503) must be accurate and should be free from any network or firewall restrictions that could hinder communication.

Dispatcher Log Review:

Since the logs show a 404 error, it's important to compare the URL you are requesting with the actual structure and setup of your AEM site, paying special attention to the properly configured homepage.

Once you've made these detailed checks and adjustments, try accessing the URL again and monitor the Dispatcher logs for any changes or new insights. If problems persist, delve into both the IIS and AEM logs to uncover more detailed information about the cause of the 404 error.