[SOLVED] telegram-cli bind: Address already in use
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for your favorable reply. Yes apache is running on port 80. How can I fix this problem so that either telegram-cli listen on another port or share same port 80?
Only one server may use port 80 at a time (generic). If both services are restricted to a specific network, then the one service can use port 80 on one network, and the other service can use port 80 on a different network.
But both can't be active at one time.
Now you should be able to run a virtual machine to contain one of the services - thus that VM would get a different network address. Then both services can be active at one time on a physical system.
I dont know if this will work using containers (no experience there).
If you do, all clients that use that servervice must also use that alternate port.
for example - if you switched the web server to use port 8080 (common) every web browser must specify port 8080 to connect to the web server. I use the web server for the example because I've done that before.
You would have to look into the configuration of telegram to see if you can specify an alternate port though.
Actually telegram-cli is using port 80 but with opening a different socket. I was surfing and found that link http://stackoverflow.com/questions/1...sharing-a-port which states that many sockets can be opened on one port by many users.
Actually telegram-cli is using port 80 but with opening a different socket. I was surfing and found that link http://stackoverflow.com/questions/1...sharing-a-port which states that many sockets can be opened on one port by many users.
If this is true then how can I fix my problem
This is only true for a single service. No two services can use the same socket on the same network on the same system.
It is not true for any client. A client gets a random socket. If it gets an "already in use" error, it is supposed to try another socket.
And that is what is in your URL.
Telegram is an instant messaging service. A web server is not.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.