TOS 7.0.0517 Beta (X86) is Released for Update

[kai]

Is the new user part of the 'admin' group?

No. But I tried adding it there and nothing changed.

[Gremlin]

I created a user and found that they cannot access functions for mounting a remote folder. {This seems logical to a certain extent for security, but that is debatable I suppose.}
Added this user to 'admin' group and they could access the functions. This user was then able to mount a remote folder (presuming access to required file service} using smb protocol.
A non-admin user could not access the mounted folder until (at least) read permission was granted at the mount point.
Of course, to mount a remote folder the user executing the mount would need to know the credentials for the source share.

[EriChan]

On the underlying layer of the Linux operating system, the mount operation usually requires root privileges. In the TOS system, for security considerations, non-administrator users (non-superusers) are typically restricted from performing the operation of mounting remote file systems.

Recommended solutions:

• Setup by administrator: It is recommended that the administrator (superuser) complete the mounting operation uniformly in **Control Panel > Remote Folders**, and set its mount point as a public folder.

• Permission allocation: After the mounting is successful, the administrator can assign read and write permissions of this mount point folder to regular users via **Control Panel > Shared Folders > Edit Permissions**.

[kai]

I created a user and found that they cannot access functions for mounting a remote folder. {This seems logical to a certain extent for security, but that is debatable I suppose.}
Added this user to 'admin' group and they could access the functions. This user was then able to mount a remote folder (presuming access to required file service} using smb protocol.
A non-admin user could not access the mounted folder until (at least) read permission was granted at the mount point.
Of course, to mount a remote folder the user executing the mount would need to know the credentials for the source share.

The problem is that the newly created user can't map the shared folder as a remote network drive from Windows. They are denied access, even though all possible rights are granted.
Moreover, if you deny the new user access to WebUI TOS in the application settings, they can still access it!!

NAS F2-223
TOS 7.0.0517

[Felix]

We were unable to reproduce the local drive mapping issue during our tests. Please verify if you are currently using a computer where an administrator has already mapped and accessed the drive. If so, we recommend trying a different computer. Alternatively, please unmount the device for the administrator user, restart both the NAS and the computer, and then attempt verification again.

Regarding the issue preventing users from accessing the TOS desktop, we have successfully reproduced it and a fix is scheduled for a future TOS7 update. As this will take some time to implement, we appreciate your patience. Thank you for your understanding and continued support. Please keep an eye on our update announcements for further news.

[andreyzhukov]

Что делать с ошибкой при установке программы: Transmission4_okm TOS7_TOS6 4.1.1.1 x86_64.tpk
Истекло время ожидания запроса. Таймаут подключения к серверу, проверьте сеть и повторите попытку.

Одно и тоже при загрузке с компьютера файла и если он на самом NAS

[andreyzhukov]

Так же вылетает при попытке синхронизации фото Tnas Mobile Beta на iOS. Условно 5000 изи 35000 синхронизировало за ночь и начало теперь сразу почти вылетать. 1 минуту рабоатет и вылетает.

[Frynes]

Hello!

I've successfully upgraded my TNAS F4-425 from TOS 6 to 7 (of course going the long way, starting with 7.0.0299, then updating to this latest version 7.0.0517). Everything went smoothly at first.

About 15-20 minutes into 0517, the OS seems to have crashed. I had clicked to update docker and portainer (both were disabled), and left it alone for 5 minutes or so. When I came back to my computer, it said to click anywhere on the screen to log back into TOS (I guess my session timed out). When I clicked, it took me to a basic grey background login screen (with images missing). I entered my login, then pwd, and it would do nothing. I tried on another browser (private tab) and same thing was happening. I noticed there was no HDD activity on the NAS, so I rebooted about 10 minutes later, since nothing was responding. It's now restarted, and there is still no HDD activity, and now no web gui, TNAS does not appear on TNAS PC for Windows. The TNAS still responds to ping though, and it is indeed the correct IP. When trying to SSH, I'm asked my login, but as soon as I enter it, the TNAS closes the network connection.

EDIT: After a third reboot, things are back to normal again.

Has the TOS 7 been stable in your use since this time 2 weeks ago? I have had the same issue on TOS 5 and F4-212 NAS. This fixed would be an important mover for my move to TOS 7.

Regards,

[TMzethar]

Что делать с ошибкой при установке программы: Transmission4_okm TOS7_TOS6 4.1.1.1 x86_64.tpk
Истекло время ожидания запроса. Таймаут подключения к серверу, проверьте сеть и повторите попытку.
Одно и тоже при загрузке с компьютера файла и если он на самом NAS

It appears you are using an installation package from the app community. We recommend that you contact the developer who provided the installation package.
viewtopic.php?t=4506

[TMzethar]

Так же вылетает при попытке синхронизации фото Tnas Mobile Beta на iOS. Условно 5000 изи 35000 синхронизировало за ночь и начало теперь сразу почти вылетать. 1 минуту рабоатет и вылетает.

Please let us know the version of the TNAS mobile app.
Please collect a log file here and send it to us via the support email address for review.
My iPhone/TNAS mobile 3/Log