Disable Cloud Access through User-Start file?

OK stupid question time. :laughing: Anyone use the user-start file to disable remote access/cloud access on a first gen v4.x single bay My Cloud? If so which services disable remote access/cloud access or which command from SSH will disable the Dashboard Cloud Access option?

For some stupid reason the My Cloud Dashboard Setting Cloud Access option gets turned back on (re-enabled) from time to time when I reboot or restart my first gen v4.x My Cloud. Very frustrating to have to constantly check the Dashboard to ensure remote access remains disabled.

Look at the file /usr/local/sbin/GetShareRemoteAccess.sh I think his file is called from the dashboard
to modifiy the remote access setting.

This has never happened on my Gen 1 device and I have had Cloud Access disabled forever. I only reboot maybe twice a month and for firmware updates.

I have very few services disabled upon startup. So its possible if one has certain services disabled or stopped it prevents Cloud Access from being re-enabled.

Don’t know why it happens on my end though. But its frustrating. I disable Cloud Access only to find it re-enabled a few days later when I happen to check again. I often shut down the My Cloud for long periods of time (like over night or while on vacation) since it fails to sleep for any length of time (another much discussed issue).

Will take a look at the /usr/local/sbin/GetShareRemoteAccess.sh file to see whats up with it. Wanted to keep the ability to enable remote access for those few rare times when I use it, but force it off otherwise.

The /usr/local/sbin/GetShareRemoteAccess.sh file should allow that. Just run the script to disable remote access. Use the dashboard to enable remote access when you want. You shluld also be able to see how to check if remote access is enabled with a script.

I maybe wrong. Not sure if this file is used to enable cloud access.

I think but I could be wrong that file just checks the remote access status and reports back. Its possible the remote_access.conf is where it’s set but that isn’t found where the share-param.conf file indicates its supposed to be on my system (etc/remote_access.conf).

IIRC, I’ve seen it happen on a firmware upgrade. I think I even posted about it being a stupid idea…

Me too. More than once after upgrading the firmware the Remote Access option was enabled when it was not enabled prior to upgrade. Stupid.