Apart from that, there's a good chance auto-update will work in a few hours if your node isn't too old.
On Saturday 13 December 2008 16:33, Dennis Nezic wrote: > On Sat, 13 Dec 2008 10:21:32 +0000, jdavies <jdaviestx at tx.rr.com> wrote: > > > I see this in my "alerts" section: > > > > Build too old > > This node's software is older than the oldest version (Build #1192) > > allowed by the newest peers we try to connect to. Please update your > > node as soon as possible as you will not be able to connect to peers > > labeled "TOO NEW" until you do. (Freenet may leave your node in the > > dust of the past if you don't upgrade.) > > > > So I tried running the "update.sh" script (I'm running on Linux), but > > I get: > > > > debian:Freenet$ ./update.sh > > Updating freenet > > Created temporary download directory. > > Checking sha1test.jar ... > > sha1test.jar may be out of date or corrupt, attempting to download a > > new versionDownloaded sha1test.jar but its md5sum is bogus. > > Using old jar. > > Fetching update.sh > > https://checksums.freenetproject.org/latest/update/update.sh.sha1 > > An SSL exception has > > occured:sun.security.validator.ValidatorException: PKIX path building > > failed: sun.security.provider.certpath.SunCertPathBuilderException: > > unable to find valid certification path to requested target > > Could not download new update.sh. > > > > Any suggestions? > > You probably have an outdated update.sh. Try downloading the latest > update.sh from http://downloads.freenetproject.org/alpha/update/ > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/support/attachments/20081213/f845882d/attachment.pgp>