Slimefun

Slimefun

3M Downloads

[PKIK path building failed] keep spamming

Opened this issue ยท 5 comments

commented

Description (Required)

I have my console spammed with [Craft Scheduler Thread - 0/WARN]
I'm worry about a security leak :(

Steps to reproduce the Issue (Required)

I started a fresh install, with Spigot 1.14.4, CS-CoreLib, SlimeFun and 1 other plugin: ProtocolSupport

Expected behavior (Required)

Previously, I didn't have this issue, but recently, it happened.

Server Log / Error Report

https://pastebin.com/f7bBKCgH

Environment (Required)

  • Minecraft Version: 1.14.4
  • Slimefun Version: Slimefun vDEV - 477 (git 156683f)
  • CS-CoreLib Version: CS-CoreLib vDEV - 84 (git 0d29dbee)
    image
commented

Update your Java and your servers root certs, seems you're using some real outdated shit.

Edit: Wait... are you on a bloody xp machine? Don't be surprised if modern security protocols and certs don't work on a very old machine...

commented

Oh, really, I have J8 x64 update 241, I'm on W7 with classic theme, and do u mean updating to another java ver, 9+ ?
Thanks for the help, but that make me sad :((

commented

Hmm should be fine on 241. Do you still get this?

commented

Yea, I still get this, sometimes, the sv online long enough, it disappear, magically, and at the next start, it still happens

commented

The error has nothing to do with Slimefun, at least not directly, and therefore I am closing this issue.

I have encountered errors like these myself before, they can be hard to fix.
For me the fix was to switch from Java's JDK to OpenJDK. (JDK is the developer version of Java, not the version you'd run your server with).
Basically what happens:
Your server tried to connect to Mojang's skin servers but was rejected due to a certificate error.

Updating your Java version would be the easiest solution but you should update your OS too.
If anything fails and your local certificates somehow corrupted then there is no way around manually re-adding the certificates using Java's keytool.
You can find a lot of explanations how to do that online, as it is a rather common issue.

Given that you are still on Windows 7 and Windows 7's support has ended recently, that might very well be a problem too.