Wyday.com blockedAnswered

We just rolled out our first project using limeLM and I am a bit overwhelmed with the number of offline activation requests. A lot of these can be resolved by removing an entry in users's hosts file but there are some cases where even after that, wyday.com does not open in their browser.

What are other ways that users might have blocked access on both Windows and OSX? These users report they are not running a firewall.

Answer

Much more information is needed. We have a FAQ: https://wyday.com/limelm/help/faq/#internet-error

I got a customer that was very helpful with troubleshooting. This is what we got:

-------------

1. nslookup wyday.com

-------------

Server: dns.opendns.com

Address: 208.67.222.222

Non-authoritative answer:

Name: wyday.com

Addresses: 2606:4700:`0::ac43:20b2

2606:4700:`0::6814:3f62

2606:4700:`0::6814:4062

172.67.32.178

104.20.63.98

104.20.64.98

-------------

2. Tracert wyday.com

-------------

Unable to resolve target system name wyday.com

3. Wyday.com does not open in Internet Explorer on Windows 10 Pro

4. Regedit entries for TLS 1.2 did not help

4. No AV, VPN, or Firewall

5. Windows Defender running. After turning it off, still no connection to wyday.com

What else can we try short of Wireshark?

, edited
Answer

Is it a TLS problem? What error are they seeing?

Is this a corporate network? Tell the admin to fix the network.

Is this an authoritarian state? Tell them to work around the facist state.

Much more information is needed to help. This is basic networking stuff. They need to fix their stuff.

wyDay is up and running in all parts of the world. It works on all up-to-date systems and networks.

, edited

The issue is affecting many of my users across different countries, none of which have been confirmed to be from authoritarian states so far.

The IE error I am getting from the same customer that info is posted about above is: ERR_ADDRESS_UNREACHABLE

The Lime error is TA_E_INET when calling TA_UseTrial or TA_Activate

The user is using a home network. I doubt any of my customers are using a corporate one, due to the nature of the product.

We can't reproduce this. We've had no downtime in months. And our servers are reachable from every country with internet access.

Much more information is needed. If they're blocking wyday.com through piracy tools / hosts-file block lists, or whatever, then the solution is to stop doing that.

Have them install updates available, and remove any piracy tools.

, edited

It's not the hosts file, and I am trying to figure out what else this could be but I am out of ideas. 

Ping wyday.com does not work but nslookup in debug is fine. Here's a trace: https://filedn.com/lWF0N9OPEsvVO4AG7TpMr5L/WydayNSLookup.txt
 

If it is true that cracks are so widespread, it would be great if there was some kind of a diag app from you guys that customers could run and check for common issues, recognize common cracks, etc. This is our first product, and I am worried about how much we will have to scale support to handle offline activations as we release more software.

Users have no idea what is doing this, so they don't know how to stop it.

If it is true that cracks are so widespread, it would be great if there was some kind of a diag app from you guys that customers could run and check for common issues, recognize common cracks, etc.

This isn't a widespread problem.

This is our first product, and I am worried about how much we will have to scale support to handle offline activations as we release more software.

Are you using the latest version of TurboActivate? Are you using the dynamic version or the static version (if you're using the static version, switch to the dynamic version).

That log you posted shows no errors. Yes, that's some useful information, but not enough useful information to help.

Start by:

  1. Update TA to the latest version (currently 4.4.4.0).
  2. If you're using the static version of TurboActivate, switch t o the dynamic version of TurboActivate.
  3. Update their version of Windows to 10 or 11, and apply every single Windows update available.
  4. Update all their network drivers.

After updating everything, restarting the PC, and attempting to access wyday.com inside internet explorer again, if they're still getting errors, you need to investigate their network and see what they've done wrong.

There are a billion ways to mess up a network. We cannot provide any tool to fix broken networks.

, edited

Yes, we are on 4.4.4.0. Very interesting point about static lib, that is what we are using, because we have other static libraries in the project and cannot switch to dynamic.

Can you give me some more info about why the static one would behave differently than the dynamic one, and if there is anything I can do to work around that without switching?

Answer

OK, we've added a FAQ about it because this question has come up enough in the past few years to warrant a centralized answer:

Don't use the static library, only use the dynamic library!

No, there's no workaround. Every app can use dynamic libraries.