Bug 2084525 - VPN error: invalid connection type for SSTP connections
Summary: VPN error: invalid connection type for SSTP connections
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-nm
Version: 36
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-12 10:57 UTC by Iñaki Ucar
Modified: 2023-05-25 18:27 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-05-25 18:27:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Iñaki Ucar 2022-05-12 10:57:59 UTC
Description of problem:
Connection to SSTP VPNs fail with the following message:

> Necessary secrets for the VPN connection <connection> were not provided.

I get this in the journal:

> may 12 12:49:33 <host> NetworkManager[1523]: <warn>  [1652352573.3298] vpn[<hash>,<connection>]: plugin NeedSecrets request #1 failed: GDBus.Error:org.freedesktop.NetworkManager.VPN.Error.BadArguments: Invalid connection type.


Version-Release number of selected component (if applicable):
NetworkManager-1.36.4-1.fc36
NetworkManager-sstp-1.3.0-3.fc36


How reproducible:
Always


Steps to Reproduce:
1.Create a new SSTP VPN connection.
2.Try to connect.

Comment 1 Iñaki Ucar 2022-05-29 16:34:33 UTC
According to the network-manager-sstp maintainer [1], this is due to a missing setting in plasma-nm (I'm using KDE). Also, according to the discussion there, this is a workaround for the time being:

- Open up /etc/NetworkManager/VPN/(your-connection).connection
- Add a property "connection-type" and set it to "password" under the VPN settings

[1] https://gitlab.gnome.org/GNOME/network-manager-sstp/-/issues/50

Comment 2 Ben Cotton 2023-04-25 17:08:49 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 18:27:05 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.