I want to run a Python Flask app with a Raspberry Pi. The pi is connected through a router. Thus the Flask web app can be viewed from other devices connected to the router. However, my raspberry pi IP address is 192.168.1.145 and the app runs with this URL 192.168.1.145:5000. I would give a meaningful hostname to the raspberry pi like flaskserver:5000 and make it accessible to other devices connected to the same router as pi.
I have tried the following steps-
In flask app my code is
app.config['SERVER_NAME'] = 'flaskserver:5000' app.run(host = '192.168.1.145', port = 5000, debug=True, use_reloader=False)
I have added this line to my /etc/hosts
192.168.1.145. flaskserver
That did not work. So I tried -
127.0.0.1 flaskserver
I have also tried the following code for my flask server -
app.config['SERVER_NAME'] = 'flaskserver:5000' app.run(host = 'flaskserver', port = 5000, debug=True, use_reloader=False)
I am making a lot of trial and error with the configurations. So far nothing has worked.
Any advice would be appreciated.
Thank you.
I would try a reverse proxy such as nginx to expose your application to port 80. Then change the host file to whatever you want.
Related
Device: Raspberry Pi 2 Model B
OS: Raspbian Stretch ( no desktop ) with static ip
Router: Belkin F9K1103
DNS service: Hosting on Norwegian version of domainnameshop.com
Greetings. I'm in the process of setting up my Pi as a server. The current motive is to be able to ssh into the device from another network and host a Git server on it.
It works great at home using the local ip address, but when it comes to port forwarding port 22, NOTHING works... I've tried for at least 10 hours combined, scavenging the internet for solutions on this topic, rasbian / raspberry related port forwarding or general. Nothing seems to work. I've tried everything it seems, and no matter what i do the tests show that the port is CLOSED.
I'm currently port forwarding the Pi's local ip and port 22 on the networks port 22 ( also tried port 3322 to the pi's port 22 ) on BOTH the router and the modem using the internet provider's own service for port forwarding online ( Telenor ). The Pi is connected with an ethernet cable, and I've tried connecting it to both the router and the modem when doing all the tests. I've also tried to add 'Port 22' and 'Port 3322' in the Pi's SSH configuration file.
I've also tried to use a DNS service in which I'm forwarding my home network's ip address but still no luck.
Can anybody please help me before I go insane? I'm I missing something crucial? I can't count on both my hands how many forum posts I've been reading and guides on both raspberry or general port forwarding..
Ok so I found out what was wrong.
Our modem is quite new and advanced, and the internet provider has their own online admin panel for it with its own port forwarding solution and what not. So this was apparently a case of classic double NAT conflict. The router tries to port forward to the modem which would normally just bridge that onto the web, but the modem is in a sense being port forwarded too by the internet provider and it's own services.
What I had to do was reverting the static IP configs on the Pi, unplug it from the wifi router, then plug it directly to the modem and then port forward it using our internet providers online admin panel for the modem.
Now it works brilliantly.
Okay, here's the situation I am in. I have a raspberry Pi 2 model B. I have Raspbain Jessie installed as the OS. I have Apache installed as well. I have a web server running and i am able to edit it and access the site from different devices on different internet connections. I want to be able to connect to my RaspPi through SSH on my MacBook Pro. I am able to do this while on the same network. My Pi is plugged into the router via an Ethernet. What i have tried is, logging into my router and reserving an IP for my Pi, i also entered my MAC address here. I have gone into the port forwarding options in my router and have it set up as: HTTP, TCP, Server address(the one i reserved) my Ipv6, and Start port 80, end port 80. Ontop of that i have gone into my /etc/dhcpcd.conf file. There at the end of the file i added
interface eth0
static ip_address=10.0.0.100
static routers=10.0.0.1
static domain_name_servers=68.44.180.118 2001:558:feed::1 2001:558:feed::2
The guide I followed is attached here and follows other guides i have seen.
http://www.circuitbasics.com/how-to-set-up-a-static-ip-on-the-raspberry-pi/
Yet when i try to SSH remotely i cannot get a connection, and when i connect on the same internet i can connect as normal. Please if anybody sees what could help .
Your router's firewall is probably blocking the ports for SSH, which does not use port 80 (in raspbian, I think its default is port 22). If you are going to take the risk of leaving your SSH open to the public, you should probably switch it to a different port other than the default before opening up a port on your firewall. The Raspbian Community has a thread on how to properly change SSH's default server port. You'll also need to make sure your SSH client is using the same port. You will need to leave 80 open for web, and also forward the SSH port, which ever you choose that to be (22 is the default).
I don't have a ton of experience with routers or port forwarding, but I do have a new Raspberry Pi and I wanted to see if I could set up a simple Hello World page just for educational purposes. I have quite a bit set up with apache2 already installed and the web page works great on my local area network, however I can't connect to it using my LTE from my phone, telling me this thing does not connect to the internet.
I am currently using Rasbian under all the default settings from the pi.
My router is an all in one modem and router, from xfinity. After sifting through countless sites trying to solve this issue, the following 2 were the closest thing to my particular issue. My reputation is not high enough to put more than 2 links, so I will put the most important ones..
So to the best of my knowledge this is the way to do it ...
1) Set the web server up to work locally
2) Then go into the router with the IPv4 or IPv6 (shouldn't matter which) and forward all Port 80 traffic to, say, Port 8080 where my PI 'should' be listening, then send back my web page down through Port 80 to the client calling the web page.
Under 10.0.0.1 I find this...
Then I go to 'Advanced'
I have tried from Start port 80 to End port 8080, which my 2 PI files I edited to listen for that port.
Those files are under
sudo nano /ect/apache2/sites-enabled-000-default.conf
and
sudo nano /ect/apache2/ports.conf
I changed
Listen 80
to
Listen 8080
and all other combinations alongside changing my router Start and End ports... none of which worked so I am lead to believe there is either a knowledge gap or I am doing something terribly wrong.
I just want to put a simply Raspberry pi web server online from my Local connection at home using a Comcast xfinity router. If anyone has any experience doing, I would seriously appreciate it, I've spent far too many hours trying to walk through this alone, so now I am reaching out to the faithful stackoverflow community.
It sounds like you are almost there.
For you to be able to access your raspberry pi server from the internet, you need to find your external ip address. Your router has one external ip address that you can reach from the internet. While on your wifi, search google for "what is my ip" Google may display it as the top result, or you might have to click into a site like ipchicken. Write this IP address down.
Next, setup your router to forward all port 80 (default http port). Try setting Apache to listen on port 80, and have your router set with start port and end port to be port 80 (this makes it so you don't have to put :port-number in the address, i.e. you will do http://your-ip-address rather than http://your-ip-address:8080). The start port is the port on the external network, the end is the port that your Apache server is running on the raspi.
It looks like your raspi has the ip address of 10.0.0.17 on your local network based on your screen shot. If it doesn't, change the IP address in the port forwarding section of the router configuration to be the IP address of your pi. You can figure out what the assigned IP address of your pi is through the router interface, or by typing ifconfig -a and looking for the ip address of the adapter that you're using to connect to the network. Your router may have the ability to assign a static ip address to your raspberry pi while it's connected to your network. It would say something like DHCP reservation. You'd need to find the MAC address of your pi. You can do that with ifconfig -a as well. Then configure your modem to always assign your pi the same ip address that you've configured in the port forwarding.
Now that everything is setup, switch to your cellular connection and then try to go to the ipaddress that Google gave you.
type your-ip in browser address bar -> port 80 request to your modem's IP -> you've set external port 80 requests to be forwarded to port 80 on your internal network for the device 10.0.0.17 -> your raspberry pi will serve the HTML
Note: The external ip address of your modem is most likely not static unless you specifically pay for a static address. This address usually will stay the same for at least a day though, so if you're just testing, it's not a big problem. In the future, if you want to ensure that you'll be able to reach your pi, look into dynamic dns.
I have installed XAMPP to run Apache server on windows,So the Apache server run great on LAN (Local Area Network ).
But i need to run the server ,so the public can access it from WAN
(Wide Area Network) .
I have forward HTTP port 80 on 4G portable router ,but no device can access the Apache server from Public (WAN)
** I have tried DDNS solutions also with no success.
The issue is most likely the 4g network itself. It seems they don't allow servers to wait on their network.
We have a set of machines in a datacenter. Only one of the machines is accessible from the internet-world. If we need to talk to any other machine in the datacenter we would need to login to this internet-visible machine.
We have a monitoring web-tool which monitors all the servers. For this to work I needed the browser to be in the same lan as datacenter. I made this possible by using dynamic-forwarding a port from my local machine to the world visible machine and set this port as the proxy on my browser .. this worked fine.
Now I wanted to use some command-line tools which needed to talk to all the machines in the datacenter. The only way I could make that work was to login to world-visible machine and run my commands from there.
After looking around on the web, I discovered(could be wrongly) that I can use tsocks to achieve the goal of running my command line tools on my local machine as-if they are running in the datacenter network. However, I am having trouble getting them work. I am attaching the tsocks.conf file I created
local = 192.168.81.0/255.255.255.0
local = 0.0.0.0/255.255.255.255
path {
reaches = 192.168.5.0/255.255.255.0
server = 0.0.0.0
server_port = 8080
server_type = 5
}
path {
reaches = 10.125.4.0/255.255.255.0
server = 0.0.0.0
server_port = 8081
server_type = 5
}
path {
reaches = 10.110.80.0/255.255.255.0
server = 0.0.0.0
server_port = 8082
server_type = 5
}
I have all the three server_ports mentioned above dynamically-forwarded using ssh and I am able to use each of them as a proxy for my browser with no trouble to access machines on each of the three datacenters but doing
. tsocks -on
and pinging one of the machines does not give me any response.. It does not look like my set up is working... can somebody help?
Sorry for the wrong question. Everything was working fine. I was trying to ping a server in the network which was configured not to respond to pings at all. Other operations such as ssh work fine. So the proxy was setup properly. just the way I was testing was wrong.
Thanks,
Sunil.