Originally Posted by Raakh5
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.
BTW, from https://github.com/vysheng/tg/wiki/T...m-CLI-Commands
telegram-cli starts the tg process, which I believe is the server... and that server listens on port 80, which is in use by your web server.
I did find https://github.com/vysheng/tg/wiki/R...-CLI-as-Daemon
which describes how to start telegram using an arbitrary port...
But any client that is going to connect must also use that same port number.