Sentry cannot receive any error on fresh install

Hi,
I cloned onpremise lastest version 23.4. Everything seem work but sentry cannot receive any error.
I tested on client success but sentry don’t show new issue.
image

Log running:

I used sentry-cli for test but sentry don’t receive the issue.

sentry-cli send-event -m ‘A test event’ --log-level=debug
DEBUG 2021-03-17 14:27:25.053566434 +07:00 sentry-cli version: 1.61.0, platform: “linux”, architecture: “x86_64”
INFO 2021-03-17 14:27:25.053718655 +07:00 sentry-cli was invoked with the following command line: “/usr/local/lib/node_modules/@sentry/cli/sentry-cli” “send-event” “-m” “A test event” “–log-level=debug”
DEBUG 2021-03-17 14:27:25.054452477 +07:00 client close; request transport to shut down (from sentry)
DEBUG 2021-03-17 14:27:25.054456544 +07:00 spawning curl transport (from sentry)
DEBUG 2021-03-17 14:27:25.054499802 +07:00 shutting down http transport (from sentry)
DEBUG 2021-03-17 14:27:25.055157833 +07:00 curl: > POST /api/1/store/ HTTP/1.1
Host: 127.0.0.1:9000
Accept: /
X-Sentry-Auth: Sentry sentry_key=17775b1f3b634a7c9e31c0eb46a4c1b1, sentry_version=7, sentry_timestamp=1615966045.054729, sentry_client=sentry-cli/x86_64
Content-Type: application/json
Content-Length: 2909 (from sentry)
DEBUG 2021-03-17 14:27:25.055215637 +07:00 curl: {“event_id”:“ef9ba33cedee4e5391bd0d1c3999eb5f”,“logentry”:{“message”:“A test event”},“platform”:“native”,“timestamp”:1615966045.053744,“server_name”:“test”,“environment”:“release”,“user”:{“ip_address”:“{{auto}}”,“username”:“root”},“extra”:{“environ”:{“DBUS_SESSION_BUS_ADDRESS”:“unix:path=/run/user/1014/bus”,“HOME”:“/root”,“LANG”:“C.UTF-8”,“LESSCLOSE”:“/usr/bin/lesspipe %s %s”,“LESSOPEN”:“| /usr/bin/lesspipe %s”,“LOCAL_BUILD_STATUS”:“false”,“LOGNAME”:“root”,“LS_COLORS”:“rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arc=01;31:.arj=01;31:.taz=01;31:.lha=01;31:.lz4=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.tzo=01;31:.t7z=01;31:.zip=01;31:.z=01;31:.Z=01;31:.dz=01;31:.gz=01;31:.lrz=01;31:.lz=01;31:.lzo=01;31:.xz=01;31:.zst=01;31:.tzst=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.alz=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.cab=01;31:.wim=01;31:.swm=01;31:.dwm=01;31:.esd=01;31:.jpg=01;35:.jpeg=01;35:.mjpg=01;35:.mjpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.m4a=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.oga=00;36:.opus=00;36:.spx=00;36:.xspf=00;36:”,“MAIL”:“/var/mail/root”,“OLDPWD”:“/opt/sentry/onpremise”,“PATH”:“/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin”,“PWD”:“/usr/local/lib/node_modules/@sentry/cli”,“SENTRY_DSN”:“http://17775b1f3b634a7c9e31c0eb46a4c1b1@127.0.0.1:9000/1",“SHELL”:“/bin/bash”,“SHLVL”:“2”,“TERM”:“xterm”,“USER”:“root”,“XDG_DATA_DIRS”:“/usr/local/share:/usr/share:/var/lib/snapd/desktop”,“XDG_RUNTIME_DIR”:“/run/user/1014”,“XDG_SESSION_ID”:“305442”,“_”:“/usr/local/bin/sentry-cli”}},“sdk”:{“name”:“sentry-cli”,“version”:"1.61.0”}} (from sentry)
DEBUG 2021-03-17 14:27:25.057306547 +07:00 curl: < HTTP/1.1 200 OK (from sentry)
DEBUG 2021-03-17 14:27:25.057331581 +07:00 curl: < Server: nginx (from sentry)
DEBUG 2021-03-17 14:27:25.057340054 +07:00 curl: < Date: Wed, 17 Mar 2021 07:27:25 GMT (from sentry)
DEBUG 2021-03-17 14:27:25.057348497 +07:00 curl: < Content-Type: application/json (from sentry)
DEBUG 2021-03-17 14:27:25.057356628 +07:00 curl: < Content-Length: 41 (from sentry)
DEBUG 2021-03-17 14:27:25.057364651 +07:00 curl: < Connection: keep-alive (from sentry)
DEBUG 2021-03-17 14:27:25.057372035 +07:00 curl: < access-control-expose-headers: x-sentry-error, x-sentry-rate-limits, retry-after (from sentry)
DEBUG 2021-03-17 14:27:25.057396287 +07:00 curl: < vary: Origin (from sentry)
DEBUG 2021-03-17 14:27:25.057412591 +07:00 curl: < (from sentry)
DEBUG 2021-03-17 14:27:25.057750163 +07:00 dropping http transport (from sentry)
ef9ba33c-edee-4e53-91bd-0d1c3999eb5f

relay_1                                     | 2021-03-17T04:25:34Z [relay_server::actors::upstream] ERROR: authentication encountered error: could not send request to upstream
relay_1                                     |   caused by: could not send request using reqwest
relay_1                                     |   caused by: error sending request for url (http://web:9000/api/0/relays/register/challenge/): error trying to connect: dns error: no record found for name: web.google.internal. type: AAAA class: IN
relay_1                                     | 2021-03-17T04:25:48Z [relay_server::actors::upstream] WARN: Network outage, scheduling another check in 60s

This portion explains it: relay cannot talk to the web backend. Could your system have some custom DNS interfering with Docker Compose’s automatic internal DNS?

I sent event through port web:9000, dont sent through relay port 3000.
I used “SENTRY_DSN”:http://17775b1f3b634a7c9e31c0eb46a4c1b1@127.0.0.1:9000/1

I compared with running one.
I see docker haven’t container sentry_onpremise_web_run_9506
I don’t know the new one don’t have this container.

Hi, we are investigating the same issue on another thread: Relay cannot connect to web:9000 selft hosting on Google Cloud - #23 by codydietrich

Would you mind continuing over there? Closing this one in favor of the other thread.