Android "File Server" is Unusable / Fails with 502, Works on Desktop

I am trying to use the File Server feature to access files on my Android device. The tunnel connects successfully in the app (v9.1) and shows a status of "OK" with a live ping. However, any attempt to access the public URL (https://l1uwnvgbp.localto.net/ in my case) results in a 502 Bad Gateway error every time. The files are completely inaccessible.

Troubleshooting:

This is not a simple configuration issue. I have spent hours systematically testing and ruling out every possible cause of user error:

Network Issues: Ruled out. I used a VPN to bypass my local ISP's filter, proving the connection to your servers is clean.

File Path Issues: Ruled out. The 502 error persists even when using a simple, standard path like /storage/emulated/0/Download. The problem is not the folder path.

App Permissions: Ruled out. The LocaltoNet app was granted all available file and storage permissions.

Battery Optimization: Ruled out. The LocaltoNet app was explicitly set to "Unrestricted" to prevent the Android OS from putting it to sleep.

Proof of an App Failure:

To isolate the problem, I stopped the tunnel on my Android phone and started the exact same File Server tunnel from the command-line client on my Linux desktop.

The tunnel from my desktop worked instantly and perfectly.

Conclusion:

This proves that my account and the LocaltoNet service are working correctly. The bug is entirely within the Android client application. The "File Server" feature, as advertised for Android, is currently unstable and unusable. It should be investigated, as the public roadmap shows other users are also experiencing frequent disconnects and instability with the Android client.