#(rushll) crashed

21 messages · Page 1 of 1 (latest)

mild ermineBOT
#

(rushll) crashed

#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.

loud light
#

!logs

rugged shaleBOT
# loud light !logs
Info: logs

Please post your full latest log file.

Background Info: One of the most helpful tools to identifying the source of a problem is your server logs file! Logs contain all sorts of important information like server and plugin versions, any error messages, and a lot more important information (More Info).

How To: Your log can be found in the logs folder within your server folder. The most recent log is a text file labeled latest.log. To get help using these logs, please open that file in a text editor and copy all of the text, then open https://paste.denizenscript.com/New/Log and paste the text into the box on the page. Then click "Submit" and copy the URL and paste that back into this channel.

Please do not upload the file to Discord or to other pastebin services, use the log pastebin linked above.

loud light
#

@lapis mortar You'll have to provide a server log which includes the crash, please follow the instructions. A snippet may show part of the problem but it does not show the full problem and a server log will help identify what the root cause of it is generally.

teal brook
#

It's a file called latest.log

#

Probably have to scroll down a bit

abstract canopy
#

@lapis mortar

loud light
#

!checklogs

rugged shaleBOT
loud light
#

In the future please follow the instructions and use the website.

rugged shaleBOT
#
Server Version

Paper version git-Paper-307 (MC: 1.19.2)-- (:warning: Outdated build, behind by 243... Current build is 550)

Plugin Version(s)

Citizens v2.0.33-SNAPSHOT (build 3311) -- (Current build :white_check_mark:)

Checked For

@loud light

Online/Offline

Offline, but proxied.

Other Noteworthy Plugin(s)

WorldGuard v7.0.8+33cdb4a, MythicMobs v5.3.5-64893d49, ProtocolLib v5.0.0

Suspicious Line(s)

[06:16:18] [Server thread/INFO]: [Investment] [STDOUT] [Investment] Leaked by Chan5k @ BlackSpigot.com :triangular_flag_on_post: Server is likely running cracked plugins.

Suspicious Plugin(s)

LoginSecurity v3.3.0 :triangular_flag_on_post: (Offline login authenticator plugin)
SkinsRestorer v15.0.4 :triangular_flag_on_post: (Offline skins fixer plugin)

Problematic Plugin(s)

PlugManX v2.3.4 - :warning: Plugin Managers are dangerous and will cause unpredictable issues. Remove it.
Geyser-Spigot v2.2.1-SNAPSHOT - Bedrock clients are unsupportable. Please do all testing with a Java Edition client.
floodgate v2.2.2-SNAPSHOT (b88-94eabd7)

Possibly Relevant Plugin(s)

GadgetsMenu v4.9.3 - GadgetsMenu has been linked to compatibility issues with Citizens.
MVdWPlaceholderAPI v3.1.1 - Some scoreboard or name-edit plugins may lead to scoreboard control instability.
TAB v4.0.3 - This plugin adds Below_Name scoreboards to NPCs.
ViaVersion v4.9.2 - Mixed client vs server versions can sometimes cause packet-related issues.
HeadDatabase v4.17.0 - HeadDatabase has been known to cause issues with skins.
ModelEngine vR3.1.8 - ModelEngine has Citizens support, but that support is known to be buggy. Issues related to NPCs that use ModelEngine should be reported to ModelEngine support, not Citizens.
Multiverse-Core
GSit

Potentially Bad Line(s)

Starting Minecraft server on 0.0.0.0:26439 - server is offline but has no address bind. This might mean you're using a system level firewall, but if not, it means your proxy is bypassable by hackers. Either enable a system level firewall, or bind your server to localhost in server.properties via server-ip=127.0.0.1.
[06:16:20] [Thread-26/WARN]: Caused by: java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.github.com/repos/SkriptLang/Skript/releases :warning: Log contains error messages.

loud light
#

Oof.

#

👀

abstract canopy
#

@crimson kiln cracked @lapis mortar

crimson kilnBOT
abstract canopy
#

@crimson kiln crackedplugins @lapis mortar

crimson kilnBOT
urban apexBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@lapis mortar