The element type "meta" must be terminated by the matching end-tag "</meta>"

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When starting Fisheye/Crucible and at varying intervals while the application is running, the following error appears in fisheye.out:

[Fatal Error] :13:3: The element type "meta" must be terminated by the matching end-tag "</meta>".

Cause

This error is caused by the XML parser encountering XML that does not have a matching end tag being returned from some endpoint. It can caused by many factors and needs to be investigated individually. In one specific case, this was caused by the Analytics plugin making a request back to Atlassian, but was blocked by a proxy that prevented external internet access. The HTML returned by the proxy had a <meta> tag that was not closed.

Workaround

Disable the Analytics plugin via Administration => Global Settings => Analytics.

Resolution

Address the response being returned so that the <meta> tag is properly ended.

DescriptionInvalid XML causes a fatal error in fisheye.out
Product
Fisheye
Last modified on Jun 3, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.