Uptime check failure

[ronaldorcampos]

Self-Hosted Version

25.10.0

CPU Architecture

x86_64

Docker Version

28.1.1

Docker Compose Version

v2.35.1

Machine Specification

• [x] My system meets the minimum system requirements of Sentry

Steps to Reproduce

Im trying to setup uptime checks for some of my internal DNS which resolves to 192.168.100.xxx ip range but im getting destination restricted.

I have UPTIME_CHECKER_ALLOW_INTERNAL_IPS enabled in my .env file

When doing curl, i can resolve to my DNS fine

Expected Result

Uptime check to succeed

Actual Result

12:13:24 [INFO] sentry.uptime.consumers.results_consumer: uptime.result_processor.false_num_missing_check (guid='4a6bdc9ae7ad5f70adaa8a7dca48e78a' subscription_id='5d5ada73c27f4a3c8c2f8f82127b5bfe' status='failure' status_reason={'type': 'dns_error', 'description': 'destination is restricted'} trace_id='4a6bdc9ae7ad5f70adaa8a7dca48e78a' span_id='a0f7c07df9b12e52' scheduled_check_time_ms=1763554404000 scheduled_check_time_us=1763554404000000 actual_check_time_ms=1763554404018 actual_check_time_us=1763554404018269 duration_ms=0 duration_us=194 request_info={'request_type': 'GET', 'http_status_code': None, 'url': 'http://internal-api-aws.cloudadminlocal.io/health', 'request_body_size_bytes': 0, 'response_body_size_bytes': 0, 'request_duration_us': 194, 'durations': {'dns_lookup': {'start_us': 1763554404018268, 'duration_us': 0}, 'tcp_connection': {'start_us': 1763554404018268, 'duration_us': 0}, 'tls_handshake': {'start_us': 1763554404018268, 'duration_us': 0}, 'time_to_first_byte': {'start_us': 1763554404018268, 'duration_us': 0}, 'send_request': {'start_us': 1763554404018268, 'duration_us': 0}, 'receive_response': {'start_us': 1763554404018268, 'duration_us': 0}}, 'certificate_info': None} request_info_list=[{'request_type': 'GET', 'http_status_code': None, 'url': 'http://internal-api-aws.cloudadminlocal.io/health', 'request_body_size_bytes': 0, 'response_body_size_bytes': 0, 'request_duration_us': 194, 'durations': {'dns_lookup': {'start_us': 1763554404018268, 'duration_us': 0}, 'tcp_connection': {'start_us': 1763554404018268, 'duration_us': 0}, 'tls_handshake': {'start_us': 1763554404018268, 'duration_us': 0}, 'time_to_first_byte': {'start_us': 1763554404018268, 'duration_us': 0}, 'send_request': {'start_us': 1763554404018268, 'duration_us': 0}, 'receive_response': {'start_us': 1763554404018268, 'duration_us': 0}}, 'certificate_info': None}] region='default')

Event ID

No response

[ronaldorcampos]

Will see if I can open a PR.

[aldy505]

I really discourage this. If you want it, you can create a docker-compose.override.yml file, and add:

services:
  uptime-checker:
    environment:
      UPTIME_CHECKER_ALLOW_INTERNAL_IPS: "true"

Then

docker compose up -d uptime-checker && docker compose restart uptime-checker

I will provide a documentation for this later.

[ronaldorcampos]

@aldy505 any specific reason? ok thanks.

[aldy505]

Putting it on your .env would pollute the file, you need to add inline documentation to know what it's for and which container should it attach to. It's also very prone to typos.

If you use docker-compose.override.yml, you can do so much more than that as seen on this config source code. Some other thing you can do is scaling containers without changing docker-compose.yml, so you can do git pull or git checkout <next version> easily, this is one example of it: https://develop.sentry.dev/self-hosted/tasks/#scaling-workers

[ronaldorcampos]

I see ok., thank you for the advice.

[getsantry[bot]]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀