[tahoe-dev] [tahoe-lafs] #536: port number conflict: 8123 is (or was) used by polipo and is blocked by TorButton

[tahoe-lafs]

#536: port number conflict: 8123 is (or was) used by polipo and is blocked by
TorButton
-----------------------------------+----------------------------------------
     Reporter:  zooko              |       Owner:          
         Type:  defect             |      Status:  reopened
     Priority:  major              |   Milestone:  1.3.0   
    Component:  code-frontend-web  |     Version:  1.2.0   
   Resolution:                     |    Keywords:          
Launchpad_bug:                     |  
-----------------------------------+----------------------------------------

Comment(by warner):

 I don't think we've come to a resolution on this. I don't know how to
 justify switching *to* a port that is assigned by IANA.

 I've observed three different deployment scenarios that are affected by
 the choice of default port. The first is a single user giving Tahoe a try
 at home (our developer community). This user tends to run a single node,
 and intends to use its webapi. I think these users would most benefit from
 a low-effort path to their Tahoe node listening on a webport that matches
 what the documentation uses in its examples.

 The second is me, when I build a local test grid, with multiple nodes on a
 single machine. I am often surprised by the fact that N-1 of these nodes
 fail at startup, because they all defaulted to the same webport, and only
 the first node started was able to claim it. I added the "--webport none"
 option to make this easier for me to set up, but in fact I usually forget
 and have to go back and edit the node configs (usually to disable the
 webport on all but one node).

 The third is allmydata (as represented by Zandr) when we set up a new
 webapi node on our commercial grid. In some cases, these nodes are fronted
 by an HTTP load-balancing proxy. In others, they live on a round-robin DNS
 name. In the latter case, it is important that all the nodes listen on the
 same port, so we advertise HOST:8123 (and have customer-side tools which
 embed that base URL). The round-robin DNS case obligates us to only run
 one webapi node per ip address, of course.

 I'm not worried so much about the continuing allmydata.com rollout: it's a
 simple matter to add the appropriate --webport argument to the scripts we
 use when creating these nodes. I'm more concerned about an apparently
 gratuitous change which will bring the (new) docs into conflict with
 existing user's (old) nodes.

 That said, I'm not feeling as strongly about this change as I was a week
 ago. Maybe I'm just desperate to get this release out :).

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/536#comment:9>
tahoe-lafs <http://allmydata.org/>
secure decentralized file storage grid