SSH into Mystic is blocked reddit / bbs ---------------------------------------------------------------------- inop76 · 2019-08-19 02:48 I am testing a Mystic powered BBS and have enabled SSH. I am able to login from within the computer using localhost. I'm unable to ssh in from a remote computer. From the remote computer I do get password prompt but then it hangs and I get disconnected. Using localhost I get the prompt and was able to login. Is there something I'm missing? I'm using a Linux VPS and use ufw for the firewall. Disabling the firewall made no difference. ---------------------------------------------------------------------- mechroCutie · 2019-08-19 04:31 do you have the ssh port forwarded? is it listening on that port? ---------------------------------------------------------------------- inop76 · 2019-08-19 05:37 I have set up 8022 to be the ssh port. Using the SSH client I use the following command: From inisde the VPS \[working\]: **ssh -p 8022 test@localhost** From my laptop at home \[now working\]: **ssh -p 8022 test@** I am able to use telnet (port is 8023) and it works from inside and outside the VPS. Disabling the firewall didn't make a difference. Running netstat inside the VPS: `Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name` `tcp 0 0` [`127.0.0.53:53`](https://127.0.0.53:53)[`0.0.0. 0`](https://0.0.0.0)`:* LISTEN -` `tcp 0 0` [`0.0.0.0:8022`](https://0.0.0.0:8022)[`0.0.0.0`](https://0.0.0.0)`:* LISTEN 20289/./mis` `tcp 0 0` [`0.0.0.0:8023`](https://0.0.0.0:8023)[`0.0.0.0`](https://0.0.0.0)`:* LISTEN 20289/./mis` `tcp 0 0` [`127.0.0.1:25`](https://127.0.0.1:25)[`0.0.0.0`](https://0.0.0.0)`:* LISTEN -` `tcp 0 0` [`0.0.0.0:443`](https://0.0.0.0:443)[`0.0.0.0`](https://0.0.0.0)`:* LISTEN -` `tcp6 0 0 :::8022 :::* LISTEN 20289/./mis` `tcp6 0 0 :::8023 :::* LISTEN 20289/./mis` `tcp6 1 0 ::1:25 :::* LISTEN -` `tcp6 0 0 :::443 :::* LISTEN -` Not sure if I need to port forward if I'm supplying the port number in the ssh command. ---------------------------------------------------------------------- mechroCutie · 2019-08-19 05:39 the vps needs to know to direct traffic headed into that port to the machine. otherwise the machine cant respond, because it may not have received the command. edit: spelling and also im not an expert. this might not be an issue. ---------------------------------------------------------------------- inop76 · 2019-08-19 05:54 Sorry, I still don't understand... Telnet works (using port 8023 for this): telnet 8023 And I did no port forwarding. SSH into the VPS is on port 443 (I modified this myself.. this is were I get my Linux console) SSH into the BBS software is port 8022 If I explicitly supply the port number to ssh (-p 8022) why do I still need to port forward? Mystic is listening on port 8022 for SSH and 8023 for Telnet. I get the login prompt for ssh. I supply the username and password then it hangs for a few seconds and kicks me off. Mystic is seeing the SSH attempts: 05:51:23 SSH > Connect on slot 1/5 (remote\_ip)05:51:23 SSH 1-HostName Unknown05:51:23 SSH 1-Negotiating SSH session05:51:30 SSH 1-Creating terminal process05:51:36 SSH 1-Closing terminal process So it creates a "terminal process" then about 6 seconds later kicks me off. Doing all this from inside the VPS always works. ---------------------------------------------------------------------- mechroCutie · 2019-08-19 05:57 this is officially outside my limited knowledge. with what yoube said though it sounds like the ssh connections are succeeding and mystic just doesnt know what to do after. the only help i can provide past this is to be a rubber ducky. im cute tho so im good at that (> 3 <) ---------------------------------------------------------------------- HrBingR · 2019-08-19 20:40 So for one, port forwarding has nothing to do with Mystic itself, and typically needs to be done on a router/firewall if your VPS/network is behind a NAT. That being said, based on what you've mentioned here regarding telnet working from a custom port and SSH on a custom port at least giving you a login prompt, your VPS is not behind a NAT and thus does not require any port forwarding. Only place I could think to check is the Mystic config itself, could be it's not allowing external connections for whatever reason. Check the following parts of the config for the SSH server in Mystic that could be blocking you: >**Auto IP Ban**: >This option will automatically BAN an IP if they connect to a server more than X times in X seconds. The default recommendation is 4 connections in 120 seconds. Setting either of the values to a zero will disable this feature. Refer also to the IP Blocks + Exceptions and Edit IP Blacklist and Edit IP Whitelist sections of the Wiki. >**Country Block**: >Use IP2Location country blocking? Options are 'Yes' or 'No'. >**Dupe IP Limit**: >Set the maximum number of allowed connections per IP address. A setting of 0 will disable this limit. Also make sure that your IPv4 and 6 adapter interfaces are set as follows: * IPv4: 0.0.0.0 * IPV6: :: Disclaimer: Not too familiar with Mystic, or BBS software in general, just understand networking to a finer degree than the average joe. If you need more help troubleshooting this, drop me a PM. ---------------------------------------------------------------------- inop76 · 2019-08-21 02:54 Thanks. I tried the above changes and I still have the issue. I've spent too much time on trying to get this to work so I decided to give EnigmaBBS a try and after I've set up the ssh server on it (on the same 8022 port) it worked right away so I know there was no issues with firewalls, etc. when I was tring to get Mystic to work. Thanks for your help