Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Dispatcher server wont get content from publisher when accessing on HTTPS

Avatar

Level 2

I have my dispatcher server configured for HTTPS and it will render the content if it has already been cached by accessing my dispatcher site over HTTP. If I clear the cache and try to access the site via HTTPS I get a 404 not found because the cached files don't exist but if it's not found then it should serve and cache the content from my publisher like it does over HTTP.

 

<VirtualHost *:443>
ServerName your-dispatcher-domain
SSLEngine on
SSLCertificateFile /path/to/your/certificate.crt
SSLCertificateKeyFile /path/to/your/private.key

LogLevel debug

<IfModule disp_apache2.c>
DispatcherConfig /path/to/dispatcher.any
DispatcherLog /var/log/dispatcher/dispatcher.log
DispatcherLogLevel 4
DispatcherPassError 1
</IfModule>

<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
DocumentRoot /path/to/your/document/root
<Directory /path/to/your/document/root>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
</VirtualHost>

 

Any additional guidance on this would be very helpful.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 2

The HTTPS (*:443) virtual host was not correctly accessing the dispatcher module settings, leading to difficulties in fetching content from the publisher and logging issues.

 

  • No entries were being logged into dispatcher.log when connecting via HTTPS.
  • The same errors occurred when connecting via HTTP with cache and filtering disabled, suggesting that the virtual host was not using the dispatcher module.

Adding the dispatcher module configuration directly into the *:443 virtual host resolved the issue.

 

LoadModule dispatcher_module /dispatcher-apache.so

<IfModule dispatcher_module>

DispatcherConfig conf/dispatcher.any

DispatcherLog /logs/dispatcher.log

</IfModule>


<VirtualHost *:443>

LoadModule dispatcher_module /dispatcher-apache.so

<IfModule dispatcher_module>

DispatcherConfig conf/dispatcher.any

</IfModule>
ServerName your-dispatcher-domain
SSLEngine on
SSLCertificateFile /path/to/your/certificate.crt
SSLCertificateKeyFile /path/to/your/private.key

LogLevel debug

 

<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
DocumentRoot /path/to/your/document/root
<Directory /path/to/your/document/root>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
</VirtualHost>

This was also the incorrect module for me to use.
<IfModule disp_apache2.c>
DispatcherConfig /path/to/dispatcher.any
DispatcherLog /var/log/dispatcher/dispatcher.log
DispatcherLogLevel 4
DispatcherPassError 1
</IfModule>

View solution in original post

6 Replies

Avatar

Level 2

yes I have my publisher IP and port 4503 set under /renders

Avatar

Community Advisor

Hi @amezcua1,

 

Is the issue with HTTPS access occurring only when you clear the cache and then access the site?

If the cache is maintained then the HTTPS request are being served properly. Correct?

The intent behind the question is to ensure your SSL/TLS configuration on the dispatcher server is correctly set up and the dispatcher is forwarding HTTPS request to publisher.

 

Ideally, The cache should not differentiate between HTTP and HTTPS if the content is the same.

Can you share your dispatcher cache configuration once?

 

Also, as you have enabled Trace logging, is it possible to share the logs for when the request comes via HTTPS vs HTTP to check the difference?

 

Thanks,

Rohan Garg

Avatar

Community Advisor

I believe your https is not configured properly. The dispatcher log will tell you the issue with request if you see the request coming to dispatcher with Https. Can you enable the dispatcher log with log level as trace or debug to get the logs for the request. This will help in tracing back what is not working.

Avatar

Administrator

@amezcua1 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni

Avatar

Correct answer by
Level 2

The HTTPS (*:443) virtual host was not correctly accessing the dispatcher module settings, leading to difficulties in fetching content from the publisher and logging issues.

 

  • No entries were being logged into dispatcher.log when connecting via HTTPS.
  • The same errors occurred when connecting via HTTP with cache and filtering disabled, suggesting that the virtual host was not using the dispatcher module.

Adding the dispatcher module configuration directly into the *:443 virtual host resolved the issue.

 

LoadModule dispatcher_module /dispatcher-apache.so

<IfModule dispatcher_module>

DispatcherConfig conf/dispatcher.any

DispatcherLog /logs/dispatcher.log

</IfModule>


<VirtualHost *:443>

LoadModule dispatcher_module /dispatcher-apache.so

<IfModule dispatcher_module>

DispatcherConfig conf/dispatcher.any

</IfModule>
ServerName your-dispatcher-domain
SSLEngine on
SSLCertificateFile /path/to/your/certificate.crt
SSLCertificateKeyFile /path/to/your/private.key

LogLevel debug

 

<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
DocumentRoot /path/to/your/document/root
<Directory /path/to/your/document/root>
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
</Directory>
</VirtualHost>

This was also the incorrect module for me to use.
<IfModule disp_apache2.c>
DispatcherConfig /path/to/dispatcher.any
DispatcherLog /var/log/dispatcher/dispatcher.log
DispatcherLogLevel 4
DispatcherPassError 1
</IfModule>