leves at caesar.elte.hu
Sun Mar 26 16:08:25 UTC 2017
Unless localhost is mapped to anything other than 127.0.0.1, that should
work without allowing remote connetions.
I always use 127.0.0.1 instead of localhost, because the image will always
On Sun, 26 Mar 2017, David T. Lewis wrote:
> On Sun, Mar 26, 2017 at 02:09:45PM +0200, Levente Uzonyi wrote:
>> Hi Dave,
>> it should work without enabling remote connections if you create an
>> ssh tunnel to dan instead of ian.
> I think that is what I am doing. Just to be clear, I do this:
> lewis at lewis-Gazelle-Pro:~$ ssh -L5901:localhost:5901 dan.box.squeak.org
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in the
> individual files in /usr/share/doc/*/copyright.
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> Last login: Sun Mar 26 14:19:37 2017 from 10.208.225.29
> davidlewis at dan:~$ sudo su - squeaksourcecom
> [sudo] password for davidlewis:
> squeaksourcecom at dan:~$ pgrep -l squeakvm
> 9388 squeakvm
> squeaksourcecom at dan:~$ kill -SIGUSR2 9388
> squeaksourcecom at dan:~$ # keep this connection open until the VMC connection is made
> squeaksourcecom at dan:~$ exit
> While the ssh connection is active, I use a VNC client to connect to
> localhost:1 which is port 5901 forwarded to dan.box.squeak.org, and
> then I enter the password for the VNC connection.
>> 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"
>>> by clicking the "enable remote connections" checkbox in the RFBServer.
>>> 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