listening port with netcat not working
I am trying to listen to port 8080 using netcat. It was working fine, suddenly I an getting this. Any idea?
root@kali:~# nc -vv -l -p 8080
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
netcat
asked Jan 9 at 20:31
Rahi RRahi R
1033
migrated from security.stackexchange.com Jan 13 at 21:48
This question came from our site for information security professionals.
add a comment |
I am trying to listen to port 8080 using netcat. It was working fine, suddenly I an getting this. Any idea?
root@kali:~# nc -vv -l -p 8080
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
netcat
asked Jan 9 at 20:31
Rahi RRahi R
1033
migrated from security.stackexchange.com Jan 13 at 21:48
This question came from our site for information security professionals.
add a comment |
I am trying to listen to port 8080 using netcat. It was working fine, suddenly I an getting this. Any idea?
root@kali:~# nc -vv -l -p 8080
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
netcat
asked Jan 9 at 20:31
Rahi RRahi R
1033
I am trying to listen to port 8080 using netcat. It was working fine, suddenly I an getting this. Any idea?
root@kali:~# nc -vv -l -p 8080
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
retrying local 0.0.0.0:8080 : Address already in use
netcat
netcat
asked Jan 9 at 20:31
Rahi RRahi R
1033
asked Jan 9 at 20:31
Rahi RRahi R
1033
asked Jan 9 at 20:31
Rahi RRahi R
1033
asked Jan 9 at 20:31
Rahi RRahi R
1033
asked Jan 9 at 20:31
Rahi RRahi R
1033
1033
migrated from security.stackexchange.com Jan 13 at 21:48
This question came from our site for information security professionals.
migrated from security.stackexchange.com Jan 13 at 21:48
This question came from our site for information security professionals.
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Some other process is using the port. use ps command to find the list of running processes it would list the list of active processes and also command name. Find and kill the process responsible for using the port 8080.
add a comment |
TL;DR This means another service is using that port, and only one service at a time can use that port. Could be your web browser, proxy, or a couple other possibilities. You can use netstat -an | grep 8080 to see what else is running on that port.
Try listening on another port, such as 4444.
Port 8080 is usually reserved as a sort of secondary HTTP port, or for web proxies (e.g. Burp Suite).
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
add a comment |
Doesn't that mean that this port is currently used, try
netstat -antp
to see what is using the port 8080
using other port may help you to not enter in other problems
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393901%2flistening-port-with-netcat-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Some other process is using the port. use ps command to find the list of running processes it would list the list of active processes and also command name. Find and kill the process responsible for using the port 8080.
add a comment |
Some other process is using the port. use ps command to find the list of running processes it would list the list of active processes and also command name. Find and kill the process responsible for using the port 8080.
add a comment |
Some other process is using the port. use ps command to find the list of running processes it would list the list of active processes and also command name. Find and kill the process responsible for using the port 8080.
Some other process is using the port. use ps command to find the list of running processes it would list the list of active processes and also command name. Find and kill the process responsible for using the port 8080.
answered Jan 10 at 6:41
holloman5756
add a comment |
add a comment |
TL;DR This means another service is using that port, and only one service at a time can use that port. Could be your web browser, proxy, or a couple other possibilities. You can use netstat -an | grep 8080 to see what else is running on that port.
Try listening on another port, such as 4444.
Port 8080 is usually reserved as a sort of secondary HTTP port, or for web proxies (e.g. Burp Suite).
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
add a comment |
TL;DR This means another service is using that port, and only one service at a time can use that port. Could be your web browser, proxy, or a couple other possibilities. You can use netstat -an | grep 8080 to see what else is running on that port.
Try listening on another port, such as 4444.
Port 8080 is usually reserved as a sort of secondary HTTP port, or for web proxies (e.g. Burp Suite).
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
add a comment |
TL;DR This means another service is using that port, and only one service at a time can use that port. Could be your web browser, proxy, or a couple other possibilities. You can use netstat -an | grep 8080 to see what else is running on that port.
Try listening on another port, such as 4444.
Port 8080 is usually reserved as a sort of secondary HTTP port, or for web proxies (e.g. Burp Suite).
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
TL;DR This means another service is using that port, and only one service at a time can use that port. Could be your web browser, proxy, or a couple other possibilities. You can use netstat -an | grep 8080 to see what else is running on that port.
Try listening on another port, such as 4444.
Port 8080 is usually reserved as a sort of secondary HTTP port, or for web proxies (e.g. Burp Suite).
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
answered Jan 9 at 20:38
SomeGuySomeGuy
1214
1214
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
add a comment |
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
Yes, it was Brup Suite. Thanks a lot
– Rahi R
Jan 10 at 0:17
add a comment |
Doesn't that mean that this port is currently used, try
netstat -antp
to see what is using the port 8080
using other port may help you to not enter in other problems
add a comment |
Doesn't that mean that this port is currently used, try
netstat -antp
to see what is using the port 8080
using other port may help you to not enter in other problems
add a comment |
Doesn't that mean that this port is currently used, try
netstat -antp
to see what is using the port 8080
using other port may help you to not enter in other problems
Doesn't that mean that this port is currently used, try
netstat -antp
to see what is using the port 8080
using other port may help you to not enter in other problems
answered Jan 13 at 21:35
Mobrine Hayde
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393901%2flistening-port-with-netcat-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
