Proxy problemAnsweredLocked
Hi, we use Turbofloat Server for a licensed product. Activation of the license is working but it will not reactivate its license after 90 days.
Message "This floating license server is activated, but it failed to verify the activation with the servers"
Proxy server is set and working. Even if i set a system proxy so no proxy should be needed any more it could not activate.
If i deactivate manually and reactivate manually its working.
License holder has no ideas any more and i am tired of reactivating manually every 90 days.
Regards,
Sascha
Server 2012 R2
TFS 4.4.4.0 (latest i guess)
<proxy url="http://proxy.ourdomain.tld:3128"/> (needs no user/pass)
Proxy settings in IE are set and are working
systemproxy is not set, set it but also not working so i removed it
TFS 4.4.4.0 (latest i guess)
Actually check. We don't track down bugs in old versions. It's not a good use of anyone's time.
Also, have them install all updates for the server. Directly from Windows Update.
Also, update the proxy software to talk to modern correctly configured and secure servers. If that doesn't work, disable the proxy until they can find proxy software that works.
Actually check. We don't track down bugs in old versions. It's not a good use of anyone's time.
so 4.4.4.0 is not the latest one? If i follow this link:
https://wyday.com/limelm/api/TurboFloat-Server-Windows.zip
i will get 4.4.4.0
i did not guess the version, i did guess that this is the latest one but its from my May 2021 may there is newer version? Idk
Also, have them install all updates for the server. Directly from Windows Update.
whats the matter here in this case? But yes its uptodate
Also, update the proxy software to talk to modern correctly configured and secure servers. If that doesn't work, disable the proxy until they can find proxy software that works.
have you read my post? I can browse via proxy - so proxy is working. Its squid proxy -- its working, and btw much more common than TurboFloat :)
In the logfile there is nothing written what the problem is exactly, just could not activate.
Could it not reach the proxy? Couldnt get the URL or may got some error back from proxy?
Which URL is it trying to reach so i can check further.
Could it not reach the proxy? Couldnt get the URL or may got some error back from proxy?
Maybe. Enable notification level logging in TFS. Enable logging in the proxy server, etc.
Which URL is it trying to reach so i can check further.
Notification level is already activated, https://wyday.com accessing in IE is OK
so its not a proxy problem
also not Firewall one, there is a rule for Turbofloat, no block in firewall rule logs
Our servers are up, latest TFS can contact the servers.
Enable logging on the proxy server and fix any configuration problem.
then please give more details for checking log – exact address and port please
and just to remember: manual activation is not a problem, only revalidation after 90 days is the problem
then please give more details for checking log – exact address and port please
Already answered in this thread and the FAQ.
The port? 443. Same as every HTTPS connection.
Ok but how this can be happen:
manual activation is not a problem, only revalidation after 90 days is the problem
it should be the same activation way or not?
What do you mean by manual activation?
Offline activation?
Running with "-a"?
Much more information is needed.
If online activation is succeeding sometimes and failing other times, then there's something on the device or the network blocking it conditionally.
I am just the customer, the application provider has no answer for that so i am writing here to find a solution
running with -a always works, but revalidation never and no there is no problem with our server or our network
we have more than 20 licenseserver running on different servers and none of them is (re)producing such errors
Contact the company that provides the app and they will provide support. This comes down to basic network management and supporting that.
We don't provide support to our customers' customers. There are a slew of reasons why, but primarily because we don't control our customers' software.
Contact the company that makes the software. That's not us.
Locking the topic.