Does anyone have any ideas on how to fix this?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Space on April 14, 2017, 01:22:05 AMSource and target sets as "*", I set source to "OpenVPN net" but nothing changed.
if you go to VPN -> OpenVPN -> Servers you see a network listed in column "Tunnel Network". Remember this network.
Then go to Firewall -> Rules - OPENVPN. There should be a rule to let the traffic pass from the OpenVPN network to the destinations you desire. Make sure that in the column "Source" the network from above is listed.
Quote from: bartjsmit on April 13, 2017, 12:57:34 PM
Make sure the source is set to your tunnel subnet or * as well.
Quote from: fabian on April 12, 2017, 06:50:59 PMI see rule for OpenVPN with destination value "*".
a missing pass rule in the firewall?
Quote from: bartjsmit on April 09, 2017, 06:56:24 PMI have this strings in logs:
Sorry, I was a bit cryptic. Check out VPN -> OpenVPN -> Log File and see if you can spot any errors there.
Apr 11 03:17:24 openvpn[64982]: 192.168.3.36:55542 TLS Error: TLS handshake failed
Apr 11 03:17:24 openvpn[64982]: 192.168.3.36:55542 TLS Error: TLS object -> incoming plaintext read error
Apr 11 03:17:24 openvpn[64982]: 192.168.3.36:55542 TLS_ERROR: BIO read tls_read_plaintext error
Apr 11 03:17:24 openvpn[64982]: 192.168.3.36:55542 OpenSSL: error:14089086:SSL routines:ssl3_get_client_certificate:certificate verify failed
Apr 11 03:17:24 openvpn[64982]: 192.168.3.36:55542 VERIFY ERROR: depth=0, error=unsupported certificate purpose: C=RU, ST=SPb, L=SPb, O=InfinityNet, emailAddress=admin@infinitynet, CN=Server Certificate for my OpenVPN
Quote from: bartjsmit on April 09, 2017, 12:42:46 PMNo errors, only certiicate verification or connection timeout.
What error messages and log entries do you see?
Quote from: djGrrr on February 18, 2017, 04:58:21 PMThank you, now it's work, sometimes, but sometimes not, it's very strange (may be is android MS RDP client is buggy). But it's better then was!
Looking at the port forward rules screenshot a bit closer, the problem is that you have the destination address set to "LAN Address" when it must be set to "WAN address"