1924 results found
Entry: https://wyday.com/blog/2023/q4-2023-big-stuff/
Yes, to both questions: https://wyday.com/limelm/help/turbofloat-server-commandline/ Use -v to figure out the license they're using.
Also, have them run these 2 PowerShell commands and provide the full results: https://wyday.com/forum/t/32294/activation-error-enable-network-adapters/#post-53658
It's covered here: https://wyday.com/blog/2024/2024-a-year-of-behind-the-scenes-progress/ And multiple times on the forum already.
https://wyday.com/limelm/help/faq/#in-vmAlso, fix your code to catch exceptions and show useful warnings to customers.
This type of problem (time based licensing) is what custom license fields were made for: https://wyday.com/limelm/help/license-features/ So create a single product version and limit when they can no longer receive free updates using a date/time field.
Described here: https://wyday.com/limelm/help/trials/ 3.
The current and proposed API Key restrictions (Max of 3 IP Addresses per 72 Hours - https://wyday.com/forum/t/4205/current-limelm-server-status/#post-19959) are not compatible with services hosted on Azure App Service (https://docs.microsoft.com/en-us/azure/app-service/) and possibly other hosting/PAAS solutions or Function/Lambda services.
From: https://wyday.com/limelm/help/faq/#fix-broken-wmi "Remove all anti-virus software except Microsoft's Defender anti-virus.
However, this information is readily available in the web API functions as the "total_deacts" and "deac_limit" in the following functions: https://wyday.com/limelm/help/api/limelm.pkey.getDetails/https://wyday.com/limelm/help/api/limelm.pkey.activity/https://wyday.com/limelm/help/api/limelm.pkey.advancedSearch/ Any of which seem like a better fit than manually exporting all the data in your account to get a value that by its very nature changes often.
> Also, whitelist https communication (wyday.com over 443), as described in the FAQ: https://wyday.com/limelm/help/faq/#internet-error Yes, already confirmed.
I've done this on the affected computer: cd ~ curl -kO https://letsencrypt.org/certs/isrgrootx1.pem curl -kO https://letsencrypt.org/certs/isrg-root-x2.pem sudo security add-trusted-cert -d -r trustRoot -k "/Library/Keychains/System.keychain" "isrgrootx1.pem" sudo security add-trusted-cert -d -r trustRoot -k "/Library/Keychains/System.keychain" "isrg-root-x2.pem" I've also done this as suggested by Apple: Download https://letsencrypt.org/certs/isrgrootx1.pem Download https://letsencrypt.org/certs/isrg-root-x2.pem 1 Open Keychain Access. 2 Select the System keychain. 3 Double click or drag and drop ‘isrgrootx1.pem’ to install it to the System keychain. 4 Authenticate. 5 Double click ‘isrgrootx1.pem’ in the System keychain to open it. 6 Click the disclosure triangle next to ‘Trust’ to view the trust settings. 7 In the drop down menu for ‘When using this certificate’, select Always Trust. 8 Authenticate again if prompted. 9 Double click or drag and drop ‘isrg-root-x2.pem’ to install it to the System keychain. 10 Authenticate. 11 Double click ‘isrg-root-x2.pem’ in the System keychain to open it. 12 Click the disclosure triangle next to ‘Trust’ to view the trust settings. 13 In the drop down menu for ‘When using this certificate’, select Always Trust. 14 Authenticate again if prompted.
So they're blocking wyday.com an/or https://wyday.com intentionally or unintentionally.
You can find the latest version here: https://wyday.com/limelm/api/
For re-activation of offline activation you need to go through the whole process again (except for entering the product key): https://wyday.com/limelm/help/offline-activation/
A way to reproduce what you're seeing. wyUpdate doesn't do things unless you tell it to do things: https://wyday.com/wybuild/help/faq.php#how-it-works So, the information we need is a way to reproduce wyUpdate *not* doing what you told it to do.
Hey Mey, More information is needed: https://wyday.com/limelm/help/faq/#useful-reports Are you using the Unicode NSIS?
Hi again,I am using the C# AutomaticUpdater and I do like that: automaticUpdater.wyUpdateCommandline = "-updatepath=\"https://192.168.1.7:8081/static/\"";automaticUpdater.ForceCheckForUpdate(); But its gives me an error, and in the error I can see that its still looking at the old IP, not what I setted....
The web API docs talk about the parameters and what valid values are: https://wyday.com/limelm/help/api/limelm.pkey.generate/ "subscriptionReference" = "email", is not how feature values are set (subscriptionReference is not a parameter we accept).
Use POST and use an HTTPS communication tool (curl, wget, etc.) to do the request.