Syndie Archive set up?
Syndie Archive set up?
Hi i2p. I've recently discovered Syndie and I love it. GUI is user friendly and it all seems to be working great, no complaints here.
I love the decentralization bit, better that eepsites. I'd like to move my activity to Syndie exclusively.
So in return I'd like to set up an archive for anyone to connect with. How would I do that?
Another question: In the "syndicate" tab I see "configure http server". What is the purpose of that and what happens when people connect to it? I am still learning a lot so expect more questions lol.
Any help will be greatly appreciated.
I love the decentralization bit, better that eepsites. I'd like to move my activity to Syndie exclusively.
So in return I'd like to set up an archive for anyone to connect with. How would I do that?
Another question: In the "syndicate" tab I see "configure http server". What is the purpose of that and what happens when people connect to it? I am still learning a lot so expect more questions lol.
Any help will be greatly appreciated.
i2pBote: sxgroarUzprvVzqEFV7tjDrjTpgatXxTqFw9H2z-yPV6ejjHmKosjaTHWkVBR-H7HHhe-y5d5GR9fdtBAGWbCy
Re: Syndie Archive set up?
Hi!
In general terms: just setup the http server of syndie, and it acts as a server.
You need to setup a I2P hidden service to it, if you want I2P users access it via I2P, or just open that port in local firewall and other may reach it via clearnet.
The http server is the server instance sending out the messages of syndie. If other user connect to it, it is checked which messages are new for the user (timeframe and size limitable in config), and those messages are exchanged.
Syndie Docs on: https://syndie.de/
echelon
In general terms: just setup the http server of syndie, and it acts as a server.
You need to setup a I2P hidden service to it, if you want I2P users access it via I2P, or just open that port in local firewall and other may reach it via clearnet.
The http server is the server instance sending out the messages of syndie. If other user connect to it, it is checked which messages are new for the user (timeframe and size limitable in config), and those messages are exchanged.
Syndie Docs on: https://syndie.de/
echelon
Re: Syndie Archive set up?
Thanks echelon for your quick reply.
i2p exclusively, that's the plan
So 2 new questions lol. First do I need to set up a different service for that or can I use my existing site/service and after that is done do I need to configure a new archive using the "add archive" tab?
Going to check the docs now, thanks.
EDIT: Can't really find in the link you provided HOW to exactly set things up so any help???????? Server is now running with default port. So that's a start.
In general terms: just setup the http server of syndie, and it acts as a server.
You need to setup a I2P hidden service to it, if you want I2P users access it via I2P
i2p exclusively, that's the plan
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
Going to check the docs now, thanks.
EDIT: Can't really find in the link you provided HOW to exactly set things up so any help???????? Server is now running with default port. So that's a start.
i2pBote: sxgroarUzprvVzqEFV7tjDrjTpgatXxTqFw9H2z-yPV6ejjHmKosjaTHWkVBR-H7HHhe-y5d5GR9fdtBAGWbCy
Re: Syndie Archive set up?
Hi!
great. You can create a new hidden service, or use a existent one and change the port and destination IP as you like it.
If syndie server runs on default port, you can try access it with a browser on that IP:port. It should show some syndie stuff![Smile :-)](./images/smilies/icon_e_smile.gif)
Now open the I2P router console, go to /i2ptunnelmgr and create a new "http" hidden service (or edit a existent one).
Try to enter the name and at least the port (of the syndie server), you can also change the name of the keyfile.
If you feel like it, you can edit the limit values and other extended values, usually not needed for first start.
Create the tunnel with save and backup the keyfile. Without keyfile, the address is gone and you need to create a new name/address and tell others.
On /i2ptunnelmgr you should see the service listed now, as you named it. Under the preview button you can get the b32 address of this service. Which which other can reach your hidden service.
But test it first on your own system (aka enter the b32 into your browser and see if you get the same view as if you enter the IP:port of syndie )
echelon
great. You can create a new hidden service, or use a existent one and change the port and destination IP as you like it.
If syndie server runs on default port, you can try access it with a browser on that IP:port. It should show some syndie stuff
![Smile :-)](./images/smilies/icon_e_smile.gif)
Now open the I2P router console, go to /i2ptunnelmgr and create a new "http" hidden service (or edit a existent one).
Try to enter the name and at least the port (of the syndie server), you can also change the name of the keyfile.
If you feel like it, you can edit the limit values and other extended values, usually not needed for first start.
Create the tunnel with save and backup the keyfile. Without keyfile, the address is gone and you need to create a new name/address and tell others.
On /i2ptunnelmgr you should see the service listed now, as you named it. Under the preview button you can get the b32 address of this service. Which which other can reach your hidden service.
But test it first on your own system (aka enter the b32 into your browser and see if you get the same view as if you enter the IP:port of syndie )
echelon
Re: Syndie Archive set up?
Now that was crystal clear! Thanks.
So, everything works. Created a new service, is accessible through my browser, changed the port to 4444.......no problems there.
One last hitch. When I try to add the archive to Syndie and want to sync it I get: "Fetch error: Archive must be proxied." What to do about that?
Archive b32: http://nvolgdj333esokdlf6z4cdm4xegfrw6t ... a.b32.i2p/
EDIT: after removing from Syndie and add again i get: Fetch error: unable to fetch-bad URL.
Sorry for all the questions man but I really want this to work
Thanks for your patience and time, much appreciated.
So, everything works. Created a new service, is accessible through my browser, changed the port to 4444.......no problems there.
One last hitch. When I try to add the archive to Syndie and want to sync it I get: "Fetch error: Archive must be proxied." What to do about that?
Archive b32: http://nvolgdj333esokdlf6z4cdm4xegfrw6t ... a.b32.i2p/
EDIT: after removing from Syndie and add again i get: Fetch error: unable to fetch-bad URL.
Sorry for all the questions man but I really want this to work
![Smile :)](./images/smilies/icon_e_smile.gif)
i2pBote: sxgroarUzprvVzqEFV7tjDrjTpgatXxTqFw9H2z-yPV6ejjHmKosjaTHWkVBR-H7HHhe-y5d5GR9fdtBAGWbCy
Re: Syndie Archive set up?
Alright. I managed to get an archive up and it is syncing and fetching. Thing is it works on the default port 8080. worked right off the bat.
Yet, when I try to set up just for i2p following the exact examples of others I get all sorts of errors: Connection refused, bad URL, must be proxied and even a protocol error. I really really want one for i2p as well (learning AND helping the network especially Syndie).
I've been cracking my brain as to what I'm doing wrong but can't figure it out.........
Yet, when I try to set up just for i2p following the exact examples of others I get all sorts of errors: Connection refused, bad URL, must be proxied and even a protocol error. I really really want one for i2p as well (learning AND helping the network especially Syndie).
![Geek :geek:](./images/smilies/icon_e_geek.gif)
i2pBote: sxgroarUzprvVzqEFV7tjDrjTpgatXxTqFw9H2z-yPV6ejjHmKosjaTHWkVBR-H7HHhe-y5d5GR9fdtBAGWbCy
Re: Syndie Archive set up?
HI
Somehow you setup a wrong protocol.
Did you setup a http server typ hidden service?
And entered the correct IP:port of the syndie server?
echelon
Somehow you setup a wrong protocol.
Did you setup a http server typ hidden service?
And entered the correct IP:port of the syndie server?
echelon
Re: Syndie Archive set up?
Yes. Http as per your instuction.
Port the same as the server. Tried standard as well.
Doing another set up shortly.
EDIT: Nope, same errors.........default port works fine, 4444 gives me the errors.
EDIT2: Never mind got 2 up and running, was being stupid in the set up
All is working fine. How do I tell others about the archives?
![Smile :)](./images/smilies/icon_e_smile.gif)
![Smile :)](./images/smilies/icon_e_smile.gif)
EDIT: Nope, same errors.........default port works fine, 4444 gives me the errors.
EDIT2: Never mind got 2 up and running, was being stupid in the set up
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)
i2pBote: sxgroarUzprvVzqEFV7tjDrjTpgatXxTqFw9H2z-yPV6ejjHmKosjaTHWkVBR-H7HHhe-y5d5GR9fdtBAGWbCy
Re: Syndie Archive set up?
Hi!
Oh, ok, 4444 is the default http proxy port for the brwoser, only to be used in browser config. sorry, did missed that information.
You can handout the b32 address via syndie, email, forum, IRC.
also you can register a petname on stats.i2p with the b64 address (found in hidden service config) and hand out that petname.
echelon
Oh, ok, 4444 is the default http proxy port for the brwoser, only to be used in browser config. sorry, did missed that information.
You can handout the b32 address via syndie, email, forum, IRC.
also you can register a petname on stats.i2p with the b64 address (found in hidden service config) and hand out that petname.
echelon
Re: Syndie Archive set up?
Will do. Thanks for all your help
If I can ever return the favor, let me know.
![Smile :)](./images/smilies/icon_e_smile.gif)
i2pBote: sxgroarUzprvVzqEFV7tjDrjTpgatXxTqFw9H2z-yPV6ejjHmKosjaTHWkVBR-H7HHhe-y5d5GR9fdtBAGWbCy