NoRouteError('Network unreachable') in PROXY setup #9852

Activity

1. anoadragon453 commented on Apr 20, 2021

   

   anoadragon453

   on Apr 20, 2021

   Member

   More actions

   You'll need to omit the http:// and https:// from HTTP_PROXY and HTTPS_PROXY respectively. This is indeed different from the typical definition of HTTP_PROXY and HTTPS_PROXY environment variables. Note that currently the connection from Synapse to the proxy uses HTTP, regardless of whether the request from the proxy to the destination will use TLS.

   #9119 does attempt to fix this, but you'll need to omit the protocol specifier until it lands. I'm closing this issue in favour of #9090.
2. anoadragon453

   closed this as completedon Apr 20, 2021
3. f1-outsourcing commented on Apr 20, 2021

   

   f1-outsourcing

   on Apr 20, 2021

   Last edited by f1-outsourcing

   Author

   More actions

   Hi Andrew @anoadragon453

   I have changed to

   export HTTP_PROXY=proxy.example.com:535
   export HTTPS_PROXY=proxy.example.com:535
   export NO_PROXY="localhost,.local,127.0.0.1"
   

   But I am still having this:

   synapse.http.federation.well_known_resolver - 286 - INFO - GET-18 - Error fetching https://matrix.org/.well-known/matrix/server: No route to host: 101: Network unreachable.

   (with the packages 1.31.0)

   I can't really make up from your comment if the use of a forward proxy should work currently or not?

   (Is there a patch available that I can use to try matrix, or should I just forget about trying to get this to work with the proxy?)
4. anoadragon453 commented on Apr 21, 2021

   

   anoadragon453

   on Apr 21, 2021

   Member

   More actions

   Aha, I believe I misunderstood the initial problem.

   Outbound federation requests, such as resolving well-known pages, do not currently go through the configured proxy. If you have firewalled outbound connections except for those towards the proxy, then federation will currently fail. Support for routing federation traffic through the http proxy is tracked at #8660, and there's currently a PR open to fix it at #9306.

   In the meantime, outbound connections directly from Synapse will need to be allowed for federation to function.