All subdomain errors and solutions

taggrs-subdomain-example

Recognizing and resolving subdomain-related errors is crucial for ensuring smooth implementation and operation of Server Side Tracking via TAGGRS. This support article outlines common subdomain errors and the steps you can take to address these issues.

1. Error 502: Load Balancer Issues

The 502 error indicates problems with the load balancers. This may signify temporary service unavailability due to maintenance or unexpected issues on our end. 

Action: Contact our support for more information and assistance.

2. Error 503: Servers May Be Down

A 503 error suggests that our servers may be down. 

Action: Check TAGGRS's status page for current service status information and expected resolution times.

3. DNS_PROBE_FINISHED_NXDOMAIN: DNS Not Validated

This error occurs when the DNS records for your subdomain have not been validated or are incorrectly set. 

Action: Follow our guide to configure your subdomain to correctly set up DNS settings.

4. File Not Found

If your subdomain displays a 'file not found' message, it means that the standard TAGGRS fondant subdomain is temporarily unavailable. 

Action: Contact us to resolve this issue.

5. Preview Mode Error: "Configuration Code Mismatch"

This error indicates that the preview server is not correctly linked, resulting in a configuration code mismatch. 

Action: Contact support for assistance in correctly linking your preview server.

6. Error 404: Various Causes

A 404 error can occur for various reasons:

- SGTM Container Removed: If the SGTM container for your site has been removed.

- SGTM Container Not Published: If the SGTM container is not published.

- Incorrect Configuration Code: When using the wrong configuration code.

Action: Ensure your SGTM container is correctly configured, published, and the correct configuration code is being used.

7. SSL Error on the Subdomain

If the developer accidentally changed something in the DNS settings. You may get an SSL error on the subdomain. If you are not using the enhanced tracking script, you will only collect client side data. 

Action: In this case, ask the developer if the DNS settings of your container still match the current settings.

Conclusion

By understanding these common errors and their solutions, you can ensure the functionality of server-side tracking via TAGGRS on your subdomains. Should you need additional support or encounter other errors, do not hesitate to submit a support ticket.