I was running docker yest. Can't remember if I had turned it off before running the tool.ascsd your error could be two things: either windows (or your antivirus/firewall) decided to be retarded and use some random port that f95checker also uses, some reports online suggest that hyper-v and docker sometimes use random ports for no reason, or your firewall is blocking the port from being bound at all.
If you mess around in some settings, you need to look for a way to unblock or free port 57095 (don’t port forward it tho!). I’m not sure if I should suppress the error, or write some small popup saying hey something is blocking this port, if you don’t fix it then the browser extension won’t work. Either way that’s the most I can do when the port is being blocked
Jarulf jemesbond your errors should be fixed in the latest beta build, try it here and let me knowYou must be registered to see the linksfind the newest one with a green tick mark and download the correct artifact for your system (GitHub account is required)
After a restart, it works normally now
probably best to show a popup so user's aren't confused when the extension doesn't work. but not sure how to tell them why in simple terms