Thanks for the tip, however this client had completely removed the entire contents of the configuration directory. Is there anything else we can try--perhaps it is cached somewhere and Windows needs to be restarted? Logs indicate it doesn't even attempt SSL...
On Thursday, 15 June 2017 02:10:08 UTC-6, Cédric Krier wrote: > > On 2017-06-14 22:42, Mark Shane Hayden wrote: > > I am having a peculiar problem with the windows desktop client since > > upgrading our dev system to 4.4. > > > > I can connect fine with my Debian machine however my colleague cannot > > connect on his Windows machine. Upon further investigation it appears > that > > his machine immediately sends HTTP to the server upon connecting and the > > server is configured to reject unencrypted connections to port 8000 > > (returns HTTP 400 unless it is encrypted). I even tried making the > server > > send a 307 redirect to https but the Windows client ignores it. > > > > Is this a new bug? Something we overlooked on client setup for Windows? > Is > > there still no way to force the client to never attempt insecure > > connections? > > You have to clean the known_hosts configuration: > http://doc.tryton.org/4.4/tryton/doc/usage.html#configuration-file > > This is were the client keep track of which servers use SSL or not. > > -- > Cédric Krier - B2CK SPRL > Email/Jabber: [email protected] <javascript:> > Tel: +32 472 54 46 59 > Website: http://www.b2ck.com/ > -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/21ee7570-adcc-4ec4-95fe-fcab8d6f5b85%40googlegroups.com.
