Closed shushu789 closed 5 months ago
Hello and thank you for your feedback!
Can you send us the logs at project@fluxzy.io address?
Logs are located at %appdata%/Fluxzy Desktop/.config/logs
directory (paste in file explorer to reach to the directory).
Regards,
Sent, I saw the log is related to the socket, I suspect this may be a problem of default port conflict, can the fluxzy port be customized? Modify it before starting
Sent, I saw the log is related to the socket, I suspect this may be a problem of default port conflict, can the fluxzy port be customized? Modify it before starting
Indeed, the port 5198 is required by Fluxzy Desktop for internal communication and it looks like it's already busy. I'm forward to the Desktop team to look if there's a way to customize this port.
However, if it's possible, can you provide us (if not confidential) the port that's was already listen to 5198. This will help us to change the default port.
netstat -nao | find "5198" | find "LISTENING"
Then with the pid
tasklist /fi "pid eq found_pid"
I checked this port number but got no results, and I didn't see the port number process of 5198 in Task Manager--Resource Monitor--Listening Port List, which is strange.
Thank you for your fast feedback.
Looking closer at the logs, the port binding is failing with a 10013 socket error. This either means that the port range was reserved by another application or due to some security measures.
For the first issue, can you run the following command to see if it was excluded?
netsh interface ipv4 show excludedportrange protocol=tcp
For the second, apart from Windows Defender, can you send us the firewall/antivirus software you are using, if any?
Regards
Based on the excluded port range results, 5198 is indeed excluded. Currently, I do not use any third-party firewall/antivirus software except Windows’ own firewall/antivirus software on my system.
In the current stable build (v1.18.2), it is not possible to change the default port without editing minified JS files, and we will not provide support to do it.
However, a fix is available in our recent alpha build which you can download here: v19.16-alpha (binary is signed like in the stable version).
The default service port has been updated to 10985 as we found that 5198 may be locked by some Hyper-V service. Finally, this default port can be customized through the FLUXZY_DESKTOP_SERVICE_PORT environment variable.
Thanks for your overall feedback.
Thanks, v19.16-alpha is currently available
Describe the bug I'm trying to use fluxzy desktop version, but it suddenly won't start, even uninstalling and reinstalling the latest version doesn't help. This just happened today. I have never encountered this problem before. At least I could open it yesterday.
Describe the tool and the environment
To Reproduce Steps to reproduce the behavior:
Screenshot