On 09/17/2012 09:02 PM, Mark Hayden wrote: > What kind of magic is the client performing when it decides to use HTTPS > or HTTP?
As far as I know, the client tries to use HTTPS and if that fails it falls back to HTTP. The fingerprint (if any) is saved in the known_hosts file and can cause some trouble when experimenting (see below). > Why does the magic fail when the proxy-pass server is in the > way? Nginx is not the problem. We are using the same architecture you describe. > How can I force the Tryton client to NOT attempt insecure connections? As far as I know you can't. > But has anyone seen this kind of problem? Is there a special > trick to make proxy-pass work with SSL the way it does without it? Just a guess: Have you tried removing the corresponding line in ~/.config/tryton/2.4/known_hosts? When the fingerprint there does not match the server's, it looks like you cannot connect and no meaningful error is reported. Regards, Robin Baumgartner
signature.asc
Description: OpenPGP digital signature
