TOS 7.0.0485 Beta (X86) is Released for Update

[TMroy]

After upgrading from version 7.0.0465, there is no access to network storage via the browser. Error: ERR_CONNECTION_REFUSED
The model is F2-425.
What to do?

The system started after the following:
1. Turned off the NAS
2. I took out all the disks except the system one.
3. Launched the NAS. Logged in via the web.
4. Disabled the NAS.
5. Put the discs back in place.
6. Turned it on.

I checked, everything is working.

It seems like the first boot after your system update was either unsuccessful or not fully prepared. Theoretically, this has nothing to do with your data drive, so I believe whether you unplug the data drive or not won't affect the system drive.

[Gravitator]

After upgrading from version 7.0.0465, there is no access to network storage via the browser. Error: ERR_CONNECTION_REFUSED
The model is F2-425.
What to do?

The system started after the following:
1. Turned off the NAS
2. I took out all the disks except the system one.
3. Launched the NAS. Logged in via the web.
4. Disabled the NAS.
5. Put the discs back in place.
6. Turned it on.

I checked, everything is working.

It seems like the first boot after your system update was either unsuccessful or not fully prepared. Theoretically, this has nothing to do with your data drive, so I believe whether you unplug the data drive or not won't affect the system drive.

Everything is possible. I don't know enough about TOS to draw any conclusions. I just described the procedure that helped me.

[DCCentR]

Hi DCCentR. The currently used Docker/Docker Compose versions are relatively new.
May I ask if you have encountered an issue that requires an even newer Docker/Docker Compose version to resolve?

Hi, all things considered, I don't really have a functional need for this update
But it's always good to have the latest version with the latest optimizations and security fixes.

[DCCentR]

Looks like a bug:

Clicking on “System log” (and clicking the "Refresh" button on that page) always triggers a pop-up error message that reads “Failed to retrieve data.”

[TMzethar]

Looks like a bug:
Clicking on “System log” (and clicking the "Refresh" button on that page) always triggers a pop-up error message that reads “Failed to retrieve data.”

Hi,
We have identified the issue you mentioned.
It has been added to our list of items to be fixed.
Please wait for a future update.

[TMzethar]

Looks like a bug:
Clicking on “System log” (and clicking the "Refresh" button on that page) always triggers a pop-up error message that reads “Failed to retrieve data.”

Hi,
This has been fixed in the newly released TOS 7 Beta.
viewtopic.php?t=9946

[usersky]

Guys where's the thread for the version 7.0.0517? I have it and don't understand what's with it. Even if that version was retired because some bad issues it should have the thread with relevant info. Don't know where else to post this.

[EgorA]

Guys where's the thread for the version 7.0.0517? I have it and don't understand what's with it. Even if that version was retired because some bad issues it should have the thread with relevant info. Don't know where else to post this.

viewtopic.php?t=9974 - here it is
I think that there is an error in this forum engine - I cant see this topic also

[usersky]

Guys where's the thread for the version 7.0.0517? I have it and don't understand what's with it. Even if that version was retired because some bad issues it should have the thread with relevant info. Don't know where else to post this.

viewtopic.php?t=9974 - here it is
I think that there is an error in this forum engine - I cant see this topic also

The release notes also wanished.

[CursaYang]

We've included the update notes for 7.0.0517 in the latest news, which you can find on the homepage.

This may have caused some misunderstanding, and we are discussing to retain the original post.