I can't get my localhost website to go public on the internet (using Xampp and no-ip.com)
I am trying to host a website locally on my PC and publish it on the internet. I am using no-ip.com and I created a dns host called (for example) mydnshostname.ddns.com.
I altered my drivers/etc/hosts file and now when I hit localhost it goes directly to my site.
I also altered my httpd-vhosts.conf file on the apache and included this:
NameVirtualHost *:80
<VirtualHost *:80>
DocumentRoot "E:/xampp/htdocs/mydnshostname"
ServerName mydnshostname.ddns.com
</VirtualHost>
Now when I hit mydnshostname.ddns.com (from my computer) I get my website correctly.
But when I try to hit it from another PC I get server not found.
If the other PC is on another network then I can't find the website at all (of course)
If the other PC is on my network I can find it under 192.168.1.x (the ip of my desktop where I host it) but not when I hit mydnshostname.ddns.com.
Is there a setting that I'm missing? How can I publish it online?
xampp dynamic-dns
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
migrated from serverfault.com Jan 16 '15 at 0:51
This question came from our site for system and network administrators.
add a comment |
I am trying to host a website locally on my PC and publish it on the internet. I am using no-ip.com and I created a dns host called (for example) mydnshostname.ddns.com.
I altered my drivers/etc/hosts file and now when I hit localhost it goes directly to my site.
I also altered my httpd-vhosts.conf file on the apache and included this:
NameVirtualHost *:80
<VirtualHost *:80>
DocumentRoot "E:/xampp/htdocs/mydnshostname"
ServerName mydnshostname.ddns.com
</VirtualHost>
Now when I hit mydnshostname.ddns.com (from my computer) I get my website correctly.
But when I try to hit it from another PC I get server not found.
If the other PC is on another network then I can't find the website at all (of course)
If the other PC is on my network I can find it under 192.168.1.x (the ip of my desktop where I host it) but not when I hit mydnshostname.ddns.com.
Is there a setting that I'm missing? How can I publish it online?
xampp dynamic-dns
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
migrated from serverfault.com Jan 16 '15 at 0:51
This question came from our site for system and network administrators.
1
you need to redirect incomming http (por 80) traffic to your PC 192.168.1.X. This is usually done in your modem/router.
– Archemar
Jan 15 '15 at 21:41
add a comment |
I am trying to host a website locally on my PC and publish it on the internet. I am using no-ip.com and I created a dns host called (for example) mydnshostname.ddns.com.
I altered my drivers/etc/hosts file and now when I hit localhost it goes directly to my site.
I also altered my httpd-vhosts.conf file on the apache and included this:
NameVirtualHost *:80
<VirtualHost *:80>
DocumentRoot "E:/xampp/htdocs/mydnshostname"
ServerName mydnshostname.ddns.com
</VirtualHost>
Now when I hit mydnshostname.ddns.com (from my computer) I get my website correctly.
But when I try to hit it from another PC I get server not found.
If the other PC is on another network then I can't find the website at all (of course)
If the other PC is on my network I can find it under 192.168.1.x (the ip of my desktop where I host it) but not when I hit mydnshostname.ddns.com.
Is there a setting that I'm missing? How can I publish it online?
xampp dynamic-dns
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
I am trying to host a website locally on my PC and publish it on the internet. I am using no-ip.com and I created a dns host called (for example) mydnshostname.ddns.com.
I altered my drivers/etc/hosts file and now when I hit localhost it goes directly to my site.
I also altered my httpd-vhosts.conf file on the apache and included this:
NameVirtualHost *:80
<VirtualHost *:80>
DocumentRoot "E:/xampp/htdocs/mydnshostname"
ServerName mydnshostname.ddns.com
</VirtualHost>
Now when I hit mydnshostname.ddns.com (from my computer) I get my website correctly.
But when I try to hit it from another PC I get server not found.
If the other PC is on another network then I can't find the website at all (of course)
If the other PC is on my network I can find it under 192.168.1.x (the ip of my desktop where I host it) but not when I hit mydnshostname.ddns.com.
Is there a setting that I'm missing? How can I publish it online?
xampp dynamic-dns
xampp dynamic-dns
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
edited Nov 14 '18 at 17:10
JakeGould
31.1k1093137
31.1k1093137
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
asked Jan 15 '15 at 21:35
Panagiotis PalladinosPanagiotis Palladinos
10414
10414
migrated from serverfault.com Jan 16 '15 at 0:51
This question came from our site for system and network administrators.
migrated from serverfault.com Jan 16 '15 at 0:51
This question came from our site for system and network administrators.
1
you need to redirect incomming http (por 80) traffic to your PC 192.168.1.X. This is usually done in your modem/router.
– Archemar
Jan 15 '15 at 21:41
add a comment |
1
you need to redirect incomming http (por 80) traffic to your PC 192.168.1.X. This is usually done in your modem/router.
– Archemar
Jan 15 '15 at 21:41
1
1
you need to redirect incomming http (por 80) traffic to your PC 192.168.1.X. This is usually done in your modem/router.
– Archemar
Jan 15 '15 at 21:41
you need to redirect incomming http (por 80) traffic to your PC 192.168.1.X. This is usually done in your modem/router.
– Archemar
Jan 15 '15 at 21:41
add a comment |
2 Answers
2
active
oldest
votes
As for your other computer on the same network, you'll need to edit the 'hosts' file for name resolution...or set up your own internal DNS server, and point all of your PC's on that network to use the DNS server.
Sometimes routers have some DNS functionality...but the quickest way for local testing is just to make an entry in the /etc/hosts file. Assuming you have windows as your desktop, just do a search for how to edit the /etc/hosts file in windows (it can be done).
Archemar's comment is correct, you'll need to do port forwarding (via your router) for all incoming traffic on port 80 to be directed to the PC that you have running Apache.
Lastly, depending on your hosting OS, you will need to adjust your firewall settings on your webserver PC -- to allow in-coming the connections on 80.
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
add a comment |
Xammp does not allow access from public IP Addresses. I tried forwarding onto the public internet and it gave an error of only local access permitted.
You should get web hosting instead, I recommend the following companies:
- http://www.1and1.co.uk/
- https://godaddy.com/
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
1
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
2
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
add a comment |
protected by JakeGould Jul 4 '16 at 2:42
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
As for your other computer on the same network, you'll need to edit the 'hosts' file for name resolution...or set up your own internal DNS server, and point all of your PC's on that network to use the DNS server.
Sometimes routers have some DNS functionality...but the quickest way for local testing is just to make an entry in the /etc/hosts file. Assuming you have windows as your desktop, just do a search for how to edit the /etc/hosts file in windows (it can be done).
Archemar's comment is correct, you'll need to do port forwarding (via your router) for all incoming traffic on port 80 to be directed to the PC that you have running Apache.
Lastly, depending on your hosting OS, you will need to adjust your firewall settings on your webserver PC -- to allow in-coming the connections on 80.
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
add a comment |
As for your other computer on the same network, you'll need to edit the 'hosts' file for name resolution...or set up your own internal DNS server, and point all of your PC's on that network to use the DNS server.
Sometimes routers have some DNS functionality...but the quickest way for local testing is just to make an entry in the /etc/hosts file. Assuming you have windows as your desktop, just do a search for how to edit the /etc/hosts file in windows (it can be done).
Archemar's comment is correct, you'll need to do port forwarding (via your router) for all incoming traffic on port 80 to be directed to the PC that you have running Apache.
Lastly, depending on your hosting OS, you will need to adjust your firewall settings on your webserver PC -- to allow in-coming the connections on 80.
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
add a comment |
As for your other computer on the same network, you'll need to edit the 'hosts' file for name resolution...or set up your own internal DNS server, and point all of your PC's on that network to use the DNS server.
Sometimes routers have some DNS functionality...but the quickest way for local testing is just to make an entry in the /etc/hosts file. Assuming you have windows as your desktop, just do a search for how to edit the /etc/hosts file in windows (it can be done).
Archemar's comment is correct, you'll need to do port forwarding (via your router) for all incoming traffic on port 80 to be directed to the PC that you have running Apache.
Lastly, depending on your hosting OS, you will need to adjust your firewall settings on your webserver PC -- to allow in-coming the connections on 80.
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
As for your other computer on the same network, you'll need to edit the 'hosts' file for name resolution...or set up your own internal DNS server, and point all of your PC's on that network to use the DNS server.
Sometimes routers have some DNS functionality...but the quickest way for local testing is just to make an entry in the /etc/hosts file. Assuming you have windows as your desktop, just do a search for how to edit the /etc/hosts file in windows (it can be done).
Archemar's comment is correct, you'll need to do port forwarding (via your router) for all incoming traffic on port 80 to be directed to the PC that you have running Apache.
Lastly, depending on your hosting OS, you will need to adjust your firewall settings on your webserver PC -- to allow in-coming the connections on 80.
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
answered Jan 15 '15 at 21:48
Mike BroylesMike Broyles
262
262
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
add a comment |
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
The other thing you want to check is if your ISP allows for you to have your own web server out of your house (assuming you have a residential connection).
– Mike Broyles
Jan 15 '15 at 21:52
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
thanks! I ll try port forwarding tomorrow. I hope the isp allows it. as for my OS I have windows 7 here. I dont use any firewall other than the one from windows.
– Panagiotis Palladinos
Jan 15 '15 at 21:53
add a comment |
Xammp does not allow access from public IP Addresses. I tried forwarding onto the public internet and it gave an error of only local access permitted.
You should get web hosting instead, I recommend the following companies:
- http://www.1and1.co.uk/
- https://godaddy.com/
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
1
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
2
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
add a comment |
Xammp does not allow access from public IP Addresses. I tried forwarding onto the public internet and it gave an error of only local access permitted.
You should get web hosting instead, I recommend the following companies:
- http://www.1and1.co.uk/
- https://godaddy.com/
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
1
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
2
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
add a comment |
Xammp does not allow access from public IP Addresses. I tried forwarding onto the public internet and it gave an error of only local access permitted.
You should get web hosting instead, I recommend the following companies:
- http://www.1and1.co.uk/
- https://godaddy.com/
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
Xammp does not allow access from public IP Addresses. I tried forwarding onto the public internet and it gave an error of only local access permitted.
You should get web hosting instead, I recommend the following companies:
- http://www.1and1.co.uk/
- https://godaddy.com/
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
answered Jan 15 '15 at 21:45
Christopher TaylorChristopher Taylor
1
1
1
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
2
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
add a comment |
1
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
2
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
1
1
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
-1 for managing to recommend two horrible hosting companies. OP, whatever you do, avoid these two like the plague.
– EEAA
Jan 16 '15 at 1:26
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
Are you kidding me? I've used both of those, ITS MY OPINION. They are both FINE for ME. Its my recommendation end ok.
– Christopher Taylor
Jan 16 '15 at 22:16
2
2
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
Yep, it's your opinion. I will defend your right to express that until the day I die. I also have an opinion, which I expressed by down voting what I believe to be a bad recommendation. Others are free to vote as they see fit as well. Your answer is reason number X that product/service recommendations really don't work within the stack exchange mission.
– EEAA
Jan 16 '15 at 22:30
add a comment |
protected by JakeGould Jul 4 '16 at 2:42
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
you need to redirect incomming http (por 80) traffic to your PC 192.168.1.X. This is usually done in your modem/router.
– Archemar
Jan 15 '15 at 21:41