[Bug] ERROR: Failed to extract ServerMetadata from context #795

@agarzon-orangerine commented on GitHub (Sep 17, 2024):

I see the same error, Im using docker image: headscale/headscale:0.23.0-rc.1 (latest at this moment)

My compose is quite straight forward:

services:
  headscale:
    image: headscale/headscale:0.23.0-rc.1
    restart: unless-stopped
    container_name: headscale
    environment:
      - TZ=America/Toronto
    volumes:
      - ./conf:/etc/headscale
      - headscale_data:/var/lib/headscale
    command: serve
    labels:
      - traefik.enable=true
      - traefik.http.routers.${COMPOSE_PROJECT_NAME}_headscale.rule=Host(`${DOMAIN}`)
      - traefik.http.routers.${COMPOSE_PROJECT_NAME}_headscale.tls=true
      - traefik.http.services.${COMPOSE_PROJECT_NAME}_headscale.loadbalancer.server.port=8080
      
volumes:
  headscale_data:

networks:
  default:
    external: true
    name: proxy

@agarzon-orangerine commented on GitHub (Sep 17, 2024): I see the same error, Im using docker image: headscale/headscale:0.23.0-rc.1 (latest at this moment) My compose is quite straight forward: ```yml services: headscale: image: headscale/headscale:0.23.0-rc.1 restart: unless-stopped container_name: headscale environment: - TZ=America/Toronto volumes: - ./conf:/etc/headscale - headscale_data:/var/lib/headscale command: serve labels: - traefik.enable=true - traefik.http.routers.${COMPOSE_PROJECT_NAME}_headscale.rule=Host(`${DOMAIN}`) - traefik.http.routers.${COMPOSE_PROJECT_NAME}_headscale.tls=true - traefik.http.services.${COMPOSE_PROJECT_NAME}_headscale.loadbalancer.server.port=8080 volumes: headscale_data: networks: default: external: true name: proxy ```

adam commented

@kradalby commented on GitHub (Sep 18, 2024):

This sounds proxy related, I found this from the upstream gRPC project we use: https://github.com/grpc-ecosystem/grpc-gateway/issues/2445

I've tested with my own server, putting it behind a nginx proxy I was unable to reproduce.

Please be mindful that we do not have the capacity to test headscale behind the X x Y x Z combinations of proxies and configuration, which is why it is not supported. You can manage, but your miles might vary.

We did a dependency update to that library, and that might be related, but the update of dependencies is more important than novel proxy configurations.

@kradalby commented on GitHub (Sep 18, 2024): This sounds proxy related, I found this from the upstream gRPC project we use: https://github.com/grpc-ecosystem/grpc-gateway/issues/2445 I've tested with my own server, putting it behind a nginx proxy I was unable to reproduce. Please be mindful that we do not have the capacity to test headscale behind the X x Y x Z combinations of proxies and configuration, which is _why it is not supported_. You can manage, but your miles might vary. We did a dependency update to that library, and that might be related, but the update of dependencies is more important than novel proxy configurations.

adam commented

@Typhon0 commented on GitHub (Sep 21, 2024):

Hi, I was experiencing the same problem with Traefik V2, and upgrading to Traefik V3 solved it.

- Headscale v0.23.0
- Traefik 3.4.1

@Typhon0 commented on GitHub (Sep 21, 2024): Hi, I was experiencing the same problem with Traefik V2, and upgrading to Traefik V3 solved it. ``` - Headscale v0.23.0 - Traefik 3.4.1 ```

adam commented

@kradalby commented on GitHub (Sep 22, 2024):

Sounds like this is out of our hands, but should be mentioned in an faq or common proxy issues.

@kradalby commented on GitHub (Sep 22, 2024): Sounds like this is out of our hands, but should be mentioned in an faq or common proxy issues.

adam commented

@davidhan888-code commented on GitHub (Sep 26, 2024):

Hi, I was experiencing the same problem with Traefik V2, and upgrading to Traefik V3 solved it.
- Headscale v0.23.0
- Traefik 3.4.1

Thanks for the hint.
I still get the same error. Besides it is 3.1.4 rather than 3.4.1

@davidhan888-code commented on GitHub (Sep 26, 2024): > Hi, I was experiencing the same problem with Traefik V2, and upgrading to Traefik V3 solved it. > > ``` > - Headscale v0.23.0 > - Traefik 3.4.1 > ``` Thanks for the hint. I still get the same error. Besides it is 3.1.4 rather than 3.4.1

adam commented

@appleimperio commented on GitHub (Sep 27, 2024):

I'm having the same issue with Nginx Proxy Manager and headscale 0.23.0

@appleimperio commented on GitHub (Sep 27, 2024): I'm having the same issue with Nginx Proxy Manager and headscale 0.23.0

adam commented

@skarpinis commented on GitHub (Sep 30, 2024):

yes same issue with NPM

@skarpinis commented on GitHub (Sep 30, 2024): yes same issue with NPM

adam commented

@appleimperio commented on GitHub (Sep 30, 2024):

In my case the problem was with the integration with a webui. I changed to headscale-admin and the error disappear.

@appleimperio commented on GitHub (Sep 30, 2024): In my case the problem was with the integration with a webui. I changed to headscale-admin and the error disappear.

adam commented

@kradalby commented on GitHub (Sep 30, 2024):

I would like to emphasis that we will not be taking any action to resolve this, the error seems to be as a result of us updating a dependency, in this case gRPC related. Since it is not an alternative to change it, nor to not update them, there is little we can or will attempt doing.

We often underline that we do not support proxies, one of the reasons is this, it seems particularly tricky to get gRPC working correctly. In addition, Tailscale's protocol does not always play nice with proxies either (as per https://github.com/juanfont/headscale/issues/1468).

I will probably close it a bit, but need to think about how to resurface it so we dont get new issues created about the same error.

@kradalby commented on GitHub (Sep 30, 2024): I would like to emphasis that we will not be taking any action to resolve this, the error seems to be as a result of us updating a dependency, in this case gRPC related. Since it is not an alternative to change it, nor to not update them, there is little we can or will attempt doing. We often underline that we do not support proxies, one of the reasons is this, it seems particularly tricky to get gRPC working correctly. In addition, Tailscale's protocol does not always play nice with proxies either (as per https://github.com/juanfont/headscale/issues/1468). I will probably close it a bit, but need to think about how to resurface it so we dont get new issues created about the same error.

adam commented

@skarpinis commented on GitHub (Sep 30, 2024):

I will ignore no another option

@skarpinis commented on GitHub (Sep 30, 2024): I will ignore no another option

adam commented

@reey commented on GitHub (Sep 30, 2024):

FYI: had the same issue with https://github.com/ifargle/headscale-webui and traefik, but no problems using: https://github.com/GoodiesHQ/headscale-admin together with traefik

@reey commented on GitHub (Sep 30, 2024): FYI: had the same issue with https://github.com/ifargle/headscale-webui and traefik, but no problems using: https://github.com/GoodiesHQ/headscale-admin together with traefik

adam commented

@dreem2001 commented on GitHub (Oct 10, 2024):

It can be caused enabled legacy API <23 in settings of Headscale-admin.

@dreem2001 commented on GitHub (Oct 10, 2024): It can be caused enabled legacy API <23 in settings of Headscale-admin.

adam commented

@appleimperio commented on GitHub (Oct 11, 2024):

@dreem2001 That was exactly my issue. I disable it and everything start working

@appleimperio commented on GitHub (Oct 11, 2024): @dreem2001 That was exactly my issue. I disable it and everything start working

adam commented

@github-actions[bot] commented on GitHub (Jan 10, 2025):

This issue is stale because it has been open for 90 days with no activity.

@github-actions[bot] commented on GitHub (Jan 10, 2025): This issue is stale because it has been open for 90 days with no activity.

adam commented