Opened 9 years ago

Closed 9 years ago

#394 closed defect (fixed)

Location of outproxy.h2ik.i2p changed to outproxy2.h2ik.i2p

Reported by: Eche|on Owned by: zzz
Priority: minor Milestone: 0.8.4
Component: apps/i2ptunnel Version: 0.8.3
Keywords: outproxy Cc: killyourtv@…, h2ik@…
Parent Tickets: Sensitive: no

Description

seems the https outproxy is dead.
remove it from the source conifg.

Subtickets

Change History (11)

comment:1 Changed 9 years ago by zzz

Is it gone for good, or is there a replacement? If so, please provide a link to some sort of authorized statement from the operator with the details.

Any change would only be for new installs.

comment:2 Changed 9 years ago by killyourtv

--- a/installer/resources/i2ptunnel.config
+++ b/installer/resources/i2ptunnel.config
@@ -124,7 +124,7 @@
 tunnel.6.sharedClient=true
 tunnel.6.interface=127.0.0.1
 tunnel.6.listenPort=4445
-tunnel.6.proxyList=outproxy.h2ik.i2p
+tunnel.6.proxyList=outproxy2.h2ik.i2p
 tunnel.6.i2cpHost=127.0.0.1
 tunnel.6.i2cpPort=7654
 tunnel.6.option.inbound.nickname=shared clients

Source: outproxy.h2ik.i2p address change & status.h2ik.i2p offline

I posted the duplicate ticket:395 for this (which I've closed).

comment:3 Changed 9 years ago by killyourtv

Cc: killyourtv@… added
Keywords: outproxy added
Priority: minortrivial
Resolution: fixed
Status: newclosed
Version: 0.8.20.8.3

comment:4 Changed 9 years ago by killyourtv

Summary: https outproxy vanished, remove from codeLocation of outproxy.h2ik.i2p changed to outproxy2.h2ik.i2p

comment:5 Changed 9 years ago by DISABLED

Resolution: fixed
Status: closedreopened

comment:6 Changed 9 years ago by DISABLED

Priority: trivialminor

latest disapproval of revision 'dbe319d674d6a6a53491762262978f53caaaa58a' unfixed it.
plus host.txt entry for the new outproxy.

comment:7 Changed 9 years ago by zzz

Component: otherapps/i2ptunnel
Resolution: fixed
Status: reopenedclosed

refixed, and added to hosts.txt

comment:8 Changed 9 years ago by h2ik

Cc: h2ik@… added
Resolution: fixed
Status: closedreopened

Sorry for the lateness of this. I should have opened a ticket against this last October when outproxy.h2ik.i2p died. As of Feb I've put up a new proxy called outproxyng.h2ik.i2p that is faster and is more favourable to my network setup (less hops, no transparent proxy, no tor, etc). The forum entry is here. I'll be sunsetting outproxy2 once 0.8.4 is out.

Also, neon.i2p is another https outproxy service which is setup much the same as outproxy2 so if you'd like to kill a few birds, you can add that one as well. I've created a list of all the active outproxies here

Thanks

comment:9 Changed 9 years ago by h2ik

So, far, clarity,

tunnel.6.proxyList=outproxyng.h2ik.i2p,neon.i2p

comment:10 Changed 9 years ago by zzz

Status: reopenedaccepted

Thanks, I'll do this before the release.

re: neon -

I would like to see more outproxies in the default configs, both for HTTP and CONNECT.

We don't really have a process, but for sure, the person running the outproxy needs to make the request.

In addition, we really need to have at least a simplistic solution for outproxy selection before we add multiple outproxies to either the HTTP or CONNECT default proxy list. I don't think the current code, which selects an outproxy at random for each request, with no failure tracking, will provide a good user experience. I know you've made some comments on the thread, but for others, see http://zzz.i2p/topics/770 for details.

Also, because of the potential for abuse, do we need some way to get to "know" the new outproxy operator, or have some minimum period of operation, with people testing it, before we add it? I have no idea what the criteria should be.

comment:11 Changed 9 years ago by zzz

Resolution: fixed
Status: acceptedclosed

Updated i2ptunnel.config and hosts.txt 0.8.3-13

Note: See TracTickets for help on using tickets.