Page 10 of 10
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 01 May 2026, 01:28
by apexwattson
Felix wrote: ↑30 Apr 2026, 17:36
apexwattson wrote: ↑30 Apr 2026, 03:12
TMzethar wrote: ↑30 Apr 2026, 02:55
Regarding your mention of 'unable to use Bitwarden auto fill username', may I ask which browser you are using?
We have noticed the issue you mentioned about ordinary users being unable to access Transmission and will conduct an investigation.
I am using Firefox. I have tried login in a private tab aswell but the issue persists.
We haven't made any changes to prevent autofill. You can check your browser's autofill exclusion list to see if the TOS Desktop URL is added and if the page's password is saved.
I have checked that setting but no luck. I have also been troubleshooting with Gemini AI which suggests some changes have been made but I am not sure if it's just guessing wildly with this answer:
"Updating to TOS 7.0.0517 introduces a redesigned login interface that handles form inputs differently than previous versions. This issue often stems from how the new WebUI interacts with browser password managers (like Chrome, Bitwarden, or 1Password), as the username field may no longer be identified as a standard "login" field by the browser's autofill engine."
However something I noticed right after updating to 7.0.0517 was that the username field was darker or more greyed out than before.

Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 04 May 2026, 21:56
by ctmutlow
Spotted my time machine backups had stopped working after the 7.0.0517 update on my F4 SSD; the update went smoothly although I didn’t check I could log in at the time.
I have now realised web interface won’t load after a successful login BUT can access via iOS app and so tried to update to next version. This failed with an out of space message despite there being 2Tb available in Volume 1, noticed cpu and memory usage were hitting maximum levels. Managed to enable ssh and dmesg shows tasks being off loaded and system out of memory! The nas rapidly becomes unreachable now as it hits memory issue.
Any suggestions about how to recover from this please ? Is there a usb update version of 7.0.0599 I could try and install?
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 04 May 2026, 22:13
by MikeZhang
When you enter OOM, it's recommended to expand RAM memory and wait it to kill processes and become accessible again
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 04 May 2026, 23:58
by ctmutlow
Thank you.
OOM out of memory? If I leave the web interface open after login in it requires login again then hangs!
So you are saying just leave it booted for a while and it will naturally come back! How long, please?
Tried after 15mins, web interface show background then multiple failed to retrieve data boxes
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 05 May 2026, 02:34
by ctmutlow
With a fresh restart after over an hour cpu. 100% and memory usage 93%, no access to system that allows access to fix.
Any suggestions please?
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 05 May 2026, 21:27
by MikeZhang
it's recommended to expand RAM memory and wait it to kill processes and become accessible again
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 05 May 2026, 21:35
by ctmutlow
Do you mean buy more physical RAM and add it to the NAS or wait until the existing RAM frees as tasks die?
Sorry I don’t understand?
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 06 May 2026, 15:14
by Felix
ctmutlow wrote: ↑05 May 2026, 21:35
Do you mean buy more physical RAM and add it to the NAS or wait until the existing RAM frees as tasks die?
Sorry I don’t understand?
We recommend that you purchase physical memory and install it into your NAS to accelerate task processing.
Re: TOS 7.0.0517 Beta (X86) is Released for Update
Posted: 07 May 2026, 02:00
by ctmutlow
Thank you both I am now up and running with 24Gb RAM.
It took several reboots to get the system up with a fully functional web interface after adding the RAM. not quite sure why?
I guess 7.0.0517 needed more memory than the previous version and broke things as everything worked fine until I did that update.
Now fully functional on TOS 7.0.0559 thank you.