Webpage can not get access from the world!Don't see apache running in netstatFirewall configuration and consequencesSimple port forwardingHow to make php webpage to access the file in /root directory?apache2 on ubuntu 14 - localhost works but ip doesn'tHow to access multiple webpage on Ubuntu 16.04 webserver from Local area networkxampp- unable to start apache on ubuntu 16Trying to open port on Ubuntu 18.04 Server - I'm missing something
Will arranging a song in piano increase my overall arrangement ability?
Expressing the Riemann Zeta function in terms of GCD and LCM
What is the moral difference between abortion and infanticide?
I don't feel like creating this riddle today
Could earthquake cancellation work?
GeoServer parametric SQL view. ERROR: function key(boolean) does not exist
"Government transplant" been tried? At what scale, and what were the results?
Being overqualified as a barrier for getting a job
Was I wrong to rebutt unjustified rewiewer comments in the review?
Can this crack in the steel chain-side Dropout be WELDED?
Putting tools you use (but can't configure) on resume?
Upper management wants me to stay longer after last day. Can I renegotiate?
What can Scotland legally do to get independence?
Which floor is the Hogwarts Library on?
On a large transport aircraft where exactly is the Forward pressure bulkhead?
Is it advisable to cover and uncover the clarinet mouthpiece to play each note?
Find elements of array with largest absolute value
Senate Impeachment rule change?
Why has Trump refused to recognize the Armenian Genocide?
find ".ts" but not ".d.ts"
How Much Would a Language Change Over 500 Years Completely Cut Off From Its Source?
As of 2019, why do mountaineering courses still teach how to use a paper map?
Is there a difference between LASSO regularisation and LASSO penalisation?
Modeling in pure math
Webpage can not get access from the world!
Don't see apache running in netstatFirewall configuration and consequencesSimple port forwardingHow to make php webpage to access the file in /root directory?apache2 on ubuntu 14 - localhost works but ip doesn'tHow to access multiple webpage on Ubuntu 16.04 webserver from Local area networkxampp- unable to start apache on ubuntu 16Trying to open port on Ubuntu 18.04 Server - I'm missing something
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I have installed a fresh Apache with a fresh Ubuntu server. I did not make any changes to my server yet. The default Apache website is visible from other PCs inside the private network.
The ports 80 and 22 are forwarded properly to the server, and I have setup a fixed IP DHCP 192.168.10.116 from my router.
SSH is accessible from public or private network. But the website is only accessible from the private network. I would like to make the website available to the world.
Note that I have tried this setup with a Windows PC + XAMMP, from which the default Apache webpage had been visible from a public IP.
Below are some details:
mg@node1:~$ sudo ufw status
Status: inactive
mg@node1:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
mg@node1:~$ cat /etc/apache2/ports.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
mg@node1:~$ sudo netstat -nptl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 702/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 780/sshd
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 1039/sshd: mg@pts/0
tcp6 0 0 :::80 :::* LISTEN 2340/apache2
tcp6 0 0 :::22 :::* LISTEN 780/sshd
tcp6 0 0 ::1:6010 :::* LISTEN 1039/sshd: mg@pts/0
mg@node1:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 node1
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
mg@node1:~$ curl http://192.168.10.116
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML ... ...
mg@node1:~$ curl http://43.xxx.xxx.95
curl: (7) Failed to connect to 43.xxx.xxx.95 port 80: Connection refused
apache2 iptables firewall webserver port-forwarding
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
|
show 9 more comments
I have installed a fresh Apache with a fresh Ubuntu server. I did not make any changes to my server yet. The default Apache website is visible from other PCs inside the private network.
The ports 80 and 22 are forwarded properly to the server, and I have setup a fixed IP DHCP 192.168.10.116 from my router.
SSH is accessible from public or private network. But the website is only accessible from the private network. I would like to make the website available to the world.
Note that I have tried this setup with a Windows PC + XAMMP, from which the default Apache webpage had been visible from a public IP.
Below are some details:
mg@node1:~$ sudo ufw status
Status: inactive
mg@node1:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
mg@node1:~$ cat /etc/apache2/ports.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
mg@node1:~$ sudo netstat -nptl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 702/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 780/sshd
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 1039/sshd: mg@pts/0
tcp6 0 0 :::80 :::* LISTEN 2340/apache2
tcp6 0 0 :::22 :::* LISTEN 780/sshd
tcp6 0 0 ::1:6010 :::* LISTEN 1039/sshd: mg@pts/0
mg@node1:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 node1
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
mg@node1:~$ curl http://192.168.10.116
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML ... ...
mg@node1:~$ curl http://43.xxx.xxx.95
curl: (7) Failed to connect to 43.xxx.xxx.95 port 80: Connection refused
apache2 iptables firewall webserver port-forwarding
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
3
You might want to check with your ISP if they block port 80.
– Terrance
Oct 2 at 13:28
@Terrance The ports are unblocked and from windows10+xammp the website was available through port 80. But I am so confused, why its not working in ubuntu+apache2.
– MJC
Oct 2 at 13:33
1
ChangeListen 0.0.0.0:80to simplyListen 80and report back.
– AlexP
Oct 2 at 14:27
1
@Terrance >> You might want to check with your ISP if they block port 80. You are right I check with the other port such 8017 its works fine except 80. Contacted with the ISP to unblock it. Thank you again.
– MJC
Oct 3 at 9:39
1
@Terrance I am scared to say that my the port forwarding rules was incorrect with the Mikrotik(except the 8017 port), after correct it the website is visible to the world. Thank you all!
– MJC
Oct 7 at 11:53
|
show 9 more comments
I have installed a fresh Apache with a fresh Ubuntu server. I did not make any changes to my server yet. The default Apache website is visible from other PCs inside the private network.
The ports 80 and 22 are forwarded properly to the server, and I have setup a fixed IP DHCP 192.168.10.116 from my router.
SSH is accessible from public or private network. But the website is only accessible from the private network. I would like to make the website available to the world.
Note that I have tried this setup with a Windows PC + XAMMP, from which the default Apache webpage had been visible from a public IP.
Below are some details:
mg@node1:~$ sudo ufw status
Status: inactive
mg@node1:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
mg@node1:~$ cat /etc/apache2/ports.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
mg@node1:~$ sudo netstat -nptl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 702/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 780/sshd
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 1039/sshd: mg@pts/0
tcp6 0 0 :::80 :::* LISTEN 2340/apache2
tcp6 0 0 :::22 :::* LISTEN 780/sshd
tcp6 0 0 ::1:6010 :::* LISTEN 1039/sshd: mg@pts/0
mg@node1:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 node1
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
mg@node1:~$ curl http://192.168.10.116
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML ... ...
mg@node1:~$ curl http://43.xxx.xxx.95
curl: (7) Failed to connect to 43.xxx.xxx.95 port 80: Connection refused
apache2 iptables firewall webserver port-forwarding
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
I have installed a fresh Apache with a fresh Ubuntu server. I did not make any changes to my server yet. The default Apache website is visible from other PCs inside the private network.
The ports 80 and 22 are forwarded properly to the server, and I have setup a fixed IP DHCP 192.168.10.116 from my router.
SSH is accessible from public or private network. But the website is only accessible from the private network. I would like to make the website available to the world.
Note that I have tried this setup with a Windows PC + XAMMP, from which the default Apache webpage had been visible from a public IP.
Below are some details:
mg@node1:~$ sudo ufw status
Status: inactive
mg@node1:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
mg@node1:~$ cat /etc/apache2/ports.conf
Listen 80
<IfModule ssl_module>
Listen 443
</IfModule>
<IfModule mod_gnutls.c>
Listen 443
</IfModule>
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
mg@node1:~$ sudo netstat -nptl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 702/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 780/sshd
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN 1039/sshd: mg@pts/0
tcp6 0 0 :::80 :::* LISTEN 2340/apache2
tcp6 0 0 :::22 :::* LISTEN 780/sshd
tcp6 0 0 ::1:6010 :::* LISTEN 1039/sshd: mg@pts/0
mg@node1:~$ cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 node1
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
mg@node1:~$ curl http://192.168.10.116
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML ... ...
mg@node1:~$ curl http://43.xxx.xxx.95
curl: (7) Failed to connect to 43.xxx.xxx.95 port 80: Connection refused
apache2 iptables firewall webserver port-forwarding
apache2 iptables firewall webserver port-forwarding
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
edited Oct 2 at 14:47
MJC
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
asked Oct 2 at 13:12
MJCMJC
313 bronze badges
313 bronze badges
3
You might want to check with your ISP if they block port 80.
– Terrance
Oct 2 at 13:28
@Terrance The ports are unblocked and from windows10+xammp the website was available through port 80. But I am so confused, why its not working in ubuntu+apache2.
– MJC
Oct 2 at 13:33
1
ChangeListen 0.0.0.0:80to simplyListen 80and report back.
– AlexP
Oct 2 at 14:27
1
@Terrance >> You might want to check with your ISP if they block port 80. You are right I check with the other port such 8017 its works fine except 80. Contacted with the ISP to unblock it. Thank you again.
– MJC
Oct 3 at 9:39
1
@Terrance I am scared to say that my the port forwarding rules was incorrect with the Mikrotik(except the 8017 port), after correct it the website is visible to the world. Thank you all!
– MJC
Oct 7 at 11:53
|
show 9 more comments
3
You might want to check with your ISP if they block port 80.
– Terrance
Oct 2 at 13:28
@Terrance The ports are unblocked and from windows10+xammp the website was available through port 80. But I am so confused, why its not working in ubuntu+apache2.
– MJC
Oct 2 at 13:33
1
ChangeListen 0.0.0.0:80to simplyListen 80and report back.
– AlexP
Oct 2 at 14:27
1
@Terrance >> You might want to check with your ISP if they block port 80. You are right I check with the other port such 8017 its works fine except 80. Contacted with the ISP to unblock it. Thank you again.
– MJC
Oct 3 at 9:39
1
@Terrance I am scared to say that my the port forwarding rules was incorrect with the Mikrotik(except the 8017 port), after correct it the website is visible to the world. Thank you all!
– MJC
Oct 7 at 11:53
3
3
You might want to check with your ISP if they block port 80.
– Terrance
Oct 2 at 13:28
You might want to check with your ISP if they block port 80.
– Terrance
Oct 2 at 13:28
@Terrance The ports are unblocked and from windows10+xammp the website was available through port 80. But I am so confused, why its not working in ubuntu+apache2.
– MJC
Oct 2 at 13:33
@Terrance The ports are unblocked and from windows10+xammp the website was available through port 80. But I am so confused, why its not working in ubuntu+apache2.
– MJC
Oct 2 at 13:33
1
1
Change
Listen 0.0.0.0:80 to simply Listen 80 and report back.– AlexP
Oct 2 at 14:27
Change
Listen 0.0.0.0:80 to simply Listen 80 and report back.– AlexP
Oct 2 at 14:27
1
1
@Terrance >> You might want to check with your ISP if they block port 80. You are right I check with the other port such 8017 its works fine except 80. Contacted with the ISP to unblock it. Thank you again.
– MJC
Oct 3 at 9:39
@Terrance >> You might want to check with your ISP if they block port 80. You are right I check with the other port such 8017 its works fine except 80. Contacted with the ISP to unblock it. Thank you again.
– MJC
Oct 3 at 9:39
1
1
@Terrance I am scared to say that my the port forwarding rules was incorrect with the Mikrotik(except the 8017 port), after correct it the website is visible to the world. Thank you all!
– MJC
Oct 7 at 11:53
@Terrance I am scared to say that my the port forwarding rules was incorrect with the Mikrotik(except the 8017 port), after correct it the website is visible to the world. Thank you all!
– MJC
Oct 7 at 11:53
|
show 9 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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/4.0/"u003ecc by-sa 4.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%2faskubuntu.com%2fquestions%2f1178138%2fwebpage-can-not-get-access-from-the-world%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1178138%2fwebpage-can-not-get-access-from-the-world%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
3
You might want to check with your ISP if they block port 80.
– Terrance
Oct 2 at 13:28
@Terrance The ports are unblocked and from windows10+xammp the website was available through port 80. But I am so confused, why its not working in ubuntu+apache2.
– MJC
Oct 2 at 13:33
1
Change
Listen 0.0.0.0:80to simplyListen 80and report back.– AlexP
Oct 2 at 14:27
1
@Terrance >> You might want to check with your ISP if they block port 80. You are right I check with the other port such 8017 its works fine except 80. Contacted with the ISP to unblock it. Thank you again.
– MJC
Oct 3 at 9:39
1
@Terrance I am scared to say that my the port forwarding rules was incorrect with the Mikrotik(except the 8017 port), after correct it the website is visible to the world. Thank you all!
– MJC
Oct 7 at 11:53