# Getting help

If you have problems building or using OpenConnect, or other questions or comments, please send email to the mailing list described below. You don't need to be subscribed to the list; you only need to click on the email address below, and send a plain text (not HTML) mail.

A lot of people seem to post questions about OpenConnect on random web forums, where they are unlikely to get a quick or knowledgeable response. It's almost as if they don't want a coherent response, which is strange. Please, don't do that.

# GitLab

We have created an OpenConnect project on GitLab.

You can file issues there, which may be more effective than sending them in email. You can also submit merge requests.

In addition to allowing discussion of issues and code changes, OpenConnect is now also using GitLab CI for continuous integration, testing, and building of the software. For example, GitLab CI builds the the Windows installers for OpenConnect with each new commit.

# Mailing list

There is a mailing list at `openconnect-devel@lists.infradead.org`. The list does not accept HTML email, so please make sure you post as plain text only.

As mentioned above, you do not have to be subscribed to the list in order to post a question.

It's usually best to read the recent messages in the archive before posting a question that is likely to have been asked before.

If you do want to subscribe to the mailing list, you can do so from the Mailman admin page.

SECURITY WARNING:
If you are posting debugging output from openconnect to the mailing list, do not include a line which looks like this:
`Set-Cookie: webvpn=835278264@921600@1221512527@6B9EC24DEB2F59E242F75B424D42F223D0912984;PATH=/`
That HTTP cookie is all that's needed to grant access to the VPN session you just logged in to — it's almost as bad as giving your password away. Version 2.26 or later of OpenConnect will automatically filter this out of the debugging output for you.

For Juniper VPN, the equivalent is a `DSID` cookie, which is not yet filtered out of any output (the authentication support in Juniper is still very new). For Palo Alto Networks GlobalConnect, the equivalent is a URL-encoded `authcookie` parameter, which is also not filtered out of any output.

# Internet Relay Chat (IRC)

There is also an IRC channel `#openconnect` on the OFTC network. You can access it via the OFTC webchat if you don't have an IRC client.

Please note that the people who can help you may be busy, and may be in a different time zone to you, and often indeed in a different time zone from one day to the next. If nobody is answering you immediately, please be patient — state your problem or question concisely and completely, and remain on the channel. You may well find that by the time you look back again, even if it's the next day, you have an answer or a fix has been made.

If you simply look in, say "hello?" a few times in the middle of the night, and then disappear again, that's not a lot more useful than posting to a randomly-chosen web forum as discussed above.