TOS 6.0.507 (X86) is Released for Update

[GevinKe]

I have an f2-421. Your company has been approved to participate in the beta program and is currently at tos 6.0.229.
The official version of tos 6.0.500 was released, so I tried upgrading my NAS, but it didn't work.

In tos 5.0, it was installed on all disks in the system and booted no matter which disk was inserted. However, in the beta 6.0 version, the system cannot be installed on another disk, so I am worried that I will not be able to use the NAS in case of disk failure.

So I tried initial installation on a blank disk, but the system installation failed because the partition was not recognized.
I tried for several days but it didn't work.

When will the official version of TOS 6.0 for f2-421 be released?

TOS 6.0.507 is currently our official version, and we are soon to release an update package for upgrading from TOS 6.0.229 to TOS 6.0.507. Please keep an eye on our announcements for timely updates.

Regarding the issue you mentioned about not being able to directly install the latest version, we take it seriously. To better assist you in resolving the problem, could you please provide a detailed description of the specific situation or error message you encountered? This will allow us to pinpoint the issue more accurately and provide you with a corresponding solution.

[Bartman]

No, I have a static IP and web address with all DNS records setup and working correctly. DNSSEC is setup and working. My son that lives so distance from me and my brother get the same errors for security, they both see Terra-master certs as unsecure, they are both with different ISP's.


Regards

[very3927]

The bios/initboot version of NAS is 5.12.

Plug the NAS's HDMI port into the monitor's HDMI and boot the NAS.

"error: no such partition
entering rescue mode...
grub rescue>"

The above message is displayed on the monitor and no further progress is made.

I tried formatting it with a new disk and deleting the partition without formatting it, but the symptoms are the same.

I turned it on, pressed del, went to the bios settings, tried various changes, and tried default settings, but it didn't work.

I tried using another blank hdd, but it didn't work.

However, if you install an existing HDD with 6.0.229 installed, it boots normally.

[koalakoala]

Thanks so much TMRyan.
Had a similar issue and the solution provided in this post (above) worked. Had to reinstall Plex.

[DCCentR]

Can I use this installation package for F4-424 Pro?
https://download3.terra-master.com/TOS% ... 290900.ins

[koalakoala]

Note. For some reason need to reinstall plex everytime the NAS is restarted.

[wemblykj]

I have imported my certs and setup TOS Certificate to use my .key and .pem in FTP, HTTPS, WebDAV and WebServer but the site still loads with unsecure server and still using TerraMaster cert/key/pem (which is invalid BTW).

So its not working.

Regards

Did this ever get resolved?

Cheers.

TL;DR

I have been using TOS 6.0.648 and I [still] have the same problem when assigning my personal CA certificate to the WebServer app.

The certificate upload and assignment appears to have worked and I can see from the TOS web-UI that the certificate is indeed properly assigned. However, when visiting my website I can see that the certificate served up is the default terra-master.com certificate, more specifically the one found at /etc/nginx/server.crt.

My CA certificate is valid [and trusted] as it works if I assign my CA certificate to 'HTTPS' (as used by TOS itself) and access TOS through my personal domain .
My CA certificate also works and is trusted in the WebServer app if I copy my certificate and key over the default key and certificate at /etc/nginx/server.*

I'm pretty capable in a Linux environment and have tried various hacks but from what I can tell this feature looks to be unworkable.

Some facts I have gleaned:

- WebServer/httpd/extra/httpd-vhosts.conf gets over written with the default terra-master certificate every time the web server restarts
- WebServer/config/WebServerDB when inspected with sqlite3 has no SSL configuration options and mirrors the options found in config/Settings.ini
- The default terra-master.com certificate reported by my browser has the fingerprint 5c5bf9a8c81def66dcd9eb9f80d1db12317c6448a13beed3d601e8b83f45c57d

[TMzethar]

Sorry you're experiencing an issue; we'll investigate it.
You can try setting your custom certificate for 'HTTPS' under Control Panel - Security - Certificates.

[Bartman]

I have imported my certs and setup TOS Certificate to use my .key and .pem in FTP, HTTPS, WebDAV and WebServer but the site still loads with unsecure server and still using TerraMaster cert/key/pem (which is invalid BTW).

So its not working.

Regards

Did this ever get resolved?

Cheers.

TL;DR

I have been using TOS 6.0.648 and I [still] have the same problem when assigning my personal CA certificate to the WebServer app.

The certificate upload and assignment appears to have worked and I can see from the TOS web-UI that the certificate is indeed properly assigned. However, when visiting my website I can see that the certificate served up is the default terra-master.com certificate, more specifically the one found at /etc/nginx/server.crt.

My CA certificate is valid [and trusted] as it works if I assign my CA certificate to 'HTTPS' (as used by TOS itself) and access TOS through my personal domain .
My CA certificate also works and is trusted in the WebServer app if I copy my certificate and key over the default key and certificate at /etc/nginx/server.*

I'm pretty capable in a Linux environment and have tried various hacks but from what I can tell this feature looks to be unworkable.

Some facts I have gleaned:

- WebServer/httpd/extra/httpd-vhosts.conf gets over written with the default terra-master certificate every time the web server restarts
- WebServer/config/WebServerDB when inspected with sqlite3 has no SSL configuration options and mirrors the options found in config/Settings.ini
- The default terra-master.com certificate reported by my browser has the fingerprint 5c5bf9a8c81def66dcd9eb9f80d1db12317c6448a13beed3d601e8b83f45c57d

,
Nope, even Terramasters ssl cert comes up not secure, I have given up totally with them tbh, even Taxy doesn't help solve the problem as that does not work, the TNAS system is that tight and restricted its is rendered usless to us simple people, there are no clear instruction from TM in most of their addons, and you will always get "we will look into it" from their suport guys, no custom ssl cert work no mater what they say.


Good luck

[wemblykj]

That would be great if the problem could be looked at.

I can confirm that I have no issue when using my CA certificate for HTTPS. I can see that my certificate is served up when I access my TNAS admin and that it is suitable trusted if I redirect myself to the TNAS admin through my domain.

I can also confirm that with my CA certificate assigned to HTTPS, the TNAS web server problem is still the same, with the default terra-master self-signed cert served up.

Whilst I could install an Apache Docker container, it would be nice if the WebServer App worked as i would have expected it to

As a work around I can confirm that copying my uploaded certificate files into /etc/nginx solves the problem in the mean time (I do not bear any responsibility for any side-affects due to this approach!)

Code: Select all

cp /etc/certificate/_archive/<your uploaded cert name>/server.* /etc/nginx