Posts by Steve0615

Yeah, just watching server activity this AM....it will work well for a while, then kick them both off around the same time, then not let them get back in, then let them in a minute later.

From the modem/router perspective, I'm monitoring the activity...and everything port-wise seems to be working. I downloaded a few other Minecraft servers, just to test activity there...and they can log onto them no problem. I'll get an io.netty error via Aternos.me server, then quickly jump over to another server...and it lets me right on. If it was a modem/router problem, I would expect more errors across the board.

(1) Yes, in the Houston, TX area...
(2) Timing seems to be random. Didn't work at this hour yesterday; working fine today.
(3) I'll trace route from both computers when I get a chance. Data sent last night was from the PC.
(4) I'll send you my IP privately.

The fact that both the PC and Mac can get on (or not get on!) always at the same time lead me to think it's nothing internal to either computer. Hence, the next place I'd think to look at: (a) something related to AT&T and/or their router; or (b) something with the Aternos server that is hanging up.

I still do part-time IT work for a couple of non-profits, so part of me is just curious about problem solving this issue.

Thanks for your time. And great job on the server (when it works!). Happy my boys have a place to play.

Seems like this io.netty.channel error is cropping up randomly.

I have two boys on a Mac and PC (respectively) with their own Minecraft accounts. They were able to play fine online for 2-3 weeks using either of their Aternos accounts (as well as their friend's account). They used Vanilla editions as well as Forge...no problems. Then all of a sudden we started getting the io.netty.channel error frequently.

Sometimes we could delete a world....and it would work. Other times we couldn't get anything to work...only to come back the next day and have it work.

Tried the DynIP option...same issue. Tried to do a trace route while the server was running...see attached.

Part of me wonders....could it be a ISP issue? We tried it earlier today at home using our AT&T service....couldn't get on. Then went over to the grandparents house (who use Comcast)...and voila(!) worked like a charm for 2 hours. Then came home and promptly tried it again (AT&T)....and didn't work.

Any advice on what to try next? Wondering if I need to configure something in the router.