Connection problem to postman. Configuration issue?

[don_promillo]

Hi,

it seems, as if most trackers were down these days.

The postman tracker seems to be down most of the time. If I get a connection, the only thing I can see, is an untitled page without any content.

http://tracker2.postman.i2p/

The same is true for all the other links, that I found on this forum. What's going on?

Kind regards,

Andreas

[cumlord]

postman is up but i've had a lot more failed requests as well and they recently added a captcha to the upload process. Maybe they're under heavier load or something has happened where postman needed to decrease limits or something but it is not easy to use atm. could try reloading tunnels, using more, or switch between different routers if you have multiple. i'm finding my i2pd routers seem to be fairing better for this but maybe that's just me.

These ones are still working for me:
http://tracker2.postman.i2p:80
http://opentracker.skank.i2p:80
http://w7tpbzncbcocrqtwwm3nezhnnsw4ozad ... b32.i2p:80
http://opentracker.dg2.i2p:80


I haven't been able to connect to these ones for about a month:

http://lnq6yobtxququ8eq1flf395itiqf-hgjxuefvzetlfnocznjqvkdbtsb7ahhn853zjvxrjbgwlb9so57kakbdaj50luzgvphjli19tgj-cxyhhhscekx5jzurdew-ucdonmynr-b2zwhsx8vqcjwcekarvt21ykoyqdab9idv8atamp~pujqxrwceatmn96fcvenwdxqlee16fi8cvfov18jbjkrhtoypttczkv4l1wnybdwkgwpx5c0kcrrzfyw5~bjuako~gj5dr7bqsl7awboqus4k1lwoyrg1koibedd3xf8bwb6k3goooyjc1umykpur3g~fxbuqthasdrickebkuqj9mpyqltsujhnxiriw-olwmtvaycfci99ox8mvazps7~97x0gsm-onek1td9nbdmq30oqdxprtxbimbzklbr1ikobbg9hvrks3l-ksygwtumhg9rsqsozevfma-s0exo~o4g21q1oikmxpmhkevwq22vhb0-lzjfmlr4saaaa.i2p:80

http://ahsplxkbhemefwvvml7qovzl5a2b5xo5 ... b32.i2p:80

http://tu5skej67ftbxjghnx3r2txp6fqz6ulk ... b32.i2p:80

http://omitracker.i2p:80

[don_promillo]

Thanks for the quick answer. Well, I use i2pd as a router too, but haven't been able to access postman for quite a long time now.

I can reach http://opentracker.skank.i2p/ though I don't get the point of the trackers, which do not offer anything but a more or less blank page without the possibility to upload or download torrents. So what's the purpose of those kind of trackers?

[ghost92]

http://tracker2.postman.i2p [AH] [B32] is the only torrent INDEX site we have currently on I2P. This is like 1337x and ThePirateBay on the clearnet.

The "trackers" you find, like http://opentracker.r4sas.i2p, are "tracking" which torrents are being seeded/leeched by different users. "A BitTorrent tracker is a special type of server that assists in the communication between peers using the BitTorrent protocol." This helps you find peers to seed/leech to, without the need of DHT (Distributed Hash Table) or PEX (Peer Exchange).

You can find the stats of R4SAS's tracker at http://opentracker.r4sas.i2p/stats.

dr|z3d added an open list of the hashes his tracker is sharing at http://opentracker.skank.i2p/hashes

[lgillis]

Hi guys!

Well, I use i2pd as a router too, but haven't been able to access postman for quite a long time now.

If sites like postman's PaT with I2Pd are not accessible for a longer period of time, this is usually due to I2Pd. If this happens, I switch I2Pd off properly (stop), wait a few minutes and restart the daemon. After a few minutes of warming up, the connections are stable again. If this is different for you, let us know so that we can look for the error together.

Have a great Sunday

[cumlord]

np @don_promillo i was getting frustrated trying to upload something at that point in time and checked to see if anyone else was having similar issues, things seem to be a bit better now on my end anyway. Last thing i could think of on your end that hasn't been mentioned if you can't connect at all is maybe the router you're using isn't well integrated to the network... but usually if you've ran torrents through it already and it's been up for a while that shouldn't be an issue.

also didn't know about skank having a list of hashes on their tracker available, thanks for that!

[don_promillo]

Sorry, it's been a while since the last time i posted something in this thread. I apologize my absence, but it was a rather frustrating experience trying to connect to postman.

So now, after an update to the latest version I decided to try again. Unfortunately, the same symptoms occur: Trying to connect to tracker2.postman.i2p does not seem to work. I've stopped i2pd and waited a few minutes to start it again. As I can connect to this forum, the i2pd-router cannot be completely miconfigured. Should I post a portion of the i2pd logfile?

Kind regards.

[anikey]

It does not open in the browser either (you wrote about it at the top, but has anything changed)? Or just torrent client not contacting it?

Have you tried running i2pd with all default settings? (i.e. as a clean config to exclude configuration problems)

[don_promillo]

This is my i2p.conf file (without the port that should be kept secret):

Code: Select all

## Configuration file for a typical i2pd user
## See https://i2pd.readthedocs.io/en/latest/user-guide/configuration/
## for more options you can use in this file.

## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.

## Tunnels config file
## Default: ~/.i2pd/tunnels.conf or /var/lib/i2pd/tunnels.conf
# tunconf = /var/lib/i2pd/tunnels.conf

## Tunnels config files path
## Use that path to store separated tunnels in different config files.
## Default: ~/.i2pd/tunnels.d or /var/lib/i2pd/tunnels.d
# tunnelsdir = /var/lib/i2pd/tunnels.conf.d

## Where to write pidfile (don't write by default)
# pidfile = /var/run/i2pd.pid

## Logging configuration section
## By default logs go to stdout with level 'info' and higher
##
## Logs destination (valid values: stdout, file, syslog)
##  * stdout - print log entries to stdout
##  * file - log entries to a file
##  * syslog - use syslog, see man 3 syslog
# log = file
## Path to logfile (default - autodetect)
# logfile = /var/log/i2pd.log
## Log messages above this level (debug, *info, warn, error, none)
## If you set it to none, logging will be disabled
loglevel = info
## Write full CLF-formatted date and time to log (default: write only time)
# logclftime = true

## Daemon mode. Router will go to background after start
# daemon = true

## Specify a family, router belongs to (default - none)
# family =

## External IP address to listen for connections
## By default i2pd sets IP automatically
#host =

## Port to listen for connections
## By default i2pd picks random port. You MUST pick a random number too,
## don't just uncomment this
port = XXXX

## Enable communication through ipv4
ipv4 = true
## Enable communication through ipv6
ipv6 = false

## Network interface to bind to
# ifname =
## You can specify different interfaces for IPv4 and IPv6
# ifname4 =
# ifname6 =

## Enable NTCP transport (default = true)
# ntcp = true
## If you run i2pd behind a proxy server, you can only use NTCP transport with ntcpproxy option
## Should be http://address:port or socks://address:port
# ntcpproxy = http://127.0.0.1:8118
## Enable SSU transport (default = true)
# ssu = true

## Should we assume we are behind NAT? (false only in MeshNet)
# nat = true

## Bandwidth configuration
## L limit bandwidth to 32KBs/sec, O - to 256KBs/sec, P - to 2048KBs/sec,
## X - unlimited
## Default is X for floodfill, L for regular node
# bandwidth = L
## Max % of bandwidth limit for transit. 0-100. 100 by default
# share = 100

## Router will not accept transit tunnels, disabling transit traffic completely
## (default = false)
# notransit = true

## Router will be floodfill
# floodfill = true

[http]
## Web Console settings
## Uncomment and set to 'false' to disable Web Console
enabled = true
## Address and port service will listen on
address = 127.0.0.1
port = 7070
## Path to web console, default "/"
# webroot = /
## Uncomment following lines to enable Web Console authentication
# auth = true
# user = i2pd
# pass = changeme

[httpproxy]
## Uncomment and set to 'false' to disable HTTP Proxy
# enabled = true
## Address and port service will listen on
address = 127.0.0.1
port = 4444
## Optional keys file for proxy local destination
# keys = http-proxy-keys.dat
## Enable address helper for adding .i2p domains with "jump URLs" (default: true)
# addresshelper = true
## Address of a proxy server inside I2P, which is used to visit regular Internet
outproxy = http://false.i2p
## httpproxy section also accepts I2CP parameters, like "inbound.length" etc.

[socksproxy]
## Uncomment and set to 'false' to disable SOCKS Proxy
# enabled = true
## Address and port service will listen on
address = 0.0.0.0
port = 4447
## Optional keys file for proxy local destination
# keys = socks-proxy-keys.dat
## Socks outproxy. Example below is set to use Tor for all connections except i2p
## Uncomment and set to 'true' to enable using of SOCKS outproxy
# outproxy.enabled = false
## Address and port of outproxy
# outproxy = 127.0.0.1
# outproxyport = 9050
## socksproxy section also accepts I2CP parameters, like "inbound.length" etc.

[sam]
## Uncomment and set to 'true' to enable SAM Bridge
enabled = true
## Address and port service will listen on
# address = 127.0.0.1
# port = 7656

[bob]
## Uncomment and set to 'true' to enable BOB command channel
# enabled = false
## Address and port service will listen on
# address = 127.0.0.1
# port = 2827

[i2cp]
## Uncomment and set to 'true' to enable I2CP protocol
enabled = true
## Address and port service will listen on
# address = 127.0.0.1
# port = 7654

[i2pcontrol]
## Uncomment and set to 'true' to enable I2PControl protocol
# enabled = false
## Address and port service will listen on
# address = 127.0.0.1
# port = 7650
## Authentication password. "itoopie" by default
# password = itoopie

[precomputation]
## Enable or disable elgamal precomputation table
## By default, enabled on i386 hosts
# elgamal = true

[upnp]
## Enable or disable UPnP: automatic port forwarding (enabled by default in WINDOWS, ANDROID)
# enabled = false
## Name i2pd appears in UPnP forwardings list (default = I2Pd)
# name = I2Pd

[reseed]
## Options for bootstrapping into I2P network, aka reseeding
## Enable or disable reseed data verification.
verify = true
## URLs to request reseed data from, separated by comma
## Default: "mainline" I2P Network reseeds
# urls = https://reseed.i2p-projekt.de/,https://i2p.mooo.com/netDb/,https://netdb.i2p2.no/
## Path to local reseed data file (.su3) for manual reseeding
# file = /path/to/i2pseeds.su3
## or HTTPS URL to reseed from
# file = https://legit-website.com/i2pseeds.su3
## Path to local ZIP file or HTTPS URL to reseed from
# zipfile = /path/to/netDb.zip
## If you run i2pd behind a proxy server, set proxy server for reseeding here
## Should be http://address:port or socks://address:port
# proxy = http://127.0.0.1:8118
## Minimum number of known routers, below which i2pd triggers reseeding. 25 by default
# threshold = 25

[addressbook]
## AddressBook subscription URL for initial setup
## Default: inr.i2p at "mainline" I2P Network
# defaulturl = http://joajgazyztfssty4w2on5oaqksz6tqoxbduy553y34mf4byv6gpq.b32.i2p/export/alive-hosts.txt
## Optional subscriptions URLs, separated by comma
# subscriptions = http://inr.i2p/export/alive-hosts.txt,http://stats.i2p/cgi-bin/newhosts.txt,http://rus.i2p/hosts.txt

[limits]
## Maximum active transit sessions (default:2500)
# transittunnels = 2500
## Limit number of open file descriptors (0 - use system limit)
# openfiles = 0
## Maximum size of corefile in Kb (0 - use system limit)
# coresize = 0
## Threshold to start probabalistic backoff with ntcp sessions (0 - use system limit)
# ntcpsoft = 0
## Maximum number of ntcp sessions (0 - use system limit)
# ntcphard = 0

[trust]
## Enable explicit trust options. false by default
# enabled = true
## Make direct I2P connections only to routers in specified Family.
# family = MyFamily
## Make direct I2P connections only to routers specified here. Comma separated list of base64 identities.
# routers =
## Should we hide our router from other routers? false by default
# hidden = true

[exploratory]
## Exploratory tunnels settings with default values
# inbound.length = 2
# inbound.quantity = 3
# outbound.length = 2
# outbound.quantity = 3

[persist]
## Save peer profiles on disk (default: true)
# profiles = true

I found a clean i2pd.config and started i2pd with it. The result is the same. postman is down.

To be more precise: The i2psnark client sometimes reports that it can't connect to postman on specific torrents. Most of the time the status of my torrents is seeding.

I cannot connect to http://tracker2.postman.i2p/ with the help of my browser. The message always reads: "Can't create connection to requested host, it may be down. Please try again later."

[lgillis]

The configuration shown has been outdated since May at the latest and many things from the basic settings have been explicitly switched on or changed. This does not necessarily mean that the configuration does not work, but it does make comparison unnecessarily difficult. Which version are you running? The current version (github.com!) is 2.50.2. I would save the existing configuration and put it aside. Uninstall the program and install the new version without making any changes to the configuration. And then see if everything works.