This should solve your issue with finding ports almost every single time. On most linux distribution you can use the much more robust nstat -a from iproute2. Netstat is a command that displays information about TCP connections on your device. On windows you can do this by firing up the application and then opening up the command prompt and running the command netstat -a -b. If you are unable to find any documentation or it doesn't appear to be working you can search your active connections. If you get a response you can narrow it down that the issue is somewhere on the source or that is not the port you need. In all linux distribution you can use the identical command telnet 149.154.167.197 443. So on a window server I'd fire up the command prompt and try telnet 149.154.167.197 443. It doesn't matter if they have a telnet server setup or not, you can verify that the destination is valid. My preferred method and I truly believe is one of the easiest way is to try and telnet to the host on that port. Once you get this port information you usually do a test to see if my device can even reach said listener. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.īy default that means we’re knocking at your door on port 443 Other ports are not supported and will not work. We currently support the following ports: 443, 80. In your specific example the google results shows the following: Ī webhook needs an open port on your server. You can usually find a list ports, IPs, FQDN by simply googling, "what ports does use". Most applications usually have documentations what needs to be enabled to allow the application to work. I am not very familiar with telegram so this is from the perspective of an administrator doing general troubleshooting for ports.
0 Comments
Leave a Reply. |