Milionarz wrócił do domu bez zapowiedzi… i zamarł, widząc, co służąca robiła jego dziecku.

Milionarz wrócił do domu bez zapowiedzi i zamarł, widząc, co pokojówka robiła z jego synem.
Ostre dźwięki jego butów odbijały się od wypolerowanego marmuru w holu, niosąc się echem po całym domu. Leonard przyjechał wcześniej niż planował. Miał 37 lat wysoki, elegancki, zawsze nienagannie ubrany mężczyzna. Tego dnia miał na sobie śnieżnobiałą koszulę i błękitny krawat, który podkreślał blask jego oczu. Biznesmen przyzwyczajony do kontroli, do układów zawieranych w szklanych biurowcach, do nerwowych spotkań w Dubaju.
Ale tego dnia nie chciał kontraktów, luksusów ani pustych słów. Pragnął czegoś prawdziwego, czegoś ciepłego. Jego serce ciągnęło go do domu, by mógł poczuć jego rytm bez napięcia, które zawsze wzbudzała jego obecność. Chciał zobaczyć swojego syna, małego Szymona, ośmiomiesięcznego chłopczyka o miękkich loczkach i bezzębnymTitle: Problem with proxy configuration
username_0: Hello,
I’m sorry for opening an issue but I’m stuck with the proxy configuration and I don’t know what to do anymore.
I’m behind a corporate proxy (I can’t modify it) and I can’t get it to work.
Here is my configuration:
„`yml
version: '3.4′
services:
reverse-proxy:
image: traefik:v2.2
command:
– –api.insecure=true
– –providers.docker=true
– –providers.docker.exposedbydefault=false
– –entrypoints.web.address=:80
– –entrypoints.websecure.address=:443
– –log.level=DEBUG
ports:
– „80:80”
– „443:443”
– „8080:8080”
volumes:
– /var/run/docker.sock:/var/run/docker.sock:ro
labels:
– „traefik.enable=true”
– „traefik.http.routers.api.rule=Host(`traefik.localhost`)”
– „traefik.http.routers.api.service=api@internal”
environment:
– HTTP_PROXY=http://user:password@proxy:8080
– HTTPS_PROXY=http://user:password@proxy:8080
– http_proxy=http://user:password@proxy:8080
– https_proxy=http://user:password@proxy:8080
– NO_PROXY=localhost,127.0.0.1
– no_proxy=localhost,127.0.0.1
„`
I read the documentation and I think I’m doing it right, but when I check the logs I still have:
„`
reverse-proxy_1 | time=”2020-05-19T13:55:26Z” level=error msg=”Unable to obtain ACME certificate for domains \”traefik.localhost\”: unable to generate a certificate for the domains [traefik.localhost]: error: one or more domains had a problem:\n[traefik.localhost] acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:connection :: Fetching http://traefik.localhost/.well-known/acme-challenge/2h0D9T1VJ1G5zQ6L8Fck5oJ8z5DrYh22Pkto4O8bqLo: Error getting validation data, url: http://traefik.localhost/.well-known/acme-challenge/2h0D9T1VJ1G5zQ6L8Fck5oJ8z5DrYh22Pkto4O8bqLo\n” providerName=letsencrypt.acme routerName=api@docker rule=”Host(`traefik.localhost`)”
„`
Do you have any idea on what’s going wrong?
Thanks
username_1: Hello @username_0,
Thanks for your interest in the project.
Just to understand, the proxy is blocking your call to Let’s Encrypt API, is that correct?
Actually, from the error message it seems to be more related to the Let’s Encrypt challenge that is not working because it can’t reach your local machine. Your proxy is not involved in this error.
What happens when you try to access `http://traefik.localhost/.well-known/acme-challenge/2h0D9T1VJ1G5zQ6L8Fck5oJ8z5DrYh22Pkto4O8bqLo` from the machine that runs Docker?
Also, I don’t really understand why you try to get a certificate for `traefik.localhost` since it’s a local domain. Maybe you should use the `tls.insecureSkipVerify` option or generate self-signed certificates for local domains.
To help you better, it would be great if you could join the [Traefik community Slack](https://traefik.herokuapp.com/), as we try to keep the GitHub issues for confirmed bugs or feature requests.
Thanks!
username_0: Thanks for your answer.
I’m trying to use traefik with letsencrypt to test an application before deploying it to my company’s servers. It is working fine when I’m home but not at work because of the proxy.
I have other services (for example a Whoami container) that have the same problem when I try to reach them from my browser. They are correctly registered in traefik (I can see them in the dashboard) but I get a „Gateway timeout” when I try to reach them.
I thought the proxy was the problem here since it’s working without it.
username_1: `Gateway timeout` usually means that the Traefik cannot reach your services.
Just to understand, is your proxy blocking the communication between containers?
If you cannot join the Slack, it will be a lot harder for us to help you, as we don’t have enough information here to understand your problem.
username_0: I think so, I can’t ping from one container to another.
I’ll try to join Slack later, thanks for your help.
username_2: Hi! I’m Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn’t look like a bug.
To confirm this, please join our [Community Forum](https://community.containo.us/) and reach out to us on the [Traefik section](https://community.containo.us/c/traefik).
In case I’m wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check [Traefik’s documentation](https://docs.traefik.io/).