A friend has connected successfully (shared desktop) from the U.S to here in Thailand to help me out with a few things. I know it works, so it's set up, but it won't let me on when it runs headless. Are you sure there isn't some sort of setting I have to change so it can run headless?
Maybe you could get your friend in the US to confirm that they can still use Screen Sharing when you are running the RasPiOS system 'headless.'?
If they can, there seems to be no reason why you should not be able to.
The official Raspberry Pi documentation looks very thorough and accurate, and includes suggestions for troubleshooting.
Ref: Raspberry Pi Connect (Beta) - https://www.raspberrypi.com/documentati ... nnect.html
I have posted previously -
I have 2 RPi[5] boards, both running 64-bit RasPiOS Bookworm, both available via Raspberry Pi Connect. Neither has ever had a screen/keyboard directly connected to them.
I don't recall needing to employ any unsupported or undocumented quirks or tricks to set up those systems for Screen Sharing access via RPi Connect, even though they have always been run 'headless.'
Although your aim is to use Screen Sharing, have you confirmed that you can use RPi Connect in 'Remote Shell' mode to access your RPi from a shell (command line) environment? Do you see "(Screen sharing)" in a grey box, alongside the option for "( Remote shell"), under the name of your system on the connect.raspberrypi.com webpage?
Statistics: Posted by B.Goode — Sun Nov 17, 2024 9:54 am
