yesdog / Waterdog

Waterdog, a Yesdog fork of Waterfall/BungeeCord that adds Bedrock support.
MIT License
186 stars 37 forks source link

Bug while being online #96

Closed HealingArcYT closed 4 years ago

HealingArcYT commented 4 years ago

Version of Waterdog Latest CodeMC build (302)

Expected Behavior Nothing

Actual Behavior

[12:12:22 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: writeAddress(..) failed: Connection refused
[12:12:22 INFO]: [HealingArcYT] disconnected with: The server you were previously on went down, you have been connected to a fallback server
[12:12:22 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: sendmmsg(..) failed: Connection refused
[12:12:22 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: writeAddress(..) failed: Connection refused
[12:12:22 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: writevAddresses(..) failed: Connection refused
[12:12:22 INFO]: [/***.**.***.***:59229|HealingArcYT] -> UpstreamBridge has disconnected
[12:12:23 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: sendmmsg(..) failed: Connection refused
[12:12:23 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: writeAddress(..) failed: Connection refused
[12:12:24 WARN]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] - NativeIoException: writeAddress(..) failed: Connection refused
[12:12:24 INFO]: [/***.**.***.***:59229|HealingArcYT] <-> DownstreamBridge <-> [testserver] has disconnected

Crashdump, Backtrace or Other Files

Describe the bug Player disconnects whyever short time after connecting

To Reproduce I dont know how to reproduce it exactly

Screenshots I have no screenshots

Server software used: Nukkit

Additional context

ZizzyZizzy commented 4 years ago

Getting the same error with Nukkit:

This server is running Nukkit git-71aea3f 「」 implementing API version 1.0.9 for Minecraft: BE v1.14.60 (protocol version 390) But I'm getting "failed: Operation not permitted"

If I configure two PMMP 1.14.60 servers, the first one connects fine and so far plays fine. When I use /server second, it connects and starts to act normally until I interact with the world, then I get the same error and it kicks me off the server.

colinrgodsey commented 4 years ago

@ZizzyZizzy "failed: Operation not permitted" comes from firewall rules usually, or bad address. Is there anything automating firewall rules? Does it work ever?

@HealingArcYT what kind of hosting are you using? those errors can generally happen if there's too many sockets open for docker/kubs containers

TobiasGrether commented 4 years ago

Closed due to inactivity. Can be reopened by the author if necessary