# Unable to modify tags in one remote tag provider, Others working fine

**URL:** <https://forum.inductiveautomation.com/t/unable-to-modify-tags-in-one-remote-tag-provider-others-working-fine/113164>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [January 8, 2026, 8:17pm UTC](https://forum.inductiveautomation.com/t/unable-to-modify-tags-in-one-remote-tag-provider-others-working-fine/113164 "2026-01-08T20:17:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![SWoollett](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SWoollett](https://forum.inductiveautomation.com/u/SWoollett)\
**Post date:** [January 8, 2026, 8:17pm UTC](https://forum.inductiveautomation.com/t/unable-to-modify-tags-in-one-remote-tag-provider-others-working-fine/113164/1 "2026-01-08T20:17:26Z")

</div>

Hello,

We have a hub and spoke architecture, one frontend gateway paired with several backend gateways which handle all the tags and coms to various plant areas.

I have recently configured a new backend gateway which is replacing an existing gateway.  
With the new gateway I am unable to modify/add any tags to the tag provider from the central frontend. All other backend gateways are functioning normally.

When connected directly to the backend gateway (with the same AD credentials) it functions normally.

I’ve compared the existing gateway and the new gateway and the configurations are identical.

Any pointer as to what might be causing this?

Cheers

S

---

<div class="post-metadata">

**Author:** ![mgross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mgross/32/3311_2.png) [@mgross](https://forum.inductiveautomation.com/u/mgross)\
**Post date:** [January 8, 2026, 9:47pm UTC](https://forum.inductiveautomation.com/t/unable-to-modify-tags-in-one-remote-tag-provider-others-working-fine/113164/2 "2026-01-08T21:47:09Z")

</div>

It might be security settings on your frontend gateway, specifically the Security Zones. Security zone identifiers can filter on IP addresses, host names, gateway names, and some other things. Your old backend gateway might have qualified for a required zone based on its host name or IP address, but your new one might not. You can also use the `Security.SecurityZones` and the `Security.SecurityZones.Zone` loggers on the central gateway to troubleshoot the security zones.

---

<div class="post-metadata">

**Author:** ![SWoollett](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SWoollett](https://forum.inductiveautomation.com/u/SWoollett)\
**Post date:** [January 11, 2026, 11:50pm UTC](https://forum.inductiveautomation.com/t/unable-to-modify-tags-in-one-remote-tag-provider-others-working-fine/113164/3 "2026-01-11T23:50:37Z")

</div>

There are no security zones configured.

Configuring the tag providers Tag Editing Permission to blank still results in the same behavior.

Interestingly looking in the project audit log shows my attempt to modify the tag provider with the STATUS\_CODE -2147352576 (HEX 80020000)

I found [Common OPC UA Error Codes - OPC Expert](https://opcexpert.com/support/common-opc-ua-error-codes/) which I’m not to sure what to do with this information now

| Name | Hexadecimal | Decimal | Description |
| --- | --- | --- | --- |
| BadInternalError | 0x80020000 | 2147614720 | An internal error occurred as a result of a programming or configuration error |

| |
| --- |

---

<div class="post-metadata">

**Author:** ![SWoollett](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SWoollett](https://forum.inductiveautomation.com/u/SWoollett)\
**Post date:** [January 12, 2026, 1:05am UTC](https://forum.inductiveautomation.com/t/unable-to-modify-tags-in-one-remote-tag-provider-others-working-fine/113164/4 "2026-01-12T01:05:02Z")

</div>

Found the issue

The Service Security wasn’t configured.

Specifically enabling ‘Trust Remote Security levels’ and setting ‘Default Provider Access Level’ to ‘Read Write Edit’