Another one here trying to connect VNC and totally lost. A few questions. Should the Organelle M be connected to my home wifi network or should my Mac be connected to the Organelle in Wifi?
I tried connecting using screen sharing with the IP of the Organelle as well as organellem:5901. It just never connects.
I upgraded to OS 4.0 with hopes that VNC would be easier. I still can’t connect.
I saw in the manual that Mac built in Screen Sharing is problematic. Is there a free app that is better?
As stated on post 2, I use realvnc for both organelle-1 and organelle-m, on macOS
I saw that and thought it was only a $40/year subscription. But then saw they have a free personal version. Thanks
1 Like
this worked perfectly!
i am using vnc viewer and have an organelle m; neither gave any issues.
thanks for putting in the time to make our lives easier. 
digging up an old thread here because it still came up on google when trying to start VNC on my Organelle 1. There’s an error, i thought you might like to update @thetechnobear:
For me “vnc://organelle:5901” did not work, but vnc://organelle.local:5901 did, as does simply organelle.local:5901.
That’s all,
Tom
It’s not really an error …. .local should be the default domain, so is ( usually) unnecessary…
but of course, versions of macOS and network settings can alter this.
( at the time I wrote this it was not needed , not tried recently, as I often just use the IP address 
)
Just tried this on an Organelle S2 and it seems to be missing vncserver (or maybe didn’t install correctly?) — in the web interface console, when I run “System > Extra > Start VNC” I get this output:
Menu Selection: 1:StartVNC
running shell :"/sdcard/System/StartVNC/run.sh" &
/sdcard/System/StartVNC/run.sh: line 29: vncserver: command not found
I’m also having no luck trying to SSH into the Organelle S2 so it’s hard to diagnose further 
To SSH, you need to enable it. We disabled it by default for security reasons. To enable it, you need to boot up with monitor and keyboard attached and run these commands:
sudo fw_dir/scripts/remount-rw.sh
sudo systemctl enable --now ssh.service
Now SSH will be available using the IP listed in the WiFi menu. User and PW are both ‘music’
I have VNC working on the S2, but haven’t made a proper installer. You can run these commands to do it manually:
sudo apt-get update
sudo apt-get install realvnc-vnc-server
Now the necessary vncserver-virtual command should be installed. Then you can use this system script to start it. (put the Start-VNC folder in /sdcard/System)
Start-VNC.zip (617 Bytes)
2 Likes
Awesome, thanks for the help! SSH is working for me, and VNC now works too connecting to port 1!
1 Like
I successfully enabled and used SSH and VNC and then added the tutorial patches folder to one of my patches folders and VNC mysteriously stopped working. I still see the files in bin/ and the Start VNC command is still in my Extras folder but it doesn’t actually start VNC. SSH still works currently. Is there any plan to add VNC functionality back into 4.4? Alternatively, is there an older firmware version that I could revert my unit to so I can easily use SSH and VNC instead of needing to troubleshoot them so much?
OS 4.4 is the only version available for the Organelle S2.
If you restart the Organelle, does it work again? or it just worked once and never again?
It worked once and hasn’t since. I fully reflashed the card last night and strictly followed the instructions above for installing VNC and using the script to start it but I’m only getting the “Starting VNC” message endlessly now without it actually starting the service.
Hey, just wanted to ping this thread again. Any plans to update VNC compatibility with 4.4?
We are working on some updates to the Organelle OS. It will include the VNC software installed, but I will just be installing using the steps I outlined above, so it would be good to know why It isn’t working for you. You could try running the command manually:
sudo mount -o remount,rw /
vncserver-virtual -geometry 1920x1080
This is all the Extra script is doing, but you might get some more info about what is going wrong.