Skip to content
Won't connect after updating to v1.7
Got a problem with Viscosity or need help? Ask here!
- Posts: 1
- Joined: Mon May 22, 2017 9:57 pm
Hi!
I just updated from 1.7 beta to 1.7. Now it refuses to connect and i get this:
2017-05-22 13:42:38: This copy of Viscosity is registered using a license that does not allow connections to one or more of the remote servers for this connection. Please contact your VPN Provider for further details.
2017-05-22 13:42:38: Viscosity Mac 1.7 (1392)
2017-05-22 13:42:38: Viscosity OpenVPN Engine Started
2017-05-22 13:42:38: Running on macOS 10.12.5
2017-05-22 13:42:38: ---------
2017-05-22 13:42:38: State changed to Connecting
2017-05-22 13:42:41: State changed to Disconnected
I have bought a license a few years back, never had any problems before now. What to do?
I just updated from 1.7 beta to 1.7. Now it refuses to connect and i get this:
2017-05-22 13:42:38: This copy of Viscosity is registered using a license that does not allow connections to one or more of the remote servers for this connection. Please contact your VPN Provider for further details.
2017-05-22 13:42:38: Viscosity Mac 1.7 (1392)
2017-05-22 13:42:38: Viscosity OpenVPN Engine Started
2017-05-22 13:42:38: Running on macOS 10.12.5
2017-05-22 13:42:38: ---------
2017-05-22 13:42:38: State changed to Connecting
2017-05-22 13:42:41: State changed to Disconnected
I have bought a license a few years back, never had any problems before now. What to do?
I have several VPNs all of which worked until I had the misfortune to install the mentioned update. After this I get
"This copy of Viscosity is registered using a license that does not allow connections to one or more of the remote servers for this connection. Please contact your VPN Provider for further details."
In Preferences/About I can see that the software is correctly displaying "Registered to:..."
"This copy of Viscosity is registered using a license that does not allow connections to one or more of the remote servers for this connection. Please contact your VPN Provider for further details."
In Preferences/About I can see that the software is correctly displaying "Registered to:..."
Hi ipreduser2 and fixone,
Please check for an update under the Preferences->General section. A new update should be available that resolves the problem.
Sadly there was a bug in the initial build (build number 1392) that was made available via automatic update. It was only available for around 10mins, however unfortunately a number of people have updated to it before we were able to replace it with a corrected build (build number 1393).
Our sincere apologies for the inconvenience!
Regards,
James
Please check for an update under the Preferences->General section. A new update should be available that resolves the problem.
Sadly there was a bug in the initial build (build number 1392) that was made available via automatic update. It was only available for around 10mins, however unfortunately a number of people have updated to it before we were able to replace it with a corrected build (build number 1393).
Our sincere apologies for the inconvenience!
Regards,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
It appears as though "DNSMODE full" isn't working properly after this update either.
2017-05-22 07:52:53: PUSH: Received control message: 'PUSH_REPLY,persist-key,persist-tun,explicit-exit-notify 2,dhcp-option DNSMODE full,<removed for clarity>
2017-05-22 07:52:54: DNS mode set to Split
Server is telling client to use full DNS, but client says it's using split. Any ideas?
2017-05-22 07:52:53: PUSH: Received control message: 'PUSH_REPLY,persist-key,persist-tun,explicit-exit-notify 2,dhcp-option DNSMODE full,<removed for clarity>
2017-05-22 07:52:54: DNS mode set to Split
Server is telling client to use full DNS, but client says it's using split. Any ideas?
Hi syCLuscH,
Thanks for the report - we can confirm we're seeing the same thing when attempting to set the DNS Mode via a dhcp-option command. We should have a new 1.7.1 beta build out in the next 24 hours with a fix for this.
In the meantime setting the DNS Mode locally does appear to work. This can be done via the Viscosity editor (under the Networking tab when editing the connection), or if you're editing Viscosity's configuration files directly you can use the following command (instead of using a dhcp-option command):
push "dhcp-option DOMAIN mycompany.com"
push "dhcp-option DOMAIN myotherdomain.org"
push "dhcp-option DOMAIN internal.lan"
The VPN DNS servers will then be used for the above domains and any subdomains of them.
Thanks,
James
Thanks for the report - we can confirm we're seeing the same thing when attempting to set the DNS Mode via a dhcp-option command. We should have a new 1.7.1 beta build out in the next 24 hours with a fix for this.
In the meantime setting the DNS Mode locally does appear to work. This can be done via the Viscosity editor (under the Networking tab when editing the connection), or if you're editing Viscosity's configuration files directly you can use the following command (instead of using a dhcp-option command):
Code: Select all
[Edit] Alternatively, if only a limited number of domains need to use the VPN's DNS servers you may like to consider pushing out the domains from the server, which will avoid the need for a client-side configuration change. For example, if your users need to resolve the domains and all subdomains of mycompany.com, myotherdomain.org, and internal.lan, you can do this like so:#viscosity dns full
push "dhcp-option DOMAIN mycompany.com"
push "dhcp-option DOMAIN myotherdomain.org"
push "dhcp-option DOMAIN internal.lan"
The VPN DNS servers will then be used for the above domains and any subdomains of them.
Thanks,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Hi syCLuscH,
An updated beta version is already available, and a release version will likely be late this week (we're waiting for an OpenSSL update due on Thursday). There are no known issues with the current beta version, so you could potentially roll that out if the issue needs to be urgently resolved and it isn't possible to wait for the full update.
Cheers,
James
An updated beta version is already available, and a release version will likely be late this week (we're waiting for an OpenSSL update due on Thursday). There are no known issues with the current beta version, so you could potentially roll that out if the issue needs to be urgently resolved and it isn't possible to wait for the full update.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
9 posts
Page 1 of 1