Opened 18 months ago
Closed 18 months ago
#2621 closed defect (fixed)
Reseed from URL stops working when upgrading to 0.9.42
Reported by: | np-tokumei | Owned by: | backup |
---|---|---|---|
Priority: | minor | Milestone: | 0.9.43 |
Component: | www/reseed | Version: | 0.9.42 |
Keywords: | reseed URL | Cc: | zzz |
Parent Tickets: | Sensitive: | no |
Description
I was setting up a reseed server and testing it using the reseed tutorial here (https://geti2p.net/en/get-involved/guides/reseed). Everything was working fine with my previous I2P router console (v0.9.41), especially when I submit the URL in the form of https://<my_reseed_host_name.tld>:8443/i2pseeds.su3
to Reseed from URL
. However, after upgrading to 0.9.42, this testing function stop working, and in the log console, there was this error:
9/12/19 10:29:00 PM WARN [Reseed ] uter.networkdb.reseed.Reseeder: EepGet? failed on https://<my_reseed_host_name.tld>:8443/i2pseeds.su3i2pseeds.su3?netid=2 : java.lang.Exception: Attempt failed
At my reseed server side, I saw this log:
"GET /i2pseeds.su3i2pseeds.su3?netid=2 HTTP/1.1" 404 0 "" "Wget/1.11.4"
So, it looks like the URL of the reseed server was appended with i2pseeds.su3?netid=2
, which is not neccessary.
Subtickets
Change History (1)
comment:1 Changed 18 months ago by
Milestone: | undecided → 0.9.43 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
oops, yeah, I broke it. The netid param is for proposal 147. But for the single-reseed case, I added the filename too, which was a mistake, it was in there twice. Thanks.
In 2dd874ddfa63d3ee13a7faae8eece827d3a7bfd3 to be 0.9.42-8