github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #989] cannot listen for clients: cannot bind address: Address already in use #788

New issue

Closed

opened 2026-05-05 07:07:34 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 07:07:34 -06:00

Owner

Originally created by @apfaffman on GitHub (Dec 13, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/989

Hello, everyone.

Barrier v 2.3.3 on Fedora 33.

Can't get Barrier running as a server. The logs report the following when trying to start the service:

[2020-12-12T18:34:32] ERROR: cannot listen for clients: cannot bind address: Address already in use
[2020-12-12T18:34:32] DEBUG: retry in 1 seconds
[2020-12-12T18:34:33] ERROR: cannot listen for clients: cannot bind address: Address already in use
[2020-12-12T18:34:33] DEBUG: retry in 1 seconds
[2020-12-12T18:34:34] DEBUG: retry in 1 seconds
[2020-12-12T18:34:34] ERROR: cannot listen for clients: cannot bind address: Address already in use

This is with SSL enabled or disabled on default port 24800.

Seems like there's a simple fix here I'm missing. Anyone know?

Originally created by @apfaffman on GitHub (Dec 13, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/989 Hello, everyone. Barrier v 2.3.3 on Fedora 33. Can't get Barrier running as a server. The logs report the following when trying to start the service: [2020-12-12T18:34:32] ERROR: cannot listen for clients: cannot bind address: Address already in use [2020-12-12T18:34:32] DEBUG: retry in 1 seconds [2020-12-12T18:34:33] ERROR: cannot listen for clients: cannot bind address: Address already in use [2020-12-12T18:34:33] DEBUG: retry in 1 seconds [2020-12-12T18:34:34] DEBUG: retry in 1 seconds [2020-12-12T18:34:34] ERROR: cannot listen for clients: cannot bind address: Address already in use This is with SSL enabled or disabled on default port 24800. Seems like there's a simple fix here I'm missing. Anyone know?

gitea-mirror closed this issue

2026-05-05 07:07:37 -06:00

gitea-mirror commented

2026-05-05 07:07:43 -06:00

Author

Owner

@albertony commented on GitHub (Dec 13, 2020):

First guess would be that another instance of barrier server is already running, for some reason.

Have you checked that?

pidof barriers

Or, some other process could be already bound to that port?

sudo netstat -tlpn | grep ':24800'

@albertony commented on GitHub (Dec 13, 2020): First guess would be that another instance of barrier server is already running, for some reason. Have you checked that? `pidof barriers` Or, some other process could be already bound to that port? `sudo netstat -tlpn | grep ':24800'`

gitea-mirror commented

2026-05-05 07:07:46 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

Indeed, this seems to be most likely another instance of Barrier. We can't work around this, I'm thus closing the issue.

Please reopen if further investigation (e.g. by executing commands suggested here https://github.com/debauchee/barrier/issues/989#issuecomment-744002178) results in a different cause being uncovered.

@p12tic commented on GitHub (Jan 10, 2021): Indeed, this seems to be most likely another instance of Barrier. We can't work around this, I'm thus closing the issue. Please reopen if further investigation (e.g. by executing commands suggested here https://github.com/debauchee/barrier/issues/989#issuecomment-744002178) results in a different cause being uncovered.

gitea-mirror commented

2026-05-05 07:07:51 -06:00

Author

Owner

@YKX-RL commented on GitHub (Feb 27, 2024):

The reason is that address is already in use. Use "ps aux | grep synergys" to find process id, then kill all of them. After that restart synergy. For more details, please check the address of this website "https://superuser.com/questions/1217379/synergy-error-message-cannot-listen-for-clients-cannot-bind-address-address-a".

@YKX-RL commented on GitHub (Feb 27, 2024): The reason is that address is already in use. Use "ps aux | grep synergys" to find process id, then kill all of them. After that restart synergy. For more details, please check the address of this website "https://superuser.com/questions/1217379/synergy-error-message-cannot-listen-for-clients-cannot-bind-address-address-a".

No labels

Rows
Columns