Issue in changing frontal server instance config to explicit hostname

[sraz]

Hi All ,

We want to update the frontal server's config file so that it only listens to specific hostnames (for example  the "mkt" hostnames) instead of all of them. Right now, the config file is set to host='*', meaning it listens to all hostnames.

We want to change it to use a list of specific hostnames separated by commas, like host='mkt-frontend.example.com,tracking.example.com' .

However, when we make this change, the tracking and redirection features stop working correctly.

Is there something we should check, or do you have any suggestions on what might be causing the issue?

Thank You!

[MeitMedia]

Hi @sraz ,

When updating the frontal server's configuration file in Adobe Campaign Classic to listen to specific hostnames, several factors could be causing the tracking and redirection features to stop working. Here are some things you should check and consider:

1. Hostnames and Certificates:

• Ensure that the specified hostnames (mkt-frontend.example.com, tracking.example.com) are properly configured in your DNS and that they resolve correctly to the IP address of the frontal server.
• Verify that the SSL certificates installed on the server cover all specified hostnames. If the certificates don’t match, HTTPS connections could fail, affecting tracking and redirection.

2. Network and Firewall Configurations:

• Check if there are any network or firewall rules that might be restricting access to the newly specified hostnames.
• Ensure that the ports (typically 80 for HTTP and 443 for HTTPS) are open and correctly configured for these hostnames.

3. Apache/IIS Configuration:

• If you are using a web server like Apache or IIS as a reverse proxy in front of the Adobe Campaign frontal server, make sure the virtual host configuration is updated to reflect the new hostnames.
• Ensure that the ServerName and ServerAlias directives in your web server configuration are correctly set up for each of the specified hostnames.

4. Frontal Server Configuration:

• When changing the host attribute in the config xml file, ensure that the hostnames are correctly listed and that there are no syntax errors.
• Double-check the tracking and redirection settings in the configuration to ensure they reference the correct hostnames.

5. Campaign URLs:

• After making the changes, ensure that the URLs used in your campaigns for tracking and redirection are updated to reflect the new hostnames. Inconsistent URLs could lead to tracking issues.

6. Log Files:

• Review the logs (web.log, webmdl.log, etc.) on the frontal server for any errors or warnings related to the hostnames or tracking.
• These logs might provide more detailed information about what’s going wrong when the hostnames are restricted.

7. Testing:

• Test each hostname individually to ensure that the frontal server responds correctly and that tracking and redirection work as expected.
• Sometimes, issues might arise from a specific hostname not being configured correctly.

8. Fallback and Rollback:

• Consider gradually implementing the changes by testing them in a staging environment first. If issues persist, roll back to the previous configuration (host='*') and analyze the differences.

9. Adobe Support:

• If the issue persists after checking the above points, it may be worth contacting Adobe Support. They can provide more specific guidance, particularly if there are undocumented nuances in how Adobe Campaign handles multiple hostnames.

This systematic approach should help identify and resolve the issue.

Best regards,

MEIT MEDIA (https://www.meitmedia.com)

Find us on LinkedIn

Contact Us: infomeitmedia@gmail.com

[sraz]

Thank you @MeitMedia for the response.

There's a proxy server in front of the frontal server, which might be causing the issue. We'll look into this further.

Best Regards,

Sraz