Both my Sync and Mystic boards have been unable to connect to MRC since 6 Sept at roughly 10:55 AM EDT.

The Mystic multiplexer has been reporting this constantly:

Sun Sep 8 10:44:23 2024 Attempting connection to mrc.bottomlessabyss.net on port 5001 using SSL transport
Sun Sep 8 10:44:28 2024 Unable to connect to mrc.bottomlessabyss.net:5001
Sun Sep 8 10:44:28 2024 Reconnecting in 10 seconds
Sun Sep 8 10:44:38 2024 Attempting connection to mrc.bottomlessabyss.net on port 5001 using SSL transport
Sun Sep 8 10:44:43 2024 Unable to connect to mrc.bottomlessabyss.net:5001
Sun Sep 8 10:44:43 2024 Reconnecting in 30 seconds
Sun Sep 8 10:45:13 2024 Attempting connection to mrc.bottomlessabyss.net on port 5001 using SSL transport
Sun Sep 8 10:45:18 2024 Unable to connect to mrc.bottomlessabyss.net:5001
Sun Sep 8 10:45:18 2024 Reconnecting in 60 seconds

Tried stopping and restarting the client, same thing persists.

Did something change with the MRC server? Or have I maybe been blackballed from MRC :( ?

|01<|09co|03d|11e|15Ÿ|11e|03n|09ix|01>|07


...Today is the first day of the rest of the mess.
--- SBBSecho 3.20-Win32
* Origin: -=[conchaos.synchro.net | ConstructiveChaos BBS]=- (1337:3/150)

On 08/09/2024 05:49 Codefenix said...

Did something change with the MRC server? Or have I maybe been

blackballed from MRC :( ? <code

Æ’enix>



There have been some upgrades, but the MRC server is up and rea
chable by both my
BBSes (different locations/IP's) so I would suggest maybe you
have had your IP
blacklisted by the server if it sent too many incorrect packets
too quickly perh
aps.



If you reach out to Stackfault on his BBS and let him know your
WAN IP he might
be able to unblock it for you.



--

|14Best regards,

|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meat
lotion:erb.pw


|07-- |08[|10eml|08] |15ml@erb.pw |07-- |08[|10web|08] |15www.e
rb.pw |07---
|07-- |08[|09fsx|08] |1521:1/158 |07-- |08[|11tqw|08] |151337:
1/101 |07---
|07-- |08[|12rtn|08] |1580:774/81 |07-- |08[|14fdn|08] |152:250
/5 |07------
|07-- |08[|10ark|08] |1510:104/2 |07--


--- ENiGMA 1/2 v0.0.14-beta (linux; x64; 18.20.4)
* Origin: thE dYslExIc dOnkEy ~ dydo.erb.pw:1337 (1337:1/201)

Re: RE: Cannot connect to MRC
By: MeaTLoTioN to Codefenix on Sun Sep 08 2024 05:39 pm

There have been some upgrades, but the MRC server is up and reachable by both m BBSes (different locations/IP's) so I would suggest maybe you have had your IP blacklisted by the server if it sent too many incorrect packets too quickly per aps.

OK, I tried leaving the MRC connector services off for a while, and then turned them back on, like an hour or so later. Now working just fine.

|01<|09co|03d|11e|15Ÿ|11e|03n|09ix|01>|07


...For certain people, after fifty, litigation takes the place of sex.
--- SBBSecho 3.20-Win32
* Origin: -=[conchaos.synchro.net | ConstructiveChaos BBS]=- (1337:3/150)

Both my Sync and Mystic boards have been unable to connect to MRC since
6 Sept at roughly 10:55 AM EDT.

The Mystic multiplexer has been reporting this constantly:

Sun Sep 8 10:44:23 2024 Attempting connection to
mrc.bottomlessabyss.net on port 5001 using SSL transport
Sun Sep 8 10:44:28 2024 Unable to connect to mrc.bottomlessabyss.net:5001 Sun Sep 8 10:44:28 2024 Reconnecting in
10 seconds Sun Sep 8 10:44:38 2024 Attempting connection to mrc.bottomlessabyss.net on port 5001 using SSL transport
Sun Sep 8 10:44:43 2024 Unable to connect to mrc.bottomlessabyss.net:5001 Sun Sep 8 10:44:43 2024 Reconnecting in
30 seconds Sun Sep 8 10:45:13 2024 Attempting connection to mrc.bottomlessabyss.net on port 5001 using SSL transport
Sun Sep 8 10:45:18 2024 Unable to connect to mrc.bottomlessabyss.net:5001 Sun Sep 8 10:45:18 2024 Reconnecting in
60 seconds

The MRC server is using soft banning for repeated connections. It will usually clears itself after a short while and resume accepting traffic. If such a situation happens (the newer client will have increasing delays to avoid these situations), just turn off the service for some time and it should connect back after that.

In your case, having more than 1 board on the same source IP makes things even more likely to happen in case of problems where the clients tries to reconnect rapidly.

I've seen you're good to go now.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

... I put a dollar in one of those change machines. Nothing changed.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (1337:3/106)