# Ошибка в логах, связанная с twitter\_login

**URL:** https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203
**Category:** Bug
**Created:** [10.Октябрь.2025 05:34:10 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203 "2025-10-10T05:34:10Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [24.Октябрь.2025 08:52:39 UTC](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203/8 "2025-10-24T08:52:39Z")

</div>

Ошибка исправлена в

> <https://github.com/discourse/discourse/pull/35593>
>
> This commit fixes a bug where we were using the twitter's oauth2
> endpoint to ch…eck if the \`twitter\_consumer\_key\` and \`twitter\_consumer\_secret\` has been configured
> correctly. However, the request returns a 403 response code because of a
> missing required param causing the problem check to fail.
> 
> Instead of fixing the request, the better thing to do is to ensure we do
> the same checks that the \`omniauth-oauth\` gem does so that we are
> actually validating the oauth flow.

---

_[View the full topic](https://meta.discourse.org/t/error-in-logs-related-to-twitter-login/385203)._
