[freenet-support] Freenet 0.7 build 1022

> To make it clearer, a comment from jflesch: > > - Stop your node > - Edit freenet.ini (in your node directory) > - Set 'fproxy.allowedHostsFullAccess' to the same value as > 'fproxy.allowedHosts' > - Do the same for 'fcp.allowedHostsFullAccess' > - Restart your node Thanks for the info.

[freenet-support] Freenet 0.7 build 1022

Yes, I am accessing it remotely, and yes, it would have been helpful to have that listed in the build email! Thanks, MrFlibble > This means that you access your node remotely, now you have > to enable the total access if > you want to be able to do everything remotely, otherwise you > are

[freenet-support] Freenet 0.7 build 1022

To make it clearer, a comment from jflesch: - Stop your node - Edit freenet.ini (in your node directory) - Set 'fproxy.allowedHostsFullAccess' to the same value as 'fproxy.allowedHosts' - Do the same for 'fcp.allowedHostsFullAccess' - Restart your node On 3/31/07, Matthew Toseland wrote: >

[freenet-support] Freenet 0.7 build 1024

-- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/support/attachments/20070331/3bbf9732/attachment.pgp>

[freenet-support] Server downtime

... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/support/attachments/20070331/7ad7ee6a/attachment.pgp>

[freenet-support] Freenet 0.7 build 1022

t this > isn't showing up, so I've no idea what it is! > > Any ideas? > > MrFlibble -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freen

[freenet-support] Freenet 0.7 build 1022

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mr. Flibble wrote: > My node's been looking weird since this update: > > The menu on the main fproxy page just shows > > * Home > * Queue > > And nothing else. > Also, if I click on the Queue menu, I see that I have an outstanding alert: >

Re: [freenet-support] Freenet 0.7 build 1022

Are you accessing the node from a remote computer? In 1021/1022 we introduced some new security settings which you must override if you want to configure/administrate the node remotely. On Fri, Mar 30, 2007 at 10:56:13PM +0100, Mr. Flibble wrote: My node's been looking weird since this update:

Re: [freenet-support] Freenet 0.7 build 1022

To make it clearer, a comment from jflesch: - Stop your node - Edit freenet.ini (in your node directory) - Set 'fproxy.allowedHostsFullAccess' to the same value as 'fproxy.allowedHosts' - Do the same for 'fcp.allowedHostsFullAccess' - Restart your node On 3/31/07, Matthew Toseland [EMAIL

[freenet-support] Server downtime

Hi, As most of you have probably noticed, the server has suffered of downtimes recently ... It's a known issue: we have moved it physically to a new chassis because of hardware problems. I would have announced it if it was planned ^-^ Everything ought to

[freenet-support] Freenet 0.7 build 1024

Freenet 0.7 build 1024 is now available. This fixes various bugs in 1022 relating to direct disk access (especially in Frost), timeouts when starting up (fixed in 1023), etc. Please upgrade. Please tell me if the auto-update system doesn't work for you. signature.asc Description: Digital

Re: [freenet-support] Freenet 0.7 build 1022

Yes, I am accessing it remotely, and yes, it would have been helpful to have that listed in the build email! Thanks, MrFlibble This means that you access your node remotely, now you have to enable the total access if you want to be able to do everything remotely, otherwise you are

Re: [freenet-support] Freenet 0.7 build 1022

To make it clearer, a comment from jflesch: - Stop your node - Edit freenet.ini (in your node directory) - Set 'fproxy.allowedHostsFullAccess' to the same value as 'fproxy.allowedHosts' - Do the same for 'fcp.allowedHostsFullAccess' - Restart your node Thanks for the info. That new

[freenet-support] Error after attempting auto update to build 1024

After attempting to do an update, which seemed to take a very long time (about an hour, which is a lot longer than It's taken before), I've tried to stop my node (as I couldn't get to the web interface). I tried stopping the windows service (which normally takes a while), but the java

[freenet-support] FW: Error after attempting auto update to build 1024

Oops, just noticed it's running 1025: Initializing Node using freenet Build #1025 r12483M and freenet-ext Build #11 r12008 with Sun Microsystems Inc. JVM version 1.5.0_11-b03 running on x86 Windows 2000 5.0 After attempting to do an update, which seemed to take a very long time (about an

Re: [freenet-support] [freenet-dev] Freenet 0.7 build 1024

On Sat, Mar 31, 2007 at 06:03:52PM +0100, Matthew Toseland wrote: Freenet 0.7 build 1024 is now available. This fixes various bugs in 1022 relating to direct disk access (especially in Frost), timeouts when starting up (fixed in 1023), etc. Please upgrade. Please tell me if the auto-update