TerraMaster Forum

Hi,

I am migrating from Synology to Terramaster and encountering an issue I did not have with Synology, hoping someone can shed some light.

I am running the F8 SSD plus with the latest TOS 6.x on my home network. TOS is accessible via local ip on port 8181.

I have a reverse proxy that redirects https://nas.mydonain.com to the local ip on port 8181. The reverse proxy sorts out ssl certificates etc...

When I go to https://nas.mydonain.com on my web browser, I can access TOS as expected and everything works.

When I try to use my TNAS Mobile on Android to access my NAS, i enter nas.mydomain.com into the address and it fails after a while with error: "please check that the address and port you entered are corrct".

I have tried:
- entering: nas.mydonain.com:443
- connecting different networks
- accessing with Chrome on my mobile works
- using the Apple version
- nothign appears in the HHTP system logs

emoll wrote: ↑15 Jan 2025, 20:28

The current version of TNAS Moblie does not support https reverse proxy address, please wait for the new version.

For that situation I use the terramaster ID to log in from outside my local network, it's the same, and you don't expose your TNAS URL on your own domain.

TMlinda wrote: ↑15 Jan 2025, 21:42

emoll wrote: ↑15 Jan 2025, 20:28

The current version of TNAS Moblie does not support https reverse proxy address,fall guys please wait for the new version.

When will the new version be released, do you know the specific time?

TomasCremin wrote: ↑01 Apr 2025, 16:59

Thank you for your attention. The login issue with the HTTPS reverse proxy address has been resolved. We recommend that you install the latest version (3.3.057 for Android, 3.3.061 for iOS) before attempting to log in using the HTTPS reverse proxy address. Feel free to contact us at any time for further consultation.

It sounds like you're dealing with an issue related to how your TNAS Mobile app is handling the reverse proxy setup. Since accessing the NAS via a web browser works fine, the problem might be specific to the app's configuration or compatibility with the reverse proxy.