On Sat, May 02, 2015 at 10:52:31AM -0400, GuiPoM wrote:

Hi there,

> I have no clue why it is not working. So I took the computer from my office
> location and I did the test from another location, with a standard internet
> access: I have no issue at all.
>
> It means that only the network between the computer and the nginx server
> makes this error appears, it must have nothing to do with the computer.

I also do not know why it fails.

Perhaps gathering more information will help find the cause.

When it fails:

* what request is made?
* what response is received? (application error, network timeout,
something else)

When it works, and the same request is made:

* what response is received?

If you can arrange that you can make the failing request on demand,
then you will probably have a better chance of identifying the problem.

ERR_TUNNEL_CONNECTION_FAILED can be associated with accessing https
through a proxy server. Do you use a proxy server on the "failing"
connection attempt? Does that proxy server have anything useful in
its logs?

> I am still hoping to find some help here. I am pretty sure that the <host:
> "truc:4321", referrer: "https://truc:4321/jeedom/index.php?v=d&p=history">
> is causing this issue, but I have no idea if this is a configuration of the
> nginx server and if I can do something around that.

If it matters: what is the configuration of the nginx server?

f
--
Francis Daly francis@daoine.org

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx