• Connection closed by foreign host

    From nathanael@21:4/123 to All on Sun Jan 27 23:02:45 2019
    This is still happening to me. If I already have a session open, whether locally with ./mystic -l or via telnet, I cannot open a second session. I get "Connection closed by foreign host".

    I've completely wiped and reinstalled Mystic at least three times now, and it works for a bit, then this.

    I've got both Telnet and BinkP max sessions set to 8. And under
    Servers/General Options Max BBS Nodes is set to 8.

    Nodespy shows 7 nodes "Waiting".

    Wassup?

    +=====================+-+=======+----------------------------------------
    | *H:U:M:O:N:G:O:U:S* | | B:B:S | nathanael : jenandcal.familyds.org:2323 +=====================+-+=======+----------------------------------------

    --- Mystic BBS v1.12 A41 2018/12/27 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (21:4/123)
  • From g00r00@21:1/108 to nathanael on Wed Jan 30 15:32:06 2019
    This is still happening to me. If I already have a session open, whether locally with ./mystic -l or via telnet, I cannot open a second session.
    I get "Connection closed by foreign host".

    I think I asked this before, but if not I will now :) Do you see it in the mis logs? Can you see it initializing, can you see the connection coming in? hat does it say?

    It could be your OS or firewall preventing it. There could be another
    software fighting for the port. There could be a lot of reasons.

    --- Mystic BBS v1.12 A42 2019/01/25 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From nathanael@21:4/123 to All on Mon Aug 5 03:30:10 2019
    I had this issue several months ago -- having to do with trapping SIGINTs before running mystic which resulted in a buildup of chat??.dat files in /mystic/data. Simply clearing out chat??.dat and restarting mystic always cleared things up.

    Not this time, though. I only have a single chat1.dat in /mystic/data but
    when I attempt to telnet into the board from wan-side it connects and then immediately kicks me out with "Connection closed by foreign host."

    From lanside I can telnet in to the local IP no problem.

    Any thoughts?

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (jenandcal.familyds.org:2323) (21:4/123)
  • From Netsurge@21:4/154 to nathanael on Sun Aug 4 15:53:40 2019
    From lanside I can telnet in to the local IP no problem.

    Any thoughts?

    Check to make sure your IP isn't in the blacklist.txt file.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://diskshop.ca/scinet

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From nathanael@21:4/123 to Netsurge on Mon Aug 5 12:58:26 2019
    Check to make sure your IP isn't in the blacklist.txt file.

    Nope, didn't see it.

    Could someone do me a favor and try to connect?

    jenandcal.familyds.org 2323

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (jenandcal.familyds.org:2323) (21:4/123)
  • From jeff@21:1/180 to nathanael on Mon Aug 5 00:27:11 2019
    On 05 Aug 2019, nathanael said the following...
    Could someone do me a favor and try to connect?
    jenandcal.familyds.org 2323

    I was able to get to a username prompt.

    Jeff.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Perceptronica (21:1/180)
  • From Avon@21:1/101 to nathanael on Mon Aug 5 19:27:02 2019
    On 04 Aug 2019 at 11:30p, nathanael pondered and said...

    Any thoughts?

    What does the MIS server report when you connect, on screen and in the logs?

    Have you tried closing MIS down and restarting?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From jeff@21:1/180 to nathanael on Mon Aug 5 18:57:14 2019
    On 04 Aug 2019, nathanael said the following...
    Not this time, though. I only have a single chat1.dat in /mystic/data but when I attempt to telnet into the board from wan-side it connects and
    then immediately kicks me out with "Connection closed by foreign host."

    I just ran into an issue that may or not be related. I have a router with
    port forwarding going on, so that incoming connections on certain ports get forwarded to the BBS computer, which is behind the router.

    When connections are made from behind the router using the BBS computer's internal (LAN) IP address or hostname, the IP address is logged as the connecting machine's internal address. I can't connect twice simultaneously from the same machine because the BBS refuses the second connection as a Duplicate IP.

    When connections are made from beyond the router, the IP address that gets logged is the other machine's internet IP address.

    However, when I connect to the BBS from inside the LAN using the router's external hostname (the name that's in the internet DNS), the IP address that gets logged is the router's *internal* IP address. Because of this, I can simultaneously connect from as many internal computers as I want as long as I use the BBS's internal IP or hostname, but when I use the external hostname I can only connect from one machine on the whole LAN at a time because of the Duplicate IP rule.

    Jeff.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: Perceptronica (21:1/180)
  • From Avon@21:1/101 to jeff on Tue Aug 6 12:37:41 2019
    On 05 Aug 2019 at 02:57p, jeff pondered and said...

    as long as I use the BBS's internal IP or hostname, but when I use the external hostname I can only connect from one machine on the whole LAN
    at a time because of the Duplicate IP rule.

    But you can change that dupe IP setting to negate this, if you want to.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From sPINOZa@21:1/116 to nathanael on Tue Aug 6 03:07:05 2019
    Could someone do me a favor and try to connect?
    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)

    Seems to work fine, I am still online :)

    Gtx,
    sPi

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: -.sOUNDGARDEn.- (21:1/116)
  • From nathanael@21:4/123 to Avon on Thu Aug 8 14:14:49 2019
    Have you tried closing MIS down and restarting?

    Yeah, I'd restarted everything. I clearly recall I still had the problem.
    But others are reporting no problems. And I just tried again, and now I can connect, too. I'll check the MIS logs just out of curiosity, but you know
    what they say about the mouths of gift horses.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (jenandcal.familyds.org:2323) (21:4/123)
  • From nathanael@21:4/123 to jeff on Thu Aug 8 14:18:46 2019
    Thanks. I'll have to reread your message more carefully; my head was kinda swimming by the end -- external from internal, internal from whatever :-) -- but sounds like there might be something there.

    The one potential complication is that I route all network traffic through an external VPN service.

    --- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
    * Origin: *HUMONGOUS* BBS (jenandcal.familyds.org:2323) (21:4/123)
  • From x1pepe@21:1/150 to All on Mon Dec 21 23:34:10 2020
    Hi all!
    When a new user try to write the Alias name to create an account get this message:

    Connection closed by foreign host

    ... and the connection ends.
    In Mystic, New User Settings Menu I have:

    Allow New Users: Yes
    Security: 20
    Password:
    New User Feedback: Yes
    Use Usa Phone: No
    User Format: As Typed
    Start Msg Group: 2
    Start File Group: 2

    What I am missing?
    Thanks ...

    *Sotano Msx BBS*
    telnet sotanomsxbbs.org:23
    <Ultimo usuario activo de Msx en Ibiza>

    --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)
    * Origin: Sotano Msx BBS (21:1/150)