Openconnect in NetworkManager not working for a user
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I've just upgraded to Kubuntu 18.04 (from 14.04, so almost fresh install), I've found a problem trying to connect to a VPN with network-manager. The configuration is very simple: just a server name (and then I have to input username and password). It works with command line:
sudo openconnect server.address
but when I try to connect from the network manager, I get this in /var/log/syslog
:
openconnect[6521]: Conectado a [server.ip]:443
openconnect[6521]: Negociación SSL con «[server.ip]»
openconnect[6521]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[6521]: Unknown certificate hash: pin-sha256:**************************************************.
openconnect[6521]: No se pudo calcular hash del certificado del servidor
NetworkManager[2677]: Falló al crear la conexión SSL
(sorry for the Spanish messages.) The problem line is Unknown certificate hash
, the line above seems to be just a warning, and after that it "cannot compute the server certificate hash" and connection fails.
I created a new user from sratch (my home directory comes from the previous installation), and here the VPN connection works:
openconnect[8533]: Conectado a [server.ip]:443
openconnect[8533]: Negociación SSL con «[server.ip]»
openconnect[8533]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[8533]: Conectó a HTTPS en [server.ip]
openconnect[8533]: Se obtuvo la respuesta CONNECT: HTTP/1.1 200 OK
openconnect[8533]: CSTP conectado. DPD 30, Keepalive 20
openconnect[8533]: Conectado como [server.ip], usando SSL
openconnect[8533]: Conexión DTLS establecida (usando GnuTLS). Ciphersuite (DTLS0.9)-(DHE-RSA-4294967237)-(AES-256-CBC)-(SHA1).
Same first 3 lines as before, but then the connection is successful and all is good. So I guess there must be something in my home directory that breaks it, but I cannot find it! I've grepped for the unknown pin-sha256, but nothing appears. And although the home directory is from the previous installation, the whole plasma configuration is new and I had to create the VPN connection.
How can I find/remove this faulty sha, or whatever it is?
network-manager kde openconnect
add a comment |
I've just upgraded to Kubuntu 18.04 (from 14.04, so almost fresh install), I've found a problem trying to connect to a VPN with network-manager. The configuration is very simple: just a server name (and then I have to input username and password). It works with command line:
sudo openconnect server.address
but when I try to connect from the network manager, I get this in /var/log/syslog
:
openconnect[6521]: Conectado a [server.ip]:443
openconnect[6521]: Negociación SSL con «[server.ip]»
openconnect[6521]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[6521]: Unknown certificate hash: pin-sha256:**************************************************.
openconnect[6521]: No se pudo calcular hash del certificado del servidor
NetworkManager[2677]: Falló al crear la conexión SSL
(sorry for the Spanish messages.) The problem line is Unknown certificate hash
, the line above seems to be just a warning, and after that it "cannot compute the server certificate hash" and connection fails.
I created a new user from sratch (my home directory comes from the previous installation), and here the VPN connection works:
openconnect[8533]: Conectado a [server.ip]:443
openconnect[8533]: Negociación SSL con «[server.ip]»
openconnect[8533]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[8533]: Conectó a HTTPS en [server.ip]
openconnect[8533]: Se obtuvo la respuesta CONNECT: HTTP/1.1 200 OK
openconnect[8533]: CSTP conectado. DPD 30, Keepalive 20
openconnect[8533]: Conectado como [server.ip], usando SSL
openconnect[8533]: Conexión DTLS establecida (usando GnuTLS). Ciphersuite (DTLS0.9)-(DHE-RSA-4294967237)-(AES-256-CBC)-(SHA1).
Same first 3 lines as before, but then the connection is successful and all is good. So I guess there must be something in my home directory that breaks it, but I cannot find it! I've grepped for the unknown pin-sha256, but nothing appears. And although the home directory is from the previous installation, the whole plasma configuration is new and I had to create the VPN connection.
How can I find/remove this faulty sha, or whatever it is?
network-manager kde openconnect
add a comment |
I've just upgraded to Kubuntu 18.04 (from 14.04, so almost fresh install), I've found a problem trying to connect to a VPN with network-manager. The configuration is very simple: just a server name (and then I have to input username and password). It works with command line:
sudo openconnect server.address
but when I try to connect from the network manager, I get this in /var/log/syslog
:
openconnect[6521]: Conectado a [server.ip]:443
openconnect[6521]: Negociación SSL con «[server.ip]»
openconnect[6521]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[6521]: Unknown certificate hash: pin-sha256:**************************************************.
openconnect[6521]: No se pudo calcular hash del certificado del servidor
NetworkManager[2677]: Falló al crear la conexión SSL
(sorry for the Spanish messages.) The problem line is Unknown certificate hash
, the line above seems to be just a warning, and after that it "cannot compute the server certificate hash" and connection fails.
I created a new user from sratch (my home directory comes from the previous installation), and here the VPN connection works:
openconnect[8533]: Conectado a [server.ip]:443
openconnect[8533]: Negociación SSL con «[server.ip]»
openconnect[8533]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[8533]: Conectó a HTTPS en [server.ip]
openconnect[8533]: Se obtuvo la respuesta CONNECT: HTTP/1.1 200 OK
openconnect[8533]: CSTP conectado. DPD 30, Keepalive 20
openconnect[8533]: Conectado como [server.ip], usando SSL
openconnect[8533]: Conexión DTLS establecida (usando GnuTLS). Ciphersuite (DTLS0.9)-(DHE-RSA-4294967237)-(AES-256-CBC)-(SHA1).
Same first 3 lines as before, but then the connection is successful and all is good. So I guess there must be something in my home directory that breaks it, but I cannot find it! I've grepped for the unknown pin-sha256, but nothing appears. And although the home directory is from the previous installation, the whole plasma configuration is new and I had to create the VPN connection.
How can I find/remove this faulty sha, or whatever it is?
network-manager kde openconnect
I've just upgraded to Kubuntu 18.04 (from 14.04, so almost fresh install), I've found a problem trying to connect to a VPN with network-manager. The configuration is very simple: just a server name (and then I have to input username and password). It works with command line:
sudo openconnect server.address
but when I try to connect from the network manager, I get this in /var/log/syslog
:
openconnect[6521]: Conectado a [server.ip]:443
openconnect[6521]: Negociación SSL con «[server.ip]»
openconnect[6521]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[6521]: Unknown certificate hash: pin-sha256:**************************************************.
openconnect[6521]: No se pudo calcular hash del certificado del servidor
NetworkManager[2677]: Falló al crear la conexión SSL
(sorry for the Spanish messages.) The problem line is Unknown certificate hash
, the line above seems to be just a warning, and after that it "cannot compute the server certificate hash" and connection fails.
I created a new user from sratch (my home directory comes from the previous installation), and here the VPN connection works:
openconnect[8533]: Conectado a [server.ip]:443
openconnect[8533]: Negociación SSL con «[server.ip]»
openconnect[8533]: La verificación del certificado del servidor falló: firmante no encontrado
openconnect[8533]: Conectó a HTTPS en [server.ip]
openconnect[8533]: Se obtuvo la respuesta CONNECT: HTTP/1.1 200 OK
openconnect[8533]: CSTP conectado. DPD 30, Keepalive 20
openconnect[8533]: Conectado como [server.ip], usando SSL
openconnect[8533]: Conexión DTLS establecida (usando GnuTLS). Ciphersuite (DTLS0.9)-(DHE-RSA-4294967237)-(AES-256-CBC)-(SHA1).
Same first 3 lines as before, but then the connection is successful and all is good. So I guess there must be something in my home directory that breaks it, but I cannot find it! I've grepped for the unknown pin-sha256, but nothing appears. And although the home directory is from the previous installation, the whole plasma configuration is new and I had to create the VPN connection.
How can I find/remove this faulty sha, or whatever it is?
network-manager kde openconnect
network-manager kde openconnect
asked 10 mins ago
JellbyJellby
17517
17517
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1139414%2fopenconnect-in-networkmanager-not-working-for-a-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1139414%2fopenconnect-in-networkmanager-not-working-for-a-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown