Configuration issue? gitea connectivity to Gitea

[RonarPS]

Hello,

i'd like to use the Issue Tracking from Gitea, and i've seen that there is a Gitea integration in gatus für that.

in my yml config i do hvae the following lines:

alerting:
gitea:
repository-url: "https://mysite/repo"
token: "generated gitea token"

in the endpoint section i do have the following:

• name: Gateway
  group: Core
  url: "icmp://192.168.1.1"
  conditions:
  • "[CONNECTED] == true"
    alerts:
  • type: gitea
    failure-threshold: 2
    success-threshold: 3
    description: "healthcheck failed"
    send-on-resolved: true

in the log i'm seeing the following message:

gatus_1 | 2025/09/25 19:27:50 [watchdog.handleAlertsToTrigger] Not sending alert of type=gitea endpoint with key=core-gateway despite being TRIGGERED, because the provider wasn't configured properly

Does anybody have an idea, what i'm doing wrong?

Thanks a lot for any hint.

[TwiN]

Look in the logs for a line with [config.validateAlertingConfig] when you start the application.

It should tell you why the validation failed.
Here's an example:

2025/09/25 16:34:11 [config.validateAlertingConfig] Ignoring provider=discord due to error=webhook-url not set
2025/09/25 16:34:11 [config.validateAlertingConfig] configuredProviders=[]; ignoredProviders=[aws-ses custom datadog discord email github gitlab gitea googlechat gotify homeassistant ifttt ilert incident-io jetbrainsspace line matrix mattermost messagebird newrelic ntfy opsgenie pagerduty plivo pushover rocketchat sendgrid signal signl4 slack splunk squadcast teams teams-workflows telegram twilio vonage webex zapier zulip]

[RonarPS]

Hi

GREAT! Thanks for the input!
i forgot the user scope for the application to set!

gatus_1 | 2025/09/29 09:10:49 [config.validateAlertingConfig] Ignoring provider=gitea due to error=token does not have at least one of required scope(s), required=[read:user], token scope=write:issue