Hi Wyatt,
Thanks for your response! Is there a solution which doesn't include running HTTP / HTTPS server on same machine?
Thanks,
Nenad.
Hello everyone,
I have a problem with the latest version of TurboFloatServer. After I activate it (TurboFloatServer.exe -a="product_key") and start it (either by installing as a service "TurboFloatServer.exe -i -config="default_configuration.xml" or by starting it as a process "TurboFloatServer.exe -x"), it constantly binds on 0.0.0.0. I would say the same version worked great a few weeks ago, but, probably, one of Windows updates broke it. My Windows version is Windows 10 Pro x64, version string is 10.0.19041.508. I used x64 version of Windows TurboFloatServer.exe. Btw, I only changed port-number in default TurboFloatServer-config.xml to 10013 (also tried with other 5678, 22123, ..).
Did you have similar experience and how to solve this?
Thanks,
Nenad.
Configure for HTTPS and set just_scgi
to true, and explicitly set the address.
https://wyday.com/limelm/help/turbofloat-server/#config-https
Hi Wyatt,
Thanks for your response! Is there a solution which doesn't include running HTTP / HTTPS server on same machine?
Thanks,
Nenad.
Is there a solution which doesn't include running HTTP / HTTPS server on same machine?
Not currently. Hosted TFS instances are coming soon.
Clarification please: Is TFS binding to 0.0.0.0 a failure state, or normal to be expected for listing for any networks?