Everything posted by craeonics
Apex uses http://update.apexdc.net/version.xml as the update URL. update.apexdc.net is a CNAME to vhost.sourceforget.net. Note the extra t. If you visit update.apexdc.net, you get redirected to some shady scam site: ww1.survey-prize.com Meaning my system log after restarting Apex is filled with this, since Apex will not stop checking: [20150716/1911] DHT bootstrap error: An attempt was made to access a socket in a way forbidden by its access permissions. (http://survey-prize.com/) [20150716/1911] Update Check: could not download digital signature (An attempt was made to access a socket in a way forbidden by its access permissions.) Perhaps the CNAME could be changed to point to the right host? I don't know how long this has been broken. I only restart due to monthly windows updates.
Hurray! Unfortunately, SourceForge is still belly up: [20150719/1233] DHT bootstrap error: HTTP/1.0 503 Service Unavailable (http://update.apexdc.net/version.xml.sign) [20150719/1233] Update Check: could not download digital signature (HTTP/1.0 503 Service Unavailable) [20150719/1233] DHT bootstrap error: HTTP/1.0 503 Service Unavailable (http://update.apexdc.net/version.xml) [20150719/1233] Update Check: could not connect to the update server (HTTP/1.0 503 Service Unavailable) This does not bode well for their already quite tarnished reputation. I noticed there's a https://www.apexdc.net/version.xml that could be used as a replacement for http://update.apexdc.net/version.xml, but it's missing the version.xml.sign and a tad outdated.
Re: DHT bootstrapping, even with those errors, my DHT pool seems to have been populated right after starting the client (currently at some 1750+ nodes). I assume these partially came from the previous session. So would it still be necessary for Apex to try and bootstrap that if it's already populated?