Traefik

问题 I've been fiddling with Traefik for a few hours and find it extremely interesting. However, I've ran into a problem that I can't seem to solve by myself. It's a very simple setup, just trying to test the HTTP to HTTPS redirection and my SSL certificates. I have the following docker-compose.yml version: '2' services: traefik: image: traefik:v1.3.7-alpine ports: - "80:80" - "443:443" - "8080:8080" volumes: - /var/run/docker.sock:/var/run/docker.sock:z - /opt/dockerapp/rocketchat/traefik/traefik

问题 I am deploying an angular app to a docker server using traefik to handle the reverse proxies. I am trying to get it to work via the equivalent of the bellow link: https://server.url.com/angular-app Using this link I am getting the following web console errors and a blank page. Loading failed for the <script> with source “https://server.url.com/runtime.33696abb3e1f13aa52cf.js”. angular-app:17:1 Loading failed for the <script> with source “https://server.url.com/polyfills.b8a0220c9c0a3ba034f8

问题 I want setup Traefik backend health check via Kubernetes annotation, but looks like Kubernetes Ingress does not support that functionality according to official documentation. Is any particular reason why Traefik does not support that functionality for Kubernetes Ingress? I'm wondering because Mesos support health checks for a backend. I know that in Kubernetes you can configure readiness/liveness probe for the pods, but I have leader/follower fashion service, so Traefik should route the

问题 I'm attempting to update from Traefik v1.2.3 to v1.3.6 on Kubernetes. I have my TLS certificates mounted inside of the pods from secrets. Under v1.2.3, everything works as expected. When I try to apply my v1.3.6 deployment (only change being the new docker image), the pods fail to start with the following message: time="2017-08-22T20:27:44Z" level=error msg="Error creating TLS config: tls: failed to find any PEM data in key input" time="2017-08-22T20:27:44Z" level=fatal msg="Error preparing

问题 I am using minikube for developing an application on Kubernetes and I am using Traefik as the ingress controller. I am able to connect and use my application services when I use the url of the host which I defined in the ingress ("streambridge.local") and I set up in the linux hosts ("/etc/hosts"). But when I use the exact same ip address that I used for the dns I am not able to connect to any of the services and I receive "404 page not found". I have to mention that I am using the IP address

问题 Some of my frontends aren't routed properly to backend. I do have 2 container: - portainer; - homeassistant; Portainer works properly but homeassistant is not routed properly to backend. my docker-compose: version: "3.6" services: portainer: image: portainer/portainer container_name: portainer domainname: ${DOMAINNAME} hostname: portainer volumes: - /var/run/docker.sock:/var/run/docker.sock - ${USERDIR}/dockerha/uavportainer/data:/data - ${USERDIR}/dockerha/shared:/shared environment: - TZ=$

问题 I am trying to configure Traefik for a WebSocket app, I just try with a simple WS app on docker: https://hub.docker.com/r/jmalloc/echo-server/ To test it I use Chrome SimpleWebSocketClient, so if I use the IP:Port of the app it works fine. If I add the Traefik DNS it fails, I just try with other WS server and clients and fails too, so it would be something of Traefik. I just try with Traefik versions: -v1.3.0/raclette -v1.2.3/morbier Those are my Traefik rules: [backends.ws-test-backend]

问题 I'm using traefik in docker-mode. It's retrieving most config (acme.domains, enabled, frontend-rules,...) from the docker containers. Currently all containers are reachable from the WWW (0.0.0.0). I'm wondering how to restrict the access to a single container to some dedicated ip-addresses. The docker labels of the private web-service would look like: labels: - "traefik.enable=true" - "traefik.backend='private container'" - "traefik.whitelistSourceRange=192.168.1.0/24" The whitelisted ip is

问题 I deploy traefik ingress controller pod and then two services, one of them a LoadBalancer type for reverse-proxy and the other a ClusterIP for dashboard. Also I create ingress for redirect all <elb-address>/dashboard to my traefik dashboard. but for some reason I get 404 error code when I trying to request my dashboard at aws-ip/dashboard That is the manifest yamls that I use to set up traefik --- apiVersion: v1 kind: ServiceAccount metadata: name: traefik-ingress-controller namespace: kube

问题 So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template. I want to enable the dashboard service while not creating an ingress for it (I set up OpenVPN to access the traefik dashboard only via VPN). Both dashboard-ingress.yaml and dashboard-service.yaml conditionally include the ingress or the respective service based on the same variable {{- if .Values.dashboard.enabled }}