Skip to content

Commit 4f30152

Browse files
defguard-communitygitbook-bot
authored andcommitted
GITBOOK-346: change request with no subject merged in GitBook
1 parent dfbd6be commit 4f30152

1 file changed

Lines changed: 10 additions & 4 deletions

File tree

admin-and-features/troubleshooting/README.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
icon: comment-question
32
description: Here are some common issues / problems that are frequently encountered.
3+
icon: comment-question
44
---
55

66
# Troubleshooting Guide
@@ -18,7 +18,7 @@ Common problems may be:
1818
1. proxy / enrollment isn't working
1919
2. DEFGUARD\_ENROLLMENT\_URL is set incorrectly in core - if set incorrectly the client will try to connect to default URL which is "http://localhost:8080" and MFA will not work.
2020

21-
## Click on "Use authenticator app" in client and nothing happens
21+
## Nothing happens after clicking on "Use authenticator app" in client
2222

2323
See the "[Desktop client real-time/auto sync doesn't work](./#desktop-client-real-time-auto-sync-doesnt-work)" answer.
2424

@@ -57,15 +57,21 @@ If you are having problems with TOTP codes form 2FA/MFA (when logging in to defg
5757

5858
Best would be to setup on the server NTP time synchronization.
5959

60-
## I get error: _h2 protocol error: http2 error: stream error received: not a result of an error_
60+
## I get the following error: There was a network error. Can't reach proxy
61+
62+
This error may happen when the client is unable to make a POST/GET request to your proxy web server. Make sure your proxy is accessible by the client, e.g. by making a GET request by hand or visiting your enrollment/proxy page from the same machine you are running the client on. 
63+
64+
In some rarer cases, your web server may not accept TLS versions lower than 1.3. Since the maximum version of TLS supported by the client is 1.2, it won't be able to connect to your web server, producing the mentioned error.
65+
66+
## I get the following error: _h2 protocol error: http2 error: stream error received: not a result of an error_
6167

6268
This error is common if you use a reverse-proxy for any of our components.
6369

6470
Every reverse proxy has a timeout for keeping the connection alive. You can increase the timeout value to see less errors, but they will eventually appear.
6571

6672
Ignore them, this is a normal behaviour.
6773

68-
## How to check if the VPN is working / my VPN is not working!
74+
## How to check if the VPN is working / my VPN is not working
6975

7076
If you have configured your defguard instance correctly, after connecting to the VPN you should be able to ping your VPN server, for example if you have the following setup:
7177

0 commit comments

Comments
 (0)