Advanced Backups

Advanced Backups

1M Downloads

Bug report : Server socket exception in newest version

basmens opened this issue ยท 4 comments

commented

Not quite sure if this is the right place to report the bug, but this is the mod that caused it. I am playing the Prominence 2 modpack with friends and added the backup mod. On default config, nothing custom added (except this mod) I get a connection exception. Specifically, when joining a world, just after the 'loading world...' text moves near the top of the screen, I get the exception. I have attached the server logs below.

This bug happens for me on the fabric 1.20 - 3.7.1 version. The 3.6.5 version does work for me. I am not 100% sure Prominence 2 is fabric based, but I tried the forge version of this mod and got the exact same behavior.

2025-02-04-2.txt

To reproduce,

  • download the 'Prominence II RPG Hasturian Era' modpack and server pack. That for me is currently version 3.1.0hf.
  • Then (after getting the basic server running) add the Advanced-Backups mod to it, version fabric - 3.7.1.
  • Try joining...
    Upon joining, I get my errors

Versioning

  • OS: Windows 10
  • Minecraft Version: 1.20.1 (as per the Prominence 2 modpack)
  • Modloader(s): I believe it is a fabric based modpack, but I tried forge too as mentioned.
  • Mod Version: fabric - 3.7.1
  • Prominence 2 version: 3.1.0hf

I hope this is all the info you need, If you need any more, feel free to ask. If this is the wrong place to put this bug report, let me know too, I can put it elsewhere. Thanks for the awesome backup mod you made, the earlier versions work great! Have a great day

commented

Hmm. I don't see what could cause this and the log isn't too helpful... But I'll look into a reproduction tonight and move from there.

In the meantime, if you can provide a debug.log that would be handy - no worries if not.

commented

I have been trying to get the reproduction setup a bit more minimal, and have found that what I said earlier doesn't always work. I'll try to give you a bit more info in a few hours, otherwise tomorrow

commented

I seem to be completely unable to reproduce this bug consistently myself. I think that I maybe just got unlucky with a corrupted download, so I am closing this issue as can't reproduce. Sorry for the inconvenience

commented

No need to apologise. You did the right thing by reporting the issue, even if it turned out to be a download issue