After upgrading our sentry to 24.9.0 we are facing sentry.auth.system: Trying to use `SystemToken` from non-internal IP

### Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

### Steps to Reproduce

Hi Team,

We have upgraded our sentry self hosted recently to 24.9.0, we are facing below issue intermittently, once after the restarting the container **sentry-self-hosted-web-1** sentry came up,
Error logs

15:06:20 [WARNING] django.request: Unauthorized: /api/0/projects/cds/evolio-masterdata-service/files/dsyms/ (status_code=401 request=)
15:06:20 [WARNING] django.request: Unauthorized: /api/0/projects/cds/evolio-masterdata-service/files/dsyms/ (status_code=401 request=)
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP

Kindly help us with the solution to resolve the issue.

Thanks!

### Expected Result

it should work with any issue.

### Actual Result

Please find the error logs-
-----------------------------------------------------------
15:06:20 [WARNING] django.request: Unauthorized: /api/0/projects/cds/evolio-masterdata-service/files/dsyms/ (status_code=401 request=)
15:06:20 [WARNING] django.request: Unauthorized: /api/0/projects/cds/evolio-masterdata-service/files/dsyms/ (status_code=401 request=)
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP
15:06:20 [ERROR] sentry.auth.system: Trying to use `SystemToken` from non-internal IP

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

24.9.0

Start with the 24.9.0 self-hosted deployment and the logs from the sentry-self-hosted-web-1 container, then trace the SystemToken requests to determine why their source IP is treated as non-internal after a restart. Reproduce the intermittent 401 responses for the dsyms endpoint and confirm that the warning and error logs no longer appear.

Written by the indexing model from the issue text.