So I'm trying to setup my home server that is accessible from the Internet. I have created my Web site in ASP and configured my IIS. It works great on my local machine AND other computers on the local network can access it. I want to make it online, so that it can be accessed from elsewhere. I created an account on DynDns, and configured it to redirect the requests to my Internet IP. Then, I configured my router to forward all the incoming requests on port 80 to my local IP address, on which my Web site runs. However, when I go to my DynDns address, it redirects me to my router's home page instead. I have disabled my firewall (I know, not a good idea, it's just for testing purposes) but still no success. Does anyone have any idea what could be going wrong? I have a SMCWBR14S-N4 if that helps.
I've heard of some routers that have reserved port 80 for there configuration pages. I think the general work around there is to run your webserver on a non-standard port like 8080, but I don't have a whole lot of experience with this, so it could be something else entirely. :)
Update: For any future readers, always remember to test your external address and port forwarding on a computer outside of the network the server is on.
Related
I have a server that has both Apache and IIS running simultaneously.
Both apps are configured on different ports and both apps use HTTPS.
The app on Apache (port 433) is accessible on any computer on the network, but I can't get the IIS app (port 4433) to work. It says: This site can’t be reached
I can ping the server.
I'm trying to access both websites with IP address of the server and port after it.
The IIS app works on the server, both with localhost address and server IP address.
I have tried all the solutions I found:
1. disabling firewall
2. allowing just the port I needed through the firewall
3. allowing anonymous access in IIS
4. different ports (4433, 7200...)
Nothing seems to work.
I will be grateful for any help.
I assume your IIS binding looks something like this:
Specifically, "All Unassigned" for the IP address, and no host name defined.
If that is what you have, then it sounds like a firewall problem. i.e. The traffic is not reaching your server.
The easiest way to check this is to turn off Apache and change the IIS binding to use port 443. If it works, then you know it's just the other port that doesn't work.
You can also use something like Wireshark to actually see if any traffic on port 4433 is making it to your server (you can use the filter tcp.port == 4433). If you don't see any traffic there even though you've made a request from another computer, then something is blocking it.
And when I say "firewall", I don't mean Windows Firewall. I mean either a router or dedicated firewall appliance that would need to be configured to allow traffic to that port.
Im trying to find a way to host a web server (flask app on raspberry pi) at home. The problem is that my apartment complex provides internet to me and so my public IP is that of the apartment router.
When I go to the public IP, instead of seeing my webpage, I see the login to my apartment's router. This is obviously because that router isn't set up to forward port 80 to my personal router.
I dont really feel comfortable asking the property manager to open forward all incoming port 80 traffic to me, nor do I think they would do it.
So what are my options here? How can I route the traffic from my webpage to just my router?
Thanks!
Let's be clear: if you are behind a router, it needs to be configured to redirect port to your computer. That is the purpose of a router. And the first benefit is that it protects you against outside attacks.
So you have 2 options:
1. ask who ever manage the router to configure redirection (maybe you could ask for another port than 80?)
2. deploy your web-server on the cloud
Otherwise, maybe you could get another internet connection (wireless?)
I am attempting to spin up an application that listens on a port and responds to HTTP requests. I am on a Windows 8 machine connecting through a Netgear router that provides port forwarding. I have:
modified my DNS zone file of one of my domains to point to the IP address that is assigned to my cable modem
Added a port-forwarding rule to my router that sends requests to port 8080 to port 8081 on my computer
Opened port 8081 on my Windows Firewall
Executed netsh http add urlact http://+:8081/ user=Everyone listen=yes as administrator
Started up my app which uses the simple webserver solution found at http://codehosting.net/blog/BlogEngine/post/Simple-C-Web-Server.aspx which uses an HttpListener object with a prefix of http://+:8081/.
From any machine on my local network, I can browse to http://home.example.com:8080/blah/blah and everything works great. Whenever I attempt the same URL from a machine connected elsewhere on the Internet, the connection times out. I have tried using the IP address instead the domain name, and have tried disabling my Windows Firewall (temporarily), still with no luck.
I'm sure this is more of a network setup issue than a code issue, but I thought I would ask anyway to see if there is anything I can do. Sorry for the spaces in the urls above. This is my first post to SO, and I apparently don't have enough of a reputation to post more than a single link.
By "elsewhere on the Internet", I am assuming you are attempting to access it from a different ISP.
The thing about some ISPs is that unless you are paying for a "business class" connection, they will do all sorts of tricks to ensure that you remain a "consumer". What you need is an unNATed static IP address.
By this I mean that the IP address that you may have at your home may not be accessible to the outside world because the ISP is actually NATing (or other) that address to you. This is a fairly common practice because of limited IP4 addresses. If you really want a service accessible via the WWW, I would suggest moving your product to a VPN, or at least a commodity hosting provider.
Edit: Try a VPN service like Hamachi
The premise is this;
We have a piece of hardware, bought by a consumer with no technical skill. This hardware runs a web server, hosting a simple web site. This web site needs to be reachable even if it's sitting behind a home router firewall. How could this be solved? The connection doesn't strictly have to go over port 80 to the web server, some forwarding could be in the equation too, if needed.
How would you solve this?
There are a number of things that normally need to happen for a web server to be accessible from the internet:
Network firewall - allow traffic on port 80 or 443 to the server
Server firewall - Proper pin holes or turn it off.
Web server - Bind all IP/hostnames properly
You can control the server firewall and the web server, what you need to get around is the network firewall. One way I have seen this done is by creating a site to site VPN between the web server and your location. You then point your firewall to redirect the traffic over the VPN and the web server that is now accessible from the internet, but all traffic does go through you.
With out adding entries to your clients firewalls or giving the web server a public IP this is not possible.
This should be easy step, but there is no guidance, and my installation is turning into a week-long nightmare.
How do i configure Wordpress on NAS so that the website I create is visible on public internet through my domain mysite.com?
At the moment, I can only access my website through http://192.168.1.169/wordpress/
This is pointless, since I won't be able to invite public into my house, just too see my website. So there has to be a better way....
ports 80/5000 on my router are enabled via Synology's EZ-internet app
WebStation has virtualhost defined that points to my mysite.com at no-ip.com
At no-ip. I defined as target MY IP, which I obtained by Googling "what's my public IP" from within my home network.
when i enter mysite.com in browser, I am prompted to login to my ROUTER?!?!?! Why? I should be seeing my website developed on my Synology NAS, and I am not!
I cannot believe there are no user guides for this! And I cannot believe that noone knows how to do this!
No Youtube videos, no forums, no answers???
Extremely frustrated....
You seem to have figured out the route just fine. If you're seeing the loginpage for your router, then two things may be happening:
Did you use http or httpS for your website address? The latter uses port 443 by default. I don't think you did, but I'll had to ask.
The router is currently configured to handle port 80 traffic for its logon page (which is scary in its own right; a router login page should not be accessible from internet). In this case the router should be configured to forward port 80 to port 80 on your Synology. Apparently EZ Internet did not do a good job configuring the port forwards for you, or the router is overriding these settings.
You would need to log into your router and find your wan ip. Then you substitute that into your address supplied above. 192.168.1.169 is an internal ip for your network.
This will only work though if you have set up port forwarding on your router to your NAS.
And port forwarding only works if you have assigned a static ip to your NAS using DHCP and your NAS mac address.
Also worth investigating is if your router provides a DMZ (de militarized zone). Putting your NAS in the DMZ can increase security for the rest of your network that you want to keep hidden.
A little late but maybe this still can help others.
step 1: Set your port forwarding right (like the above suggestions). Port 80 and 443 should be open on your router and forwarded to your (fixed) internal IP address of your NAS.
step 2: check with https://canyouseeme.org/ or a similar site if the ports are "really open". (was not the case for me when I checked)
step 3: enable webstation and check if you can access the web landing page of your Synology by entering your DNS (from outside your LAN)
if all this works there is an important
step 4: go to your Wordpress dashboard->settings->general
Adapt the site URL to use the DNS you have provided with "/wordpress" or another sub- domain.
Now you should be able to access it from outside
good luck