Re: Freenet node troubles

Pablo Arroyo schreef:
> Hello, I wish you could help me with some problems I am facing with my
> Freenet node. I have looked all over the FAQs and googling, but get no right
> answers. Please excuse me, I am not a native English speaker.
> 
> The main problem I am facing is that after accidentally uninstalling
> freenet, and then installing it again, Freenet fails to connect. If I try to
> start freenet, I will get "Firefox failed to connect to 127.0.0.1:8888. Then
> after 8-10 seconds, freenet stops running.
> I am guessing this is a problem caused by the port used by Freenet before
> and after installing it, but I could be wrong, since I am not an expert.
> Please, could you guide me in how to change the ports Freenet connects to,
> or guide me to a solution for my porblems?
> 
> I appreciate your time in reading this, I know you have other stuff to
> attend to. I really wish you could reply to my message, it would be very
> kind of you.
> 
> Thanks a lot, a former Freenet user wanting to use this amazing service
> again.
>

Plz note that 'Open Freenet' is not starting it, this command only sends 
the Fproxy address http://127.0.0.1:8888/ to your browser. It is a 
confusingly named item that would better read 'open the Freenet nodes 
homepage' or something.

Starting Freenet on windows is done by double clicking Freenet.exe or by 
using the start menu item 'start Freenet'. Third way is to use FNs 
system tray icon and pick 'start Freenet'.
You can check if FN is actually started by looking in winz' Task 
Manager, control-shift-escape.
You should see freenet.exe, freenetwrapper.exe and java.exe in the 
Processes tab.

The port numbers of your installation don't need to be changed. The ones 
your install uses can be found by looking at what's in the Freenet 
folder. Different file and folder names have two 5 digit numbers in 
them, for instance openpeers-12345. Those are the ports you can forward 
in your router and which must not be blocked by your software firewall. 
Keep those numbers to yourself, BTW.
There are www sites that allow you to check if a particular port is 
really opened. Somewhere in FNs documentation is such a site to be found 
and of course you can scroogle for one.
Freenet must be shut down before checking.
Some bad firewalls still block ports in spite of you telling it to open 
them, I had such a bad one. The same applies to hard-to-configure routers.
For most newer routers though, it is not necessary to do this by hand, 
uPnP does it for you.

_______________________________________________
Support mailing list
[email protected]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-request-RdDMkVZAZeuJnvDnx1genB2eb7JE58TQ@public.gmane.org?subject=unsubscribe