Tahoe on AWS

[Sameer Verma]

On Thu, Dec 18, 2014 at 9:11 PM, Sameer Verma <sverma at sfsu.edu> wrote:
> On Thu, Dec 18, 2014 at 8:27 PM, Sameer Verma <sverma at sfsu.edu> wrote:
>> On Thu, Dec 18, 2014 at 7:30 PM, David Stainton <dstainton415 at gmail.com>
>> wrote:
>>> Hi Sameer,
>>>
>>> You need to set (in the node section) the "tub.location" configuration
>>> parameter.
>>> Here's the details:
>>> https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/configuration.rst
>>>
>
> Am I setting the tub.location for both introducer and storage servers?
> I have my introducer running (green) but storage servers show as red
> saying "Connected to 0 of 3 known storage servers"

Never mind. I got it. I changed the tub.port and tub.location on the
storage servers and it shows up as green now.

Sameer
>
> cheers,
> Sameer
>>
>> Thanks!
>>
>>> And... if you are in San Francisco then come to by Tahoe-LAFS
>>> cryptoparty tomorrow night at noisebridge!
>>> https://www.cryptoparty.in/sanfrancisco
>>>
>>
>> Oh sweet! I'll reschedule some stuff and try to be there.
>>
>> cheers,
>> Sameer
>>
>>> Cheers,
>>>
>>> David Stainton
>>>
>>>
>>> On Fri, Dec 19, 2014 at 3:21 AM, Sameer Verma <sverma at sfsu.edu> wrote:
>>>> Hi,
>>>>
>>>> I'm trying to set up a system of 1 introducer and 10 storage nodes on
>>>> AWS, plus one client on my laptop. The introducer sets up, but when I
>>>> run it, the introducer.furl always reflects the internal IP that AWS
>>>> assigns and not the public IP. Is there a way around this?
>>>>
>>>> Also, apart from port 3456 TCP, what ports do I need to open on the
>>>> introducer and the storage nodes?
>>>>
>>>> cheers,
>>>> Sameer
>>>> _______________________________________________
>>>> tahoe-dev mailing list
>>>> tahoe-dev at tahoe-lafs.org
>>>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev