You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps:
disable tls in uptrace.yml
docker compose up -d
On the first login, update 'My Organization' name to something else. The string 'My Organization' in the left sidebar is not updated until the refresh. 'My Project' is updated correctly.
docker logs docker-uptrace-1 shows that uptrace is still trying to use the https endpoint
time=2025-06-10T11:45:05.324Z level=INFO msg="traces export: Post \"https://localhost:443/v1/traces\": http: server gave HTTP response to HTTPS client"
time=2025-06-10T11:45:15.320Z level=INFO msg="Post \"https://localhost:443/v1/logs\": http: server gave HTTP response to HTTPS client"
time=2025-06-10T11:45:15.325Z level=INFO msg="traces export: Post \"https://localhost:443/v1/traces\": http: server gave HTTP response to HTTPS client"
time=2025-06-10T11:45:20.321Z level=INFO msg="failed to upload metrics: Post \"https://localhost:443/v1/metrics\": http: server gave HTTP response to HTTPS client"
Data Retention UI shows 28 days, but ttl_delete in uptrace.yml are 14 days.
The text was updated successfully, but these errors were encountered:
On the first login, update 'My Organization' name to something else. The string 'My Organization' in the left sidebar is not updated until the refresh. 'My Project' is updated correctly.
Could you provide a screenshot? I am not sure I understand what you mean.
shows that uptrace is still trying to use the https endpoint
How have you configured uptrace_go.dsn option?
Data Retention UI shows 28 days, but ttl_delete in uptrace.yml are 14 days.
Steps:
disable tls in uptrace.yml
docker compose up -d
On the first login, update 'My Organization' name to something else. The string 'My Organization' in the left sidebar is not updated until the refresh. 'My Project' is updated correctly.
docker logs docker-uptrace-1
shows that uptrace is still trying to use the https endpointThe text was updated successfully, but these errors were encountered: