TileStache on AWS EC2
Raj
I am trying to run TileStache on AWS EC2.
Do you have any idea on which IP address I have to run TileSatche so
that I could get it to display in a url?
Because if I use their private IP address, though TileStache gives a
message of running successfully, I cannot get it to display tiles in a
url. And I cannot run it through their Public IP because its already
running an instance.
Any ideas would be appreciated!
-Thanks
Raj
Greg Allensworth
> I am trying to run TileStache on AWS EC2.
> Do you have any idea on which IP address I have to run TileSatche so
> that I could get it to display in a url?
I run TS via Apache and CGI. This allows me to run TS on port 80 and
also to serve other content -- using the EC2's public DNS name.
If you're trying to run TS via the WSGI Werkzeug service, and are seeing
that port 8080 is already in use, this means that something is already
using port 8080. You may want to check into that. If it's an existing TS
instance, and THAT's the one you want to connect to via browser, then
add :8080 to your URLs, e.g.:
http://12-34-56.amazon.com/
becomes
http://12-34-56.amazon.com:8080/
If neither of these answer your question, we should back up a bit and
ask how you're trying to run TS.
--
Greg Allensworth, Web GIS Developer
BS A+ Network+ Security+ Linux+ Server+
GreenInfo Network - Information and Mapping in the Public Interest
564 Market Street, Suite 510 San Francisco CA 94104
PH: 415-979-0343 x302 FX: 415-979-0371 email: gre...@greeninfo.org
Web: www.GreenInfo.org www.MapsPortal.org
Subscribe to MapLines, our e-newsletter, at www.GreenInfo.org
Arek Skalski
Chris Somerlot
I am having the same problem as the OP. I run TS using the Weurkeug service, on port 8080, with no other web services, on a windows AMI. I specify the port and IP via commandline flags as the elastic IP of my instance and port 8080, and I get site not found. If I try with localhost, works fine.
Arek Skalski
Chris Somerlot
I did. I tried both the IP listed in ipconfig and the elastic IP assigned by AWS. Neither work.. I get a socket error with the elastic IP and page not found with the other.
Arek Skalski
Chris Somerlot
What port would I need to open besides the one I specified, 8080?
Arek Skalski
Raj
So, I am trying to specify my private IP address & port (8080 or even
a different port). When I start TileStache using tilestache-server.py,
it says 'runing at that particular ip address & port' (I starting the
server file from a ssh client). I am assuming that private IP address
in AWS EC2 is connected with running instance(am I right?). Of course
in url I cant access using my private IP. So, I use my public IP(of
AWS) and specify the same port I used previously to run using private
IP. Then it says 'The server at xx.xx.xx.xx. is taking too long to
respond.'... ??
-Raj
On Apr 15, 5:35 am, Arek Skalski <askalsk...@gmail.com> wrote:
> 8080 seems to be enough. Have you enabled 8080 in AMI configuration? It
> needs to be set to be open for your IP. When you starder the tilestache on
> elastic IP did you try to access the tiles directly from the server? Maby
> the port isn't open for IP of machine you are testing on .
>
>
>
>
>
>
>
> > What port would I need to open besides the one I specified, 8080?
>
> >> hmm, maby you have some kind of firewall by your system? ports blocked by
> >> windows?
>
> >>> I did. I tried both the IP listed in ipconfig and the elastic IP
> >>> assigned by AWS. Neither work.. I get a socket error with the elastic IP
> >>> and page not found with the other.
>
>
> >>> > You can try -i IP option to specify address to listen on . Combine
> >>> with -p PORT to be fully custom :) Sometimes is good to read the manual.
>
Thiyagarajan
Raj