Quote from: drays on November 19, 2020, 09:29:23 PM

Quote from: Dom Wyrda on November 19, 2020, 06:30:41 PM

Quote from: drays on November 19, 2020, 04:30:32 PM

Quote from: Dom Wyrda on November 19, 2020, 08:51:37 AM

https://media.discordapp.net/attachments/778851322437828630/778904322205417482/unknown.png
Um.. someone help?
All my qt-wallets are down with this

Your wallet shows bind error 10013.

The first easiest thing I would try is to reboot the machine to release ports - if you didn't do that already, of course. If you did, then see https://stackoverflow.com/questions/3314656/what-causes-tcplistener-socket-error-10013

in particular it tells (though there is more info there):

Quote

This error code is caused by attempting to bind to a port that is exclusively in use by another process. The most common cause is accidentally starting the same service twice.

If in doubt, a quick check of TCPView should reveal which process has the port open.

I tried "listen=0", to make it use any available ports, and now that error doesn't occur, but another does
https://cdn.discordapp.com/attachments/753857994604937296/779050984479129630/unknown.png

..And the debug log has nothing in it (no writes since September)

Not sure why BitCore could be using HTTP server... But anyway, disabling "listen" is more of a workaround than a solution, as there is something wrong with that PC, which could manifest in different way, so it should be fixed instead.

Did you try to check who is using the port 8555? TCPView (https://docs.microsoft.com/en-us/sysinternals/downloads/tcpview) should show it. You may have some kind of malware, which is using multiple ports on your PC. Or just the opposite - a new antivirus, which is blocking all the ports.

I don't have any antivirus program(disabled Microsoft Defender permanantly as well), and I downloaded 2 to check if I had a virus and they say I don't (Deleted them afterwards Cheesy

)
I asked around more, and one told me that 0.0.0.0 is the local machine gateway, so my problem is probably there... But I have no idea what could be wrong.
I edited my bootloader with bcdedit a few days back, so that may be it, but it worked a few times after I edited, so I don't think that is it