David Woodhouse <dwmw2@xxxxxxxxxxxxx> writes: >> Thanks, rather late, for this. Should that have been obvious from the >> doc somewhere I didn't find? > > I don't think so. I try to be quite good at documenting OpenConnect > itself, but documentation on the NetworkManager-openconnect interaction > has been somewhat lacking. Users *mostly* shouldn't have to care about > that. I'm glad it's not just me, thanks (rather late)! >> Then nmcli produces >> >> Connected to HTTPS on *** >> Got HTTP response: HTTP/1.1 502 Bad Gateway >> Unexpected 502 result from server >> Failed to obtain WebVPN cookie >> Error: openconnect failed with status 1 >> Connection successfully activated (D-Bus active path: >> /org/freedesktop/NetworkManager/ActiveConnection/18) >> >> Obviously I can take suggestions to investigate if it's useful. > > Hm, it does that and then connects successfully? That's interesting; > probably worth filing a bug with NetworkManager. It shouldn't be doing > that if it was *given* the secrets it needs. OK. For what it's worth, https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/436 _______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
