Can I set up a HTTP server using my IP?
closed account (EwCjE3v7)
I do not understand your question. Do you mean have a donain point at ur IP?
Like www.test.com to go to ur ip?
If yes then yes u can. However u will need to buy ur domain. U can get a free domain at dot.tk
,however they end in .tk And not .com
Otherwise if you mean setup a website(http). Yees yes u can however u will need to port forward(port 80 default))
Like www.test.com to go to ur ip?
If yes then yes u can. However u will need to buy ur domain. U can get a free domain at dot.tk
,however they end in .tk And not .com
Otherwise if you mean setup a website(http). Yees yes u can however u will need to port forward(port 80 default))
Last edited on
I don't need a domain name. People can just target your IP address.
As XpertHamm0r kind of said, if you don't havean a public IP address dedicated to this server, you will need to set up port forwarding on your router so traffic destined for port 80 to your house will be redirected to your privately addressed server.
If this doesn't make sense to you, read up on NAT and how it applies to consumer Internet service.
As XpertHamm0r kind of said, if you don't have
If this doesn't make sense to you, read up on NAT and how it applies to consumer Internet service.
Last edited on
| As XpertHamm0r kind of said, if you don't have an IP address dedicated to this server, you will need to set up port forwarding on your router so traffic destined for port 80 to your house will be redirected to your privately addressed server. |
I think you misunderstood me, which means the OP probably did as well.
Assuming OP is talking about running a web server out of his house, he very likely only has one IP address which serves his whole house, and traffic is redirected to individual devices via NAT(PAT).
If OP wants to allow outside addresses to initiate connections to the webserver, then some port forwarding is going to have to happen, as the server is going to have a private address, and the router will need to know to redirect port 80 (or whatever OP wants to run it on) traffic to that private address. This has nothing to do about static addressing, besides OP will need his server to have some static address.
If OP has two connections to his house, he can just have one connection (public IP address) for his server and not have to worry about port forwarding, because he won't be dealing with NAT.
Assuming OP is talking about running a web server out of his house, he very likely only has one IP address which serves his whole house, and traffic is redirected to individual devices via NAT(PAT).
If OP wants to allow outside addresses to initiate connections to the webserver, then some port forwarding is going to have to happen, as the server is going to have a private address, and the router will need to know to redirect port 80 (or whatever OP wants to run it on) traffic to that private address. This has nothing to do about static addressing, besides OP will need his server to have some static address.
If OP has two connections to his house, he can just have one connection (public IP address) for his server and not have to worry about port forwarding, because he won't be dealing with NAT.
To get around the static IP problem there are some free services. I use no-ip to access my pc. I got a lame domain name but it's free.
Last edited on
Thank you all. I meant port 80. How can I set up my "IP website"? Example: where should I put an index file to the visitors?
You should install a web server software first, like Apache, nginx, etc.
As you most likely use windows, you can install something that do all the job for you, like VertrigoServ:
http://vertrigo.sourceforge.net/
It installs Apache, Mysql, Php and setup everything for you automatically, including firewall settings.
As you most likely use windows, you can install something that do all the job for you, like VertrigoServ:
http://vertrigo.sourceforge.net/
It installs Apache, Mysql, Php and setup everything for you automatically, including firewall settings.
@ OP: Anytime you have an outward facing machine like this it is good practice to put it on it's own sub net. This is a function of your router and what it does is prevent that machine from seeing any other devices at your site by putting that device on it's own mini-network. I would also suggest that you set your router to explicitly deny access to it's interface from this device through both wireless and wired connections. This one may or may not be practical and can easily become more trouble then it is worth from an administration stand point but it is still a good security practice to consider. Since this device will need an internal static IP anyway then restricting the IP range on that sub net might be something else to consider, but again this is one of those things that might not be worth the effort to implement since it really only throws up a road block in the event that another device tries to join that network.
There are some other good practices to consider, things like only running the services that the device needs to host your site and ensuring that all of the automatic updates for those services are set to Auto. But I'm thinking that the package that modoran suggested probably auto-configs a lot of that for you anyway.
There are some other good practices to consider, things like only running the services that the device needs to host your site and ensuring that all of the automatic updates for those services are set to Auto. But I'm thinking that the package that modoran suggested probably auto-configs a lot of that for you anyway.
So I installed VertrigoServ. If I type localhost on the browser I can access the VertrigoServ default page. How can I change it, now?
Right click on VertrigoServ icon, then go to "www folder" there. All the files accesible via web must be put there.
To change default page you either:
- change DirectoryIndex directive in a .htaccess file to point to the desired file
- change index.php file directly
For more informations see Apache documentation.
To change default page you either:
- change DirectoryIndex directive in a .htaccess file to point to the desired file
- change index.php file directly
For more informations see Apache documentation.
Topic archived. No new replies allowed.