Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant acces storeweb in 0.20 #4139

Closed
skpenpen opened this issue May 3, 2021 · 4 comments
Closed

Cant acces storeweb in 0.20 #4139

skpenpen opened this issue May 3, 2021 · 4 comments

Comments

@skpenpen
Copy link

skpenpen commented May 3, 2021

Thanos, Prometheus and Golang version used:

Thanos : 0.20.0

Object Storage Provider: filesystem

What happened:

Trying to expose storeweb behind reverse proxy, working in 0.19, not in 0.20

What you expected to happen:

Working http exposition

How to reproduce it (as minimally and precisely as possible):

storeweb:
    image:  thanosio/thanos:v0.20.0
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: 3
    deploy:
      replicas : 1
      labels:
        - com.df.notify=true
        - com.df.serviceDomain=store
        - com.df.port=10902
    environment:
      - SERVICE_NAME=thanos-storeweb
    command:
        - tools
        - bucket
        - web
        - --objstore.config-file=/thanos/storage.yml
        #- --refresh=5m
    volumes:
      - /data/monitoring/prometheus:/prometheus
      - /data/monitoring/thanos:/thanos
    networks:
      default:
      monitoring:
      proxy:    

Full logs to relevant components:

level=error ts=2021-05-03T07:55:24.087004883Z caller=http.go:48 protocol=http http.component=server msg="failed to parse host port for http log decision" err="address store.dc1.local: missing port in address"

Anything else we need to know:

Docker swarm, with docker flow reverse proxy

@skpenpen
Copy link
Author

skpenpen commented May 3, 2021

Hum, same problem than #4128 since i can access in 0.20 with "store.dc1.local/new/blocks" url, still the error in logs

@wiardvanrij
Copy link
Member

It seems a bit more related to #4041 - I'm actually not sure if there is a bug, or that there is some configuration missing.

@stale
Copy link

stale bot commented Jul 8, 2021

Hello 👋 Looks like there was no activity on this issue for the last two months.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity in the next two weeks, this issue will be closed (we can always reopen an issue if we need!). Alternatively, use remind command if you wish to be reminded at some point in future.

@stale stale bot added the stale label Jul 8, 2021
@stale
Copy link

stale bot commented Jul 22, 2021

Closing for now as promised, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants