TerraMaster Forum

ruzaj wrote: ↑16 Dec 2025, 15:38 Hi Terramaster,

f4-424 pro
tos6 6.0.794
bios MADN0101.V05

after successfully upgrade to 7.0 lots of applications dont work: plex, qbittorrent, komga, immich... so I rollback to tos6
will wait for stable version of tos7

After updating to TOS 7, if you selected the permission migration option, please wait for the process to complete and then update your applications. If you chose to configure permissions manually, you can edit the application user permissions for the shared folders required by Emby and Plex after updating the applications. Additionally, are Komga and Immich installed via Docker or as Community Applications?

RyanYang wrote: ↑16 Dec 2025, 20:05

ruzaj wrote: ↑16 Dec 2025, 15:38 Hi Terramaster,

f4-424 pro
tos6 6.0.794
bios MADN0101.V05

after successfully upgrade to 7.0 lots of applications dont work: plex, qbittorrent, komga, immich... so I rollback to tos6
will wait for stable version of tos7

After updating to TOS 7, if you selected the permission migration option, please wait for the process to complete and then update your applications. If you chose to configure permissions manually, you can edit the application user permissions for the shared folders required by Emby and Plex after updating the applications. Additionally, are Komga and Immich installed via Docker or as Community Applications?

Interesting did you have noticed my docker-disks rights post in this thread. There is no such docker application user available from the dropdown list. Can you advise?

I can't deploy nextcloud

I see we email [email protected] to report an issue or bug. Is there or will be a post listing the "confirmed" bugs, so if someone comes across an issue, they can check the list to see if it's on the list already?

DCCentR wrote: ↑16 Dec 2025, 17:48

storageninja wrote: ↑16 Dec 2025, 17:28

DCCentR wrote: ↑16 Dec 2025, 16:30 F4-424 Pro.
Can you, please, add the option to select the LAN port for which Open vSwitch should be enabled? Instead of enabling it for all ports.

I also can't get the internet to work for VMs. Has anyone figured it out?

Does the VM/client get an IP?

Looks like some problem with host and i can't select an interface:

Code: Select all

dccentr@TNAS:~# ovs-vsctl show
6feb0a03-1c4a-4fa1-93ad-9157583c26ab
    Bridge PN8ad9c6f
        Port PN8ad9c6f
            Interface PN8ad9c6f
                type: internal
    Bridge ovs_eth1
        Port eth1
            Interface eth1
        Port ovs_eth1
            Interface ovs_eth1
                type: internal
    Bridge ovs_eth0
        Port ovs_eth0
            Interface ovs_eth0
                type: internal
        Port eth0
            Interface eth0
    ovs_version: "2.17.9"

I too have a F4-424 Pro and was seeing the same behaviour after the TOS 7 update. I did a reset system configuration (Control Panel > System > Configuration > Reset System Configuration) on my unit last night and I was able to make some progress as the two network connections are now listed in the Network Setup in the VMs app and the host now shows normal, but ultimately I still can't connect to a VM that I spin up. I did notice it was using a port that I was already using in a docker container (8181), but even after stopping the docker container the webpage for the VNC doesn't connect/load.

Use network type external, not internal. Did you try that?

DCCentR wrote: ↑16 Dec 2025, 16:30 F4-424 Pro.
Can you, please, add the option to select the LAN port for which Open vSwitch should be enabled? Instead of enabling it for all ports.

I also can't get the internet to work for VMs. Has anyone figured it out?

Hello and thank you for your detailed feedback.

Regarding the request for port-specific selection in Open vSwitch: We have received your suggestion and have submitted it to the product team for evaluation. Thank you for helping us improve our product functionality.

Regarding the issue of VMs being unable to access the network: Based on the information you provided, we have confirmed that this is a known issue in the current version. We sincerely apologize for any inconvenience this may have caused.
Temporary solution: After enabling Open vSwitch, please try uninstalling and reinstalling the VMs. This should restore normal network connectivity for the host.
A fix for this issue will be provided in the next version. Please stay tuned for further updates.

Anyone else having port 8989 open, effectively blocking sonarr docker from running on its default ports?

from terminal I run:

ss -lntu | grep :8989

and get the following:

tcp LISTEN 0 4096 127.0.0.1:8989 0.0.0.0:*

Checking services file the port is not listed,as well as under control panel services and processes - ports

epicwomble wrote: ↑17 Dec 2025, 11:11 tcp LISTEN 0 4096 127.0.0.1:8989 0.0.0.0:*

Checking services file the port is not listed,as well as under control panel services and processes - ports

netstat -anp will show you the process/daemon names.

Many thanks.

tcp 0 0 127.0.0.1:8989 0.0.0.0:* LISTEN 1371/msgbus

what is msgbus? as before on TOS 6 this port was not in use and Sonarr worked fine on its default 8989