Skip to content
This repository has been archived by the owner on Aug 7, 2020. It is now read-only.

error starting the tcp server on ports #160

Open
jaaabir opened this issue May 19, 2020 · 0 comments
Open

error starting the tcp server on ports #160

jaaabir opened this issue May 19, 2020 · 0 comments

Comments

@jaaabir
Copy link

jaaabir commented May 19, 2020

note: i am running it as root user
even if i stop the apache server and run the responder its giving me the same error:

[!] Error starting TCP server on port 80, check permissions or other servers running.
[!] Error starting SSL server on port 443, check permissions or other servers running.
[!] Error starting TCP server on port 445, check permissions or other servers running.
[!] Error starting TCP server on port 139, check permissions or other servers running.
[!] Error starting UDP server on port 88, check permissions or other servers running.
[!] Error starting TCP server on port 88, check permissions or other servers running.
[!] Error starting TCP server on port 1433, check permissions or other servers running.
[!] Error starting TCP server on port 21, check permissions or other servers running.
[!] Error starting TCP server on port 110, check permissions or other servers running.
[!] Error starting TCP server on port 389, check permissions or other servers running.
[!] Error starting TCP server on port 25, check permissions or other servers running.
[!] Error starting TCP server on port 143, check permissions or other servers running.
[!] Error starting TCP server on port 587, check permissions or other servers running.
[!] Error starting UDP server on port 53, check permissions or other servers running.
[+] Listening for events...
[!] Error starting TCP server on port 53, check permissions or other servers running.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant