Another solution I've used in the past, but forgot, is simply to allow ssh access from the Internet. I say "simply" but I should warn you that it's easy to make this insecure, but with a few tweaks it's possible to reduce the risk of the wrong people getting in. The simplicity of ssh makes it a bit more complicated to use, but it's also more flexible - for example, you can setup a tunnel and use this to remotely access other devices in your home network.
When I was about to go travelling, I would setup port forwarding on my router, to map ssh traffic to my NAS. When on the road, I could access the NAS using an ssh/sftp client. My client of choice on Android is X-plore, and it can present my NAS files in a file explorer, alongside local files and folders on my phone. I can copy a file to my phone, edit it, and copy it back to the NAS. I only wanted to be able to view documents, not to edit them, so I didn't need complex synchronisation features.
Security is important. There are lots of people out there who are motivated to take control of devices on your home network, whether it's for running a proxy to cover their tracks when they download kiddie porn, or to run bitcoin mining software, or to find your NAS and encrypt all your documents for ransom. Attackers are scanning for ssh servers all the time and running brute-force password attacks on the root/admin accounts. A poorly configured NAS is an easy target.
The things I do to increase security are:
1) Use a non-standard port on your port-forwarding configuration, to reduce the likelihood of network scanners finding your ssh port. Some people use "port knockers" to increase security further still, but this makes it more complicated to use, and increases the chance that you can't access your own files when you need them, because the port knocker software is misbehaving.
2) Create yourself a non-root account, and configure OpenSSH to not permit logins for the root user, from outside your home network range.
3) Create a key pair for your non-root account, and configure OpenSSH to not permit password logins for
I actually run both Dropbear and OpenSSH (on different ports of course), so that I can configure one of these in a more restrictive way for remote access, without fear of accidentally blocking local access to my NAS. Also, when I'm not travelling, and don't need remote access, I shut down the extra server and/or disable the port forwarding rule, so that it can't be compromised.
Cheers
Jeremy