Relay is giving me errors when trying to simulate an error in sentry

On-Premise
#1

When Im trying to simulate a fail sentry does not log the error can someone help me this is what Im seeing in the relay logs.

[33;1mrelay_1 |e[0m 2021-01-26T07:08:31.166188137Z 2021-01-26T07:08:31Z [relay_server::actors::upstream] INFO: registering with upstream (http://x.x.x.x:9000/)
e[33;1mrelay_1 |e[0m 2021-01-26T07:08:31.169586818Z 2021-01-26T07:08:31Z [relay_server::actors::upstream] ERROR: authentication encountered error: upstream request returned error 503 Service Unavailable
e[33;1mrelay_1 |e[0m 2021-01-26T07:08:31.169608218Z caused by: no error details
e[33;1mrelay_1 |e[0m 2021-01-26T07:08:31.169611574Z 2021-01-26T07:08:31Z [relay_server::actors::upstream] DEBUG: scheduling authentication retry in 38 seconds

#2

Looks like your Sentry instance is down?

#3

image
image1536×510 28.3 KB

#4

Checked with the docker ps -a and the containers are up and can access the sentry url too
but the error keeps showing

{“log”:“2021-01-27T05:06:29Z [relay_server::actors::upstream] ERROR: authentication encountered error: upstream request returned error 503 Service Unavailable\n”,“stream”:“stderr”,“time”:“2021-01-27T05:06:29.797721789Z”}

#5

Had an issue with the firewall now after adding the rule the 503 did not appered any more now is showing the error below regarding authentication

{“log”:“2021-01-27T09:24:46Z [relay_server::actors::upstream] ERROR: authentication encountered error: upstream request returned error 403 Forbidden\n”,“stream”:“stderr”,“time”:“2021-01-27T09:24:46.164584928Z”}

My relay config are as below:

relay:
upstream: “http://10.64.93.21:9000/”
host: 0.0.0.0
port: 3000
logging:
level: DEBUG
processing:
enabled: true
kafka_config:
- {name: “bootstrap.servers”, value: “kafka:9092”}
- {name: “message.max.bytes”, value: 50000000} #50MB or bust
redis: redis://redis:6379
geoip_path: “/geoip/GeoLite2-City.mmdb”
http:
_client: “reqwest”

#6

This should just be web:9000. If you put the public IP there (public referring to any IP outside of the private docker compose network), Sentry would require extra authentication via keys which we do not setup in the onpremise installation.