# An error occurred while rendering message preview in a new row **URL:** \ **Category:** Graylog Central (peer support)\ **Tags:** access-specific-log-\ **Created:** [June 21, 2023, 12:38pm UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248 "2023-06-21T12:38:26Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![giuseppe.terrasi](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@giuseppe.terrasi](https://community.graylog.org/u/giuseppe.terrasi)\ **Post date:** [June 21, 2023, 12:38pm UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/1 "2023-06-21T12:38:26Z")
The search result message preview is not working when some messages are received and this error is displayed: While rendering this widget, the following error occurred: NotFoundError: Failed to execute ‘removeChild’ on ‘Node’: The node to be removed is not a child of this node. If I disable the message preview the plugin works fine. **Environment:** - OS Information: Ubuntu Server 22.04.2 LTS - Package Version: graylog-server 5.1.2-1 This is something just reported here [While rendering this widget, the following error occurred: NotFoundError: Failed to execute ‘removeChild’ on ‘Node’: The node to be removed is not a child of this node - Graylog Central (peer support) - Graylog Community](https://community.graylog.org/t/while-rendering-this-widget-the-following-error-occurred-notfounderror-failed-to-execute-removechild-on-node-the-node-to-be-removed-is-not-a-child-of-this-node/17098) but it seems that it is not resolved. ---
**Author:** ![patrickmann](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/patrickmann/32/9091_2.png) [@patrickmann](https://community.graylog.org/u/patrickmann)\ **Post date:** [June 22, 2023, 9:28am UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/2 "2023-06-22T09:28:52Z")
The topic you linked to is really old - from version 3.3. The error message is a pretty generic React error, so I doubt this is the same thing. > If I disable the message preview the plugin works fine What plugin are you referring to? ---
**Author:** ![giuseppe.terrasi](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@giuseppe.terrasi](https://community.graylog.org/u/giuseppe.terrasi)\ **Post date:** [June 22, 2023, 9:43am UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/3 "2023-06-22T09:43:48Z")
Hi patrickmann, yeah I know, it is really old but the resulting problem is exactly the same. I’m referring to the “All messages” plugin and this is the option: ![image](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/f/fe4ddb7925e6d8277cc5e888e2efec17ae15511c.png) ---
**Author:** ![patrickmann](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/patrickmann/32/9091_2.png) [@patrickmann](https://community.graylog.org/u/patrickmann)\ **Post date:** [June 22, 2023, 12:13pm UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/4 "2023-06-22T12:13:54Z")
We call dashboard components widgets; plugins are functional extensions to Graylog. It must be something local to your setup since everybody uses message preview and we haven’t heard it’s broken from anybody else. Is there any further information visible in the browser console? Try reducing the set of displayed fields to just one. Does that change anything? ---
**Author:** ![giuseppe.terrasi](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@giuseppe.terrasi](https://community.graylog.org/u/giuseppe.terrasi)\ **Post date:** [June 22, 2023, 12:48pm UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/5 "2023-06-22T12:48:28Z")
I named it “widget” in my previous post just because it is the error reported by your platform. Anyway, I noticed that this happens with some messages and this is what is present in the console: ![image](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/e/e52a411559a20395d586304ce3bdf42a6da745cf.png) As I described, if I remove the “Show message in new row” option it works but obviously I don’t have the preview. P.s. telling “We haven’t heard it’s broken from anybody else” is not productive for anybody. Error handling is your responsibility, not the customers. Also, it is an out-of-the-box installation with one input, one index and one stream, so no custom implementations could cause this error. Finally, if it is something related to a message or something that it is not expected, the platform should give me this information. Thanks. ---
**Author:** ![patrickmann](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/patrickmann/32/9091_2.png) [@patrickmann](https://community.graylog.org/u/patrickmann)\ **Post date:** [June 23, 2023, 6:19am UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/6 "2023-06-23T06:19:18Z")
@giuseppe.terrasi My comment about this being the first report was just that. We certainly take any bug report seriously. My point is: there is something about your environment that is fairly unique and I would like to pinpoint that. Which browser are you running? If Chrome, does the error occur after disabling extensions? In particular, do you use a translation extension? ---
**Author:** ![giuseppe.terrasi](https://avatars.discourse-cdn.com/v4/letter/g/839c29/32.png) [@giuseppe.terrasi](https://community.graylog.org/u/giuseppe.terrasi)\ **Post date:** [June 23, 2023, 7:46am UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/7 "2023-06-23T07:46:34Z")
This problem was present with Chrome and Edge and seems that it is something related to the 3cx extension. When I disabled it and enabled all the others the problem disappeared. I noticed that this extension tries to convert any number that can be represented as a phone number into a clickable element to start a call. Maybe, when a message contains some of these numbers, this conversion fails and breaks the DOM constructed by the widget causing the error. ---
**Author:** ![patrickmann](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/patrickmann/32/9091_2.png) [@patrickmann](https://community.graylog.org/u/patrickmann)\ **Post date:** [June 23, 2023, 8:14am UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/8 "2023-06-23T08:14:09Z")
Great - that is good to know. I will followup with frontend engineers and see if there is anything we can do to be more robust in the face of such extensions. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [July 7, 2023, 8:14am UTC](https://community.graylog.org/t/an-error-occurred-while-rendering-message-preview-in-a-new-row/29248/9 "2023-07-07T08:14:27Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.