Port Forwarding stops working after several minutes
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I am currently having issues with port forwarding.
I've got a raspberry pi with Ubuntu 16.04 installed, it's running apache and ftp servers.
I've configured a static ip for my system and configured my router to forward the outside requests to port 80, 22 and 21 in order to access my servers and use SSH from outside networks.
It worked fine until recently, now the port forwarding just randomly stops working after several minutes.
The changes to NAT settings I've made are still present in the router admin page and I can still access my web-servers or perform remote control from LAN using the same IP address, however trying to perform these actions from outside networks using my router's public ip simply results in error 110 and connection timeout.
Rebooting the router does no good, however rebooting the system itself actually temporarily resolves the issue.
I don't know what could be causing this problem and how to fix this, the only changes I've made recently were enabling ssl, redirecting all http requests to https and setting password for apache.
I've reverted all the changes already, however the issue still persists.
Is there anything that can be done besides reinstalling Ubuntu completely? Is it even the problem with the device itself or is it the router that's causing the issue?
networking raspberrypi port-forwarding
edited Jun 7 at 10:00
cmak.fr
1,529918
asked Jun 7 at 7:37
MaroonedMind
1
add a comment |Â
up vote
0
down vote
favorite
I am currently having issues with port forwarding.
I've got a raspberry pi with Ubuntu 16.04 installed, it's running apache and ftp servers.
I've configured a static ip for my system and configured my router to forward the outside requests to port 80, 22 and 21 in order to access my servers and use SSH from outside networks.
It worked fine until recently, now the port forwarding just randomly stops working after several minutes.
The changes to NAT settings I've made are still present in the router admin page and I can still access my web-servers or perform remote control from LAN using the same IP address, however trying to perform these actions from outside networks using my router's public ip simply results in error 110 and connection timeout.
Rebooting the router does no good, however rebooting the system itself actually temporarily resolves the issue.
I don't know what could be causing this problem and how to fix this, the only changes I've made recently were enabling ssl, redirecting all http requests to https and setting password for apache.
I've reverted all the changes already, however the issue still persists.
Is there anything that can be done besides reinstalling Ubuntu completely? Is it even the problem with the device itself or is it the router that's causing the issue?
networking raspberrypi port-forwarding
edited Jun 7 at 10:00
cmak.fr
1,529918
asked Jun 7 at 7:37
MaroonedMind
1
Have you forwarded https (tcp 443) port too ? you may check the destination ip of forwarders
– cmak.fr
Jun 7 at 8:06
Yes, I did. And I don't think that could be the problem because I've disabled the https protocol already, plus ftp and ssh can't be accessed from outside too.
– MaroonedMind
Jun 7 at 10:47
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am currently having issues with port forwarding.
I've got a raspberry pi with Ubuntu 16.04 installed, it's running apache and ftp servers.
I've configured a static ip for my system and configured my router to forward the outside requests to port 80, 22 and 21 in order to access my servers and use SSH from outside networks.
It worked fine until recently, now the port forwarding just randomly stops working after several minutes.
The changes to NAT settings I've made are still present in the router admin page and I can still access my web-servers or perform remote control from LAN using the same IP address, however trying to perform these actions from outside networks using my router's public ip simply results in error 110 and connection timeout.
Rebooting the router does no good, however rebooting the system itself actually temporarily resolves the issue.
I don't know what could be causing this problem and how to fix this, the only changes I've made recently were enabling ssl, redirecting all http requests to https and setting password for apache.
I've reverted all the changes already, however the issue still persists.
Is there anything that can be done besides reinstalling Ubuntu completely? Is it even the problem with the device itself or is it the router that's causing the issue?
networking raspberrypi port-forwarding
edited Jun 7 at 10:00
cmak.fr
1,529918
asked Jun 7 at 7:37
MaroonedMind
1
I am currently having issues with port forwarding.
I've got a raspberry pi with Ubuntu 16.04 installed, it's running apache and ftp servers.
I've configured a static ip for my system and configured my router to forward the outside requests to port 80, 22 and 21 in order to access my servers and use SSH from outside networks.
It worked fine until recently, now the port forwarding just randomly stops working after several minutes.
The changes to NAT settings I've made are still present in the router admin page and I can still access my web-servers or perform remote control from LAN using the same IP address, however trying to perform these actions from outside networks using my router's public ip simply results in error 110 and connection timeout.
Rebooting the router does no good, however rebooting the system itself actually temporarily resolves the issue.
I don't know what could be causing this problem and how to fix this, the only changes I've made recently were enabling ssl, redirecting all http requests to https and setting password for apache.
I've reverted all the changes already, however the issue still persists.
Is there anything that can be done besides reinstalling Ubuntu completely? Is it even the problem with the device itself or is it the router that's causing the issue?
networking raspberrypi port-forwarding
edited Jun 7 at 10:00
cmak.fr
1,529918
asked Jun 7 at 7:37
MaroonedMind
1
edited Jun 7 at 10:00
cmak.fr
1,529918
edited Jun 7 at 10:00
cmak.fr
1,529918
edited Jun 7 at 10:00
cmak.fr
1,529918
1,529918
asked Jun 7 at 7:37
MaroonedMind
1
asked Jun 7 at 7:37
MaroonedMind
1
asked Jun 7 at 7:37
MaroonedMind
1
1
Have you forwarded https (tcp 443) port too ? you may check the destination ip of forwarders
– cmak.fr
Jun 7 at 8:06
Yes, I did. And I don't think that could be the problem because I've disabled the https protocol already, plus ftp and ssh can't be accessed from outside too.
– MaroonedMind
Jun 7 at 10:47
add a comment |Â
Have you forwarded https (tcp 443) port too ? you may check the destination ip of forwarders
– cmak.fr
Jun 7 at 8:06
Yes, I did. And I don't think that could be the problem because I've disabled the https protocol already, plus ftp and ssh can't be accessed from outside too.
– MaroonedMind
Jun 7 at 10:47
Have you forwarded https (tcp 443) port too ? you may check the destination ip of forwarders
– cmak.fr
Jun 7 at 8:06
Have you forwarded https (tcp 443) port too ? you may check the destination ip of forwarders
– cmak.fr
Jun 7 at 8:06
Yes, I did. And I don't think that could be the problem because I've disabled the https protocol already, plus ftp and ssh can't be accessed from outside too.
– MaroonedMind
Jun 7 at 10:47
Yes, I did. And I don't think that could be the problem because I've disabled the https protocol already, plus ftp and ssh can't be accessed from outside too.
– MaroonedMind
Jun 7 at 10:47
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
I discovered that it was sshguard causing the problem by blocking all requests from my public ip address. Problem was solved by whitelisting the ip address.
answered Jun 7 at 21:10
MaroonedMind
1
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I discovered that it was sshguard causing the problem by blocking all requests from my public ip address. Problem was solved by whitelisting the ip address.
answered Jun 7 at 21:10
MaroonedMind
1
add a comment |Â
up vote
0
down vote
I discovered that it was sshguard causing the problem by blocking all requests from my public ip address. Problem was solved by whitelisting the ip address.
answered Jun 7 at 21:10
MaroonedMind
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
I discovered that it was sshguard causing the problem by blocking all requests from my public ip address. Problem was solved by whitelisting the ip address.
answered Jun 7 at 21:10
MaroonedMind
1
I discovered that it was sshguard causing the problem by blocking all requests from my public ip address. Problem was solved by whitelisting the ip address.
answered Jun 7 at 21:10
MaroonedMind
1
answered Jun 7 at 21:10
MaroonedMind
1
answered Jun 7 at 21:10
MaroonedMind
1
answered Jun 7 at 21:10
MaroonedMind
1
1
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1044396%2fport-forwarding-stops-working-after-several-minutes%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
Have you forwarded https (tcp 443) port too ? you may check the destination ip of forwarders
– cmak.fr
Jun 7 at 8:06
Yes, I did. And I don't think that could be the problem because I've disabled the https protocol already, plus ftp and ssh can't be accessed from outside too.
– MaroonedMind
Jun 7 at 10:47