So, now I have two options, either use a different port for my API (which is troublesome, as the port is hardcoded into the Android app I use the API for), or figure this out. I don't think I have any firewall blocking it, because I ran service iptables status and it says rvice not running. I sshd into the box, and ran nc -zv localhost 8083 and got a connection successful message. Almost all other ports work, except 8083. Strangely, changing the port in my API, recompiling it and running it works perfectly. Port Protocol Zimbra Service Description 25 : smtp : mta : incoming mail to postfix 80 : http : mailbox / proxy : web mail client (disabled by default in 8.0) 110 : pop3. I tried to connect to that port using nc -zv host port but it hangs up as well. Now whenever I try to connect to my API, the connection times out. On my DO server, I have bound my API to port 8083, and it was working normally until today. Multiple hours were wasted on this problem, hours that I won't get back. While I'm happy that I found out what was causing my problem, I'm disappointed in DO that they did not contact their users to inform them about this. The IP address returned should be the IP (public or private) of your MTA. The mail domain that your user accounts are created under must have an MX record. Thanks again to everyone who helped me out.I opened a ticket with DO and was informed that they'd automatically closed port 8083 due to the VestaCP vulnerability which allowed root access to droplets. For mail to flow inbound, servers on the internet need to connect to your MTA on port 25. I dont think I have any firewall blocking it, because I ran service iptables status and it says rvice not running. I ssh d into the box, and ran nc -zv localhost 8083 and got a connection successful message. Can you recommend any newby-friendly resource where I can learn how to go about this and what should I block? Or should I just go with something like this: ? Strangely, changing the port in my API, recompiling it and running it works perfectly. gresponderdelay Delay between responses to the same address. gquotabeforeforward Do quota check before forwarding. gpopfetchkick POPfetch will try and open the link for 10 seconds, then retry, this should bring up ISDN lines. Now I will have to set up the firewall again because the command I ran looks like having completely wiped the iptables. gpopminskip Skip ip addresses matching this list. I managed to crack into the console from the vps control panel (a terrible, terrible java app that barely took my keyboard input) and disabled the firewall altogether running service iptables stop so that I was able to access the console via ssh with the terminal. There was a firewall not controlled by the WHM software. I have been wandering through all the settings and options in WHM for several hours now, but can't seem to find anything.ĭoes anybody have a clue as to where I should start investigating? This problem is more serious in older versions of Windows, say XP (which you should not use either). There seem to be no firewall in WHM and I have whitelisted my home IP address to access ssh, though there were no restrictions in the first place. The typical situation is: you 'click on something', Windows appears to be frozen, and after several seconds (or minutes, if you are really lucky :-), the (un)famous message appears: surgemail.exe is not responding and will be terminated. I also tried to access with the hostname instead of the IP address and it's the same. Ssh: connect to host xx.xx.xxx.xxx port 22: Operation timed out When trying to connect with ssh via Terminal I only get this: So, I'm stuck in WHM and have no way to access the configuration of the machine, neither via ssh nor with ftp/sftp. Port 21 is, but I am not able to access the machine via ftp (I think it's a security measure, but I don't know where to disable/enable it). Making a port scan I see that port 22 is not responding. You know it: the longer you own your computer, the slower it runs and the more often it stucks. How to handle damaged file: surgemail.exe is corrupted. Strangely, changing the port in my API, recompiling it and running it works perfectly. Use the keyword disabled to disable this part of the SurgeMail service. Typical Windows message: surgemail.exe high cpu. gmanagersecureport - Manager secure port (default 143) This should be the main server management port and provides a secure server management connection. Sshd is running (it appears in the current running processes). Solve problems with surgemail.exe not responding. I'm trying to make the jump to VPS from shared hosting for better performances and greater flexibility, but am stuck with the fact that I can't access the machine via ssh.įirst of all, the machine is a CentOS 6.3 cPanel 圆4 with WHM 11.38.0.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |