-
-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatible with TunnelBear but needs additional configuration #1710
Comments
Hey @KazumaKun1, thank you for reporting on a compatibility. We keep a list of compatible software and user provided guides for improving compatibility in the wiki - please have a look there. If you have managed to establish compatibility with an application, please share your findings here. This will greatly help other users encountering the same issues. |
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
|
@KazumaKun1 thank you for contributing this information! |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions. If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord. |
Pre-Submit Checklist:
What worked?
TunnelBear have 3 VPN protocols:
There's also an "auto" option there
The only protocol that's stable is the WireGuard. If you're going to choose "Auto", make sure that TCP Override is off.
What did not work?
Debug Information:
The text was updated successfully, but these errors were encountered: