Ah yes... Completely forgotten about that! ;-)
Thanks! :-)
Regards,
Evert
Volodya wrote:
> Volodya wrote:
>> Hi, Evert, look for the line in your freenet.ini/.conf like that
>>
>> mainport.port=
>>
>> That is the port number for the web interface, not clientPort,
>> which is for
Hello,
I recently installed Freenet Build 5106 on a Windows XP SP2 machine
via the freenet installer. After doing so, Freenet worked well with one
exception. It is a resource hog - both in terms of memory as well as
processor time. I found this puzzling as all other large Java
Hi all!
I don't get a web interface on http://[freenet-server]:8481/ ... I do
have the following in my config:
*
# The port to listen for local FCP (Freenet Client Protocol) connections on.
clientPort=8481
# A comma-separated list of hosts that may connect to the
Volodya wrote:
> Hi, Evert, look for the line in your freenet.ini/.conf like that
>
> mainport.port=
>
> That is the port number for the web interface, not clientPort,
> which is for use of applications using FCP.
>
> Hope this solves your problem.
>- Volodya
>
Hi, Evert, look for the line in your freenet.ini/.conf like that
mainport.port=
That is the port number for the web interface, not clientPort, which is
for use of
applications using FCP.
Hope this solves your problem.
- Volodya
Evert wrote:
> Hi all!
>
> I don't
Kurtis Stalnaker wrote:
"ok, at first I thought that I was just doing something stupid. Becuase when I
open up the gateway, I try clicking on the freesite links so I can figure out
what the heck this thing does, and I always get a page that says "
"Network error"
Freenet is a complex thing to
Hi all!
I don't get a web interface on http://[freenet-server]:8481/ ... I do
have the following in my config:
*
# The port to listen for local FCP (Freenet Client Protocol) connections on.
clientPort=8481
# A comma-separated list of hosts that may connect to the
Hi, Evert, look for the line in your freenet.ini/.conf like that
mainport.port=
That is the port number for the web interface, not clientPort, which is for use of
applications using FCP.
Hope this solves your problem.
- Volodya
Evert wrote:
Hi all!
I don't get
Volodya wrote:
Hi, Evert, look for the line in your freenet.ini/.conf like that
mainport.port=
That is the port number for the web interface, not clientPort,
which is for use of applications using FCP.
Hope this solves your problem.
- Volodya
Damn, forgotten
I don't know why Frost wouldn't work... you can still get to
http://127.0.0.1:/ in your web browser?
Give freenet a few hours to find its feet. Also check whether it has any
connections (advanced mode - open connections).
On Fri, Feb 03, 2006 at 07:23:29PM -0800, kurtis stalnaker wrote:
ok,
Ah yes... Completely forgotten about that! ;-)
Thanks! :-)
Regards,
Evert
Volodya wrote:
Volodya wrote:
Hi, Evert, look for the line in your freenet.ini/.conf like that
mainport.port=
That is the port number for the web interface, not clientPort,
which is for use of
Kurtis Stalnaker wrote:
ok, at first I thought that I was just doing something stupid. Becuase when I
open up the gateway, I try clicking on the freesite links so I can figure out
what the heck this thing does, and I always get a page that says
Network error
Freenet is a complex thing to get
Hello,
I recently installed Freenet Build 5106 on a Windows XP SP2 machine
via the freenet installer. After doing so, Freenet worked well with one
exception. It is a resource hog - both in terms of memory as well as
processor time. I found this puzzling as all other large Java
On 2/6/06, Ashton Vaz [EMAIL PROTECTED] wrote:
Hello,
I recently installed Freenet Build 5106 on a Windows XP SP2 machine
via the freenet installer. After doing so, Freenet worked well with one
exception. It is a resource hog - both in terms of memory as well as
processor time. I
14 matches
Mail list logo
