# Why does ActiveGate return a 403 Forbidden error?

**URL:** <https://community.dynatrace.com/t/why-does-activegate-return-a-403-forbidden-error/42797>\
**Category:** Troubleshooting\
**Tags:** activegate, opentelemetry\
**Created:** [November 29, 2023, 1:10am UTC](https://community.dynatrace.com/t/why-does-activegate-return-a-403-forbidden-error/42797 "2023-11-29T01:10:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexander\_dt](https://avatars.discourse-cdn.com/v4/letter/a/5daacb/32.png) [@alexander\_dt](https://community.dynatrace.com/u/alexander_dt)\
**Post date:** [November 29, 2023, 1:10am UTC](https://community.dynatrace.com/t/why-does-activegate-return-a-403-forbidden-error/42797/1 "2023-11-29T01:10:00Z")

</div>

When you send OTLP requests to ActiveGate and receive a 403 error, this indicates that the provided token either expired or was not configured with the necessary permission scopes.

Verify that the token:

- Has the necessary permission scopes. For details, see&nbsp;[Authentication](https://docs.dynatrace.com/docs/extend-dynatrace/opentelemetry/getting-started/otlp-export#authentication-export-to-activegate).
- Is still within its validity period and did not expire.

If necessary, issue a new token and change your exporter configuration accordingly.
