Disable port (external) - IpTables/firewall issue
I am having a Docker container with SOLR (0.0.0.0:8984->8983/tcp) and would like to deny the "8984" Port for external request.
The Server is a Plesk Onyx 17.8.11 Update #35 with Ubuntu 16.04. The Domain: HOSTNAME.net:8984
returns results even while setting the firewall against this.
# iptables -L:
Chain INPUT (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
Chain FORWARD (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
DROP tcp -- 0.0.0.0 anywhere tcp dpt:8984
DROP tcp -- anywhere 0.0.0.0 tcp dpt:8984
DROP all -- anywhere anywhere
Any Idea how to check if the rule is active or what is wrong with the setting. My goal is to deny the port 8984 for external request but leave it active for localhost (127.0.0.1). Firewall is active.
firewall iptables ubuntu-14.04 plesk
add a comment |
I am having a Docker container with SOLR (0.0.0.0:8984->8983/tcp) and would like to deny the "8984" Port for external request.
The Server is a Plesk Onyx 17.8.11 Update #35 with Ubuntu 16.04. The Domain: HOSTNAME.net:8984
returns results even while setting the firewall against this.
# iptables -L:
Chain INPUT (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
Chain FORWARD (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
DROP tcp -- 0.0.0.0 anywhere tcp dpt:8984
DROP tcp -- anywhere 0.0.0.0 tcp dpt:8984
DROP all -- anywhere anywhere
Any Idea how to check if the rule is active or what is wrong with the setting. My goal is to deny the port 8984 for external request but leave it active for localhost (127.0.0.1). Firewall is active.
firewall iptables ubuntu-14.04 plesk
add a comment |
I am having a Docker container with SOLR (0.0.0.0:8984->8983/tcp) and would like to deny the "8984" Port for external request.
The Server is a Plesk Onyx 17.8.11 Update #35 with Ubuntu 16.04. The Domain: HOSTNAME.net:8984
returns results even while setting the firewall against this.
# iptables -L:
Chain INPUT (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
Chain FORWARD (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
DROP tcp -- 0.0.0.0 anywhere tcp dpt:8984
DROP tcp -- anywhere 0.0.0.0 tcp dpt:8984
DROP all -- anywhere anywhere
Any Idea how to check if the rule is active or what is wrong with the setting. My goal is to deny the port 8984 for external request but leave it active for localhost (127.0.0.1). Firewall is active.
firewall iptables ubuntu-14.04 plesk
I am having a Docker container with SOLR (0.0.0.0:8984->8983/tcp) and would like to deny the "8984" Port for external request.
The Server is a Plesk Onyx 17.8.11 Update #35 with Ubuntu 16.04. The Domain: HOSTNAME.net:8984
returns results even while setting the firewall against this.
# iptables -L:
Chain INPUT (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
Chain FORWARD (policy DROP)
DROP tcp -- anywhere anywhere tcp dpt:8984
DROP tcp -- 0.0.0.0 anywhere tcp dpt:8984
DROP tcp -- anywhere 0.0.0.0 tcp dpt:8984
DROP all -- anywhere anywhere
Any Idea how to check if the rule is active or what is wrong with the setting. My goal is to deny the port 8984 for external request but leave it active for localhost (127.0.0.1). Firewall is active.
firewall iptables ubuntu-14.04 plesk
firewall iptables ubuntu-14.04 plesk
edited Jan 18 at 8:16
Ahmed Ashour
1,3251715
1,3251715
asked Jan 18 at 7:55
FrancisFrancis
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I would not bother with iptables
in this case; when specifying the forwarding of the port, don't use 0.0.0.0 as the IP address; instead use 127.0.0.1:8984 -> 8983/tcp. Now only localhost access will work.
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%2f1395651%2fdisable-port-external-iptables-firewall-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would not bother with iptables
in this case; when specifying the forwarding of the port, don't use 0.0.0.0 as the IP address; instead use 127.0.0.1:8984 -> 8983/tcp. Now only localhost access will work.
add a comment |
I would not bother with iptables
in this case; when specifying the forwarding of the port, don't use 0.0.0.0 as the IP address; instead use 127.0.0.1:8984 -> 8983/tcp. Now only localhost access will work.
add a comment |
I would not bother with iptables
in this case; when specifying the forwarding of the port, don't use 0.0.0.0 as the IP address; instead use 127.0.0.1:8984 -> 8983/tcp. Now only localhost access will work.
I would not bother with iptables
in this case; when specifying the forwarding of the port, don't use 0.0.0.0 as the IP address; instead use 127.0.0.1:8984 -> 8983/tcp. Now only localhost access will work.
answered Jan 18 at 10:50
wurtelwurtel
1,19447
1,19447
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%2f1395651%2fdisable-port-external-iptables-firewall-issue%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