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?)
Related
I am using (airtel xstream fiber) connection and trying to do port forwarding. I forwarded port 3000 of wan and direct it to my system ip address 192.168.1.2 on port 3001.
Node server is running on my system on port 3001. And I can access my hello world website locally using 192.168.1.2:3001. But when I am trying to access using public ip, it show this error code "ERR_CONNECTION_TIMED_OUT".
Also, I found my router port 3001 is open using online port checking tool/website.
So, Can anyone please tell what could be reason behind this ? Is this the problem with windows.
You first need to check what ports are open by your ISP. If your ISP is giving you a local ip at the router. Basically, creating a ppp connection. It may be using a cg nat. In that case you need to buy a static ip, without that none of the traffic will be Directed to your router. Let me know if you find something, I'm currently looking to get xstream airtel as well.
No there is no need for static IP to be access server remotely. As of now, What I see is airtel allocates new ip every 24 hr or when router got disconnected. To access your server remotely you can do two things. First one is more secured.
Change Primary IP adress of your airtel router and use Portforwarding so that its port 80 will be free for you.
Enable DMZ and point it to your local server IP. [192.168.X.X]. In this case all of your ports of the device are exposed to internet. If you want to be secure. Make sure add another router between server and airtel router and enable port forwarding.
But in this case there is a catch, When you try to access your local website using public ip (which you can see on google search) it will redirect you to airtel router panel. But when you try to access it using other device (not server otherwise server will get disconnected) connected to internet using other network(other that your current airtel router like JIO sim, Airtel Sim, etc), It will work excellently.
To get rid of dynamic ip use no-ip services. Its website will help you more. Basically, It is dynamic dns server where you will get free domain. That will get update regularly while its service running on your system. To use other dns provider service like godaddy you must need an static ip.
There have been many articles on various forums on how to setup mcrosoft active directory domain services. I am a bit new to the field, so please bear with my ignorance. I have a very basic query whose answer i am not able to find. I have an office of 20 people where i would like to deploy AD Domain services to have a better control. i want to know how should i set my network PHYSICALLY. I have a router supplied by my internet provider. Where exactly should i put my server? Can i plug my server anyhere in the network and connect the users through domain, or the main internet wire should plug into the server first and the users in turn be connected to the server. enter image description here I hope i am clear. Should internet ‘flow’ from the server which has AD to users, or i can put the serverver anywhere in the topology.
In a small size network like yours, 1 server should be enough. It should be somewhere behind the router. Plugging it into the switch is fine as it will have a internal address.
You will need DNS on your server which will install when you promote to a DC. All of your computers need to look at your server for DNS. Your Server's DNS should have a forwarder to your ISP DNS or to a public DNS. It doesn't matter if you server or your router does DHCP so long as it gives out the server Internal IP for DNS.
What would I do:
I would plug your ISP into the Router, Your Router into your Switch, and all computers + server into the Switch.
You can place your server anywhere in the topology. It is not necessary for all user traffic to the internet to be routed through the server.
With small-scale deployments (less than 25 Users) I typically just put the server on the same switch and subnet as the users.
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
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.
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