leves at caesar.elte.hu
Sun Mar 26 12:09:45 UTC 2017
it should work without enabling remote connections if you create an
ssh tunnel to dan instead of ian.
On Sat, 25 Mar 2017, David T. Lewis wrote:
> On Fri, Mar 24, 2017 at 07:44:35PM -0400, David T. Lewis wrote:
>> VNC and mail from the squeaksource image do not work any more. The VNC used to
>> work on dan.box.squeak.org but not now, possibly something changed in network
>> configuration that the ancient image does not handle right. The stuck process
>> that caused the failure seems to fail on an error that tries to send mail to
>> inform someone of the problem, which fails because smtp does not work because
>> of network address resolution, which fails and throws an error that tries to
>> send more mail, etc.
> I am somewhat embarassed to admit that I just fixed the "broken VNC" problem
> by clicking the "enable remote connections" checkbox in the RFBServer. Apparently
> I accidentally left it disabled the last time I restarted the image.
> VNC access to the squeaksource.com image works again, as explained in
> dan.box.squeak.org:/srv/squeaksourcecom/README. Log in to dan.box.squeak.org,
> send SIGUSR2 to the VM process, then connect from your VNC localhost:1 connection
> within 60 seconds of the SIGUSR2 (after setting up the port forwarding to dan).
> Use the VNC password that is mentioned in the README.
> This is probably way too many layers of security now that we have the port
> forwarding set up on Rackspace, so maybe I should get rid of that requirement
> to send a SIGUSR2 to enable RFBServer. Leaving VNC running all the time would
> probably be fine. But maybe later, I will not change it now.
More information about the Box-Admins