failed to check for updates
-
-
BRUCE LEE already tried it
-
Xerxes
Hi, you mean like this? -
Xerxes said in failed to check for updates:
I have the same issue. Can you please post a fix to this?
-
Nah, I mean ping or nslookup. But I guess it works.
Since you are using the torrent, have you tried to manually download plutonium.exe? Eventually the old version in the torrent can't update itself anymore. -
Xerxes said in failed to check for updates:
I have the same issue. Can you please post a fix to this?
all you to do is update your clock at internet time i mean at [ change date and time ] and change time zone to ur country
thats it -
all you to do is update your clock at internet time i mean at [ change date and time ] and change time zone to ur country
thats it_spaCe_ what? wdym by that
-
I have the same exact problem and i cant fix it, any help would be appreciated
-
Hostftw
on taskbar and hit left click on mouse -- look at the clock at the right corner taskbar and then hit change dat and time setting and then internet time and change settings and update now thats it
and u can add dns too 8.8.8.8 and 8.8.4.4 -
Interesting, I seem to be getting an extremely similar, if not the same error. Is there a working Fix for it?
Everything else is the same for me (The Crash ID is different every time I attempted to turn Plutonium on tho)
These are the results based on what Xerxes recommended:
Ping for 104.21.233.227
Pinging cdn.plutonium.pw [104.21.233.227] with 32 bytes of data: Reply from 104.21.233.227: bytes=32 time=31ms TTL=53 Reply from 104.21.233.227: bytes=32 time=28ms TTL=53 Reply from 104.21.233.227: bytes=32 time=31ms TTL=53 Reply from 104.21.233.227: bytes=32 time=30ms TTL=53 Ping statistics for 104.21.233.227: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 31ms, Average = 30msPing for 104.21.233.228
Pinging 104.21.233.228 with 32 bytes of data: Reply from 104.21.233.228: bytes=32 time=29ms TTL=53 Reply from 104.21.233.228: bytes=32 time=36ms TTL=53 Reply from 104.21.233.228: bytes=32 time=31ms TTL=53 Reply from 104.21.233.228: bytes=32 time=36ms TTL=53 Ping statistics for 104.21.233.228: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 36ms, Average = 33msNSLookUp for
cdn.plutonium.pwServer: ********* Address: ************************ (dunno if this is private, so im censoring it) Non-authoritative answer: Name: cdn.plutonium.pw Addresses: 104.21.233.227 104.21.233.228 -
Interesting, I seem to be getting an extremely similar, if not the same error. Is there a working Fix for it?
Everything else is the same for me (The Crash ID is different every time I attempted to turn Plutonium on tho)
These are the results based on what Xerxes recommended:
Ping for 104.21.233.227
Pinging cdn.plutonium.pw [104.21.233.227] with 32 bytes of data: Reply from 104.21.233.227: bytes=32 time=31ms TTL=53 Reply from 104.21.233.227: bytes=32 time=28ms TTL=53 Reply from 104.21.233.227: bytes=32 time=31ms TTL=53 Reply from 104.21.233.227: bytes=32 time=30ms TTL=53 Ping statistics for 104.21.233.227: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 31ms, Average = 30msPing for 104.21.233.228
Pinging 104.21.233.228 with 32 bytes of data: Reply from 104.21.233.228: bytes=32 time=29ms TTL=53 Reply from 104.21.233.228: bytes=32 time=36ms TTL=53 Reply from 104.21.233.228: bytes=32 time=31ms TTL=53 Reply from 104.21.233.228: bytes=32 time=36ms TTL=53 Ping statistics for 104.21.233.228: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 36ms, Average = 33msNSLookUp for
cdn.plutonium.pwServer: ********* Address: ************************ (dunno if this is private, so im censoring it) Non-authoritative answer: Name: cdn.plutonium.pw Addresses: 104.21.233.227 104.21.233.228GenTest1 Are you using the torrent ?
