TerraMaster Forum

Since I got the F4-424 PRO, I can’t connect through Chrome. I have no issues when using Safari or Firefox, but with Chrome, it’s impossible.
I’ve already uninstalled and reinstalled it, but the same thing happens every time—it says the NAS address can’t be reached and shows the error "ERR_ADDRESS_UNREACHABLE."

As I mentioned, I can access the NAS with other browsers, so the problem isn’t with the NAS; it’s an issue with Chrome.

Has anyone else experienced this?

There’s a very simple solution, which is to stop using Chrome, and that might be the best option, but still, I’d like to fix it.

Perhaps you can try going to the network module of the control panel to change your HTTP port or HTTPS port, there are some ports that Google Chrome does not allow to use.

Chrome works fine in 'standard' form using TNAS default ports. You just have to persuade Chrome to allow 'http' rather than it's default 'https' that it tries to force.
(Shame @TM have not seen a way to accept https on local networks out of the box.)

Gremlin wrote: ↑18 Jan 2025, 22:24 (Shame @TM have not seen a way to accept https on local networks out of the box.)

what did you mean?

TMroy wrote: ↑23 Jan 2025, 14:45

Most browsers today expect to see https connection, but TNAS does not have the requisite 'local' certificate(s) and browsers 'fail' https. User then has to jump through (browser) hoops to confirm the connection is 'safe'. To experienced users not usually an issue, but to some (like my sister!) it's a nightmare

It is an insurmountable task for anyone to preconfigure certificates with local IP or URL addresses for hundreds of thousands of users; such a scenario currently presents an unsolvable predicament.

TMroy wrote: ↑26 Jan 2025, 18:33 It is an insurmountable task for anyone to preconfigure certificates with local IP or URL addresses for hundreds of thousands of users; such a scenario currently presents an unsolvable predicament.

Hello,
is it really necessary if there is a network path that TOS is offered by default?

I mean, could you issue a *.tnas.local certificate in addition to the existing *.tnas.online ?

Pulsar wrote: ↑18 Feb 2025, 15:07

I am sorry to inform you that your proposal is currently not feasible.

Yes, I’ve run into this with my F4-424 PRO too. Chrome just refuses to connect while other browsers work fine. Clearing the DNS cache and disabling page preloading fixed it for me; worth a try before giving up on Chrome.