Search found 1888 matches

Search found 1888 matches Page 1 of 189
by James
Sun Sep 15, 2019 4:06 pm
Forum: Viscosity Support (Mac Version)
Topic: No connection after update
Replies: 3
Views: 13

It's definitely a problem with the OpenVPN server's certificate. All OpenVPN clients released after the OpenSSL update (November 2018) will reject the server's certificate, not just Viscosity. Here's a post from 2018 with some more information at: https://www.sparklabs.com/forum/viewtopic.php?f=3&t=...
by James
Sun Sep 15, 2019 3:55 pm
Forum: Viscosity Support (Mac Version)
Topic: Use local DNS server for LAN and VPN provider's DNS server for WAN
Replies: 1
Views: 7

Hi donnie, It's possible to accomplish what you're after. Essentially you want a sort of "reverse" Split-DNS, where DNS lookups use the VPN connection by default except for the domain you specify, along with using that domain as a search domain so you can access hosts by a single name without needin...
by James
Sun Sep 15, 2019 1:48 pm
Forum: Viscosity Support (Mac Version)
Topic: Viscosity connection establishes slower than open vpn
Replies: 1
Views: 7

Hi rizjoj, I'd recommend seeing where exactly the delay lies: look at the OpenVPN log and look at the time between each line. I'd also recommend increasing the log verbosity to level 3 so you have a few more details. You can increase the log verbosity by adding the command "verb 3" (without the quot...
by James
Sun Sep 15, 2019 1:20 pm
Forum: Viscosity Support (Mac Version)
Topic: WOL not working.
Replies: 1
Views: 5

Hi DeeGee, A WoL request is a special low-level network packet. It requires that you be on the same subnet (i.e. IP range), or a router connected to the subnet configured to re-forward it if you're not. The easiest way to get it to work is to use a TAP/bridged connection instead of a TUN/routed one....
by James
Sun Sep 15, 2019 1:00 pm
Forum: Viscosity Support (Mac Version)
Topic: No connection after update
Replies: 3
Views: 13

Hi robbacki, Thanks for posting your log. The important line is: VERIFY ERROR: depth=0, error=format error in certificate's notAfter field This is indicating that the format of the expiry date (the notAfter field) embedded in the server's certificate is invalid. Old versions of OpenSSL inadvertently...
by James
Tue Sep 10, 2019 7:29 pm
Forum: Viscosity Support (Mac Version)
Topic: can´t connect via vpn with1.8b5 (1501)
Replies: 4
Views: 70

Hi Guma96,

Thanks for the additional information. We've just pushed out an updated beta version that should hopefully resolve this issue (version 1.8b6). Please give it a try and let us know if you still encounter any problems connecting.

Cheers,
James
by James
Mon Sep 09, 2019 6:16 pm
Forum: Viscosity Support (Mac Version)
Topic: can´t connect via vpn with1.8b5 (1501)
Replies: 4
Views: 70

Hi Guma96, Your log is indicating that a connection can't be established with the OpenVPN server; this likely it means the server is down, you're being blocked from connecting, or the server's configuration has been updated and you need to update your configuration details. As you appear to be using...
by James
Fri Aug 23, 2019 1:07 pm
Forum: Viscosity Support (Mac Version)
Topic: False incorrect username and password error
Replies: 1
Views: 134

Hi Angelo, Viscosity will display such an alert if the OpenVPN server sends an "AUTH_FAILED" message. More information about why the message is being sent may be available in the connection log (please see the link below), but you'll likely need to view the server's log (or ask your IT administrator...
by James
Wed Aug 21, 2019 4:27 pm
Forum: Viscosity Support (Mac Version)
Topic: Copied vpn connection not connecting
Replies: 1
Views: 108

Hi EAJ, If you are manually copying/moving files into place you'll need to quit and re-opened Viscosity to get it to see the changes. You may prefer to import the configuration into Viscosity, that way configuration data, files, permissions, etc. will all be correct. To do this open Viscosity's pref...
by James
Fri Aug 16, 2019 3:26 am
Forum: Viscosity Support (Mac Version)
Topic: Split DNS broken with macOS 10.14.6 update
Replies: 6
Views: 634

Thanks for posting those details. As far as I can tell your Split DNS setup is configured correctly. However based on your dscacheutil output I believe the "xxx-xxx-xx-shard-00-00-ipkmx.mongodb.net" domain might actually be a CNAME record (rather than an A record) to an ap-southeast-2.compute.amazon...
Search found 1888 matches Page 1 of 189