Safari will not allow login to QNAP NAS

I have migrated my account from a Late 2013 Mac Pro running the most up to date macOS Monterey to a Mac Mini Studio running up to date Sequoia.

My account on the mac pro can still log into my 2 QNAP NAS boxes using Safari. On my Mac Mini Studio Safari refuses to let me access the QNAP NASs

If I enter the IP address of the NAS as 192.168.1.130, I get a message "Safari can’t open the page “www.192.168.1.130” because the page’s address isn't invalid"

If I enter https://192.168.1.130/ I get the message “This Connection is Not Private"

Clicking on Show Details gives me

If I click on “view the certificate” it tells me that it is invalid - a known expected situation with QNAP NAS ( and possibly others?) as its a Self Certified Certificate.

Clicking on “visit this website”, gives me

But this is where it goers wrong. Clicking on “Visit Website”, instead of taking me to the NAS’s login page I again get

This sequence just cycles round again and again.


But if I use another account on the same Mac Mini Studio, then click on “Visit Website” it does take me to the NAS login page.


Using another browser, the DuckDuckGo browser, from my account works as well. Finder can view the folders inside the NAS. Time Machine is happily backing up.


So its something to do with my account and Safari.


I’ve spent an hour an a half on the phone to Apple Support, including getting transferred to a senior support agent. We checked everything visible in Safari and System Settings. We tried clearing caches, history and login in using a Private Window. We turned off anything that launched on login. We also checked several entries in both the System and User libraries; LaunchAgent, LaunchDaemons, Input Methods, Internet Plug-ins, Scripts. We tried booting in Safe Mode. There were many reboots. Nothing makes any difference.


Internet forum searches bring up a few people who have had similar problems login into local servers, but I haven’t found one that actually identified what was going on and providing a solution.


Apple support want me to check with QNAP to see if they are aware of anything. But I’m not convinced that QNAP can be causing a problem when other accounts, Finder and Time Machine are all happy. I suspect that if I connected a NAS from another supplier then that would also fail. If QNAP haven’t got anything then it's deleting accounts or possibly rebuilding the entire machine.


Unless some genius here can identify whats going on? I do hope so because rebuilding my account will be a complete nightmare!


Thanks.

Mac Studio, macOS 15.2

Posted on Jan 12, 2025 4:30 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 13, 2025 6:32 PM

I'm afraid the certificate is a complete red herring. I am accessing the server via a valid IP address. All other computers, accounts and browsers can access the server on my local network with exactly the same address HTTPS://192.168.1.130/. I am not trying to access the NAS over the Internet. Time Machine is successfully backing up to the NAS, Finder can see all the folders and file.

The only thing that cannot/will not access the NAS is Safari on my account on my Mac Mini Studio.


Apple Support failed to solve the problem after 1.5 hours on the telephone. They were muttering that I would have to delete my account or rebuild the whole machine. So far no-one on here has come up with a solution that addresses the problem.


So today I decided to bite the bullet, grasp the nettle, face the music etc, etc. I made sure I had everything backed up to local disks and iCloud and then completely deleted my account on the Mac Mini Studio. I created a new account with the same user name and re-imported everything.


Guess what? I can now use Safari to access the QNAP NAS. QNAP QFinder can also launch the NAS Home page. The "This Connection is not Private" loop round problem has completely gone away.


This proves that the root cause of the problem was something to do with Safari on my account on my Mac Mini Studio. It was nothing to do with certificates, firmware levels or the day of the week. Now I type https://192.168.1.130/ into Safari's search bar and it all works. Even typing the basic IP address of 192.168.130 works.

So the problem was just that Safari configuration or history was screwed up somehow.




Similar questions

10 replies
Question marked as Top-ranking reply

Jan 13, 2025 6:32 PM in response to MrHoffman

I'm afraid the certificate is a complete red herring. I am accessing the server via a valid IP address. All other computers, accounts and browsers can access the server on my local network with exactly the same address HTTPS://192.168.1.130/. I am not trying to access the NAS over the Internet. Time Machine is successfully backing up to the NAS, Finder can see all the folders and file.

The only thing that cannot/will not access the NAS is Safari on my account on my Mac Mini Studio.


Apple Support failed to solve the problem after 1.5 hours on the telephone. They were muttering that I would have to delete my account or rebuild the whole machine. So far no-one on here has come up with a solution that addresses the problem.


So today I decided to bite the bullet, grasp the nettle, face the music etc, etc. I made sure I had everything backed up to local disks and iCloud and then completely deleted my account on the Mac Mini Studio. I created a new account with the same user name and re-imported everything.


Guess what? I can now use Safari to access the QNAP NAS. QNAP QFinder can also launch the NAS Home page. The "This Connection is not Private" loop round problem has completely gone away.


This proves that the root cause of the problem was something to do with Safari on my account on my Mac Mini Studio. It was nothing to do with certificates, firmware levels or the day of the week. Now I type https://192.168.1.130/ into Safari's search bar and it all works. Even typing the basic IP address of 192.168.130 works.

So the problem was just that Safari configuration or history was screwed up somehow.




Jan 12, 2025 4:41 PM in response to RatleyRambler

QNAP is using http, or a mix of http and https, or has an invalid or expired or problematic certificate, and is getting caught by the connection security checks.


Check for firmware updates for whichever QNAP device is in use, as a starting point.


Viewing the certificate can potentially include some information about what is incorrect with it. Sometimes the certificate is malformed, sometimes it is expired, and sometimes the certificate lifetime is far too long.


Related reading:



Jan 12, 2025 5:58 PM in response to MrHoffman

My NAS is a QNAP TS-451D2 running QTS 5.2.2.2958. SWABNAS.myqnapcloud.com is the externally facing way to access the server from the internet. I’ve paid for a Certificate for that.


I can also successfully log in using Safari on my iPad.


I’ve just checked again and there is a new firmware just come out. So I’ll install that and try again. That will probably take quite some time to install so as its now 01:50 here, I will post results after getting some sleep!

Jan 12, 2025 5:06 PM in response to MrHoffman

Thanks for the response. We know that the QNAP Certificate presented by the NAS is Invalid . This situation has existed for several years now. There is an article on the QNAP site explaining it all, https://www.qnap.com/en/how-to/faq/article/why-does-my-nas-warn-me-that-my-connection-is-not-private.


But the invalid certificate does not explain why;

  • I can log in with Safari on another account on the same mac
  • I can log in with an alternate browser from my account


The problem is only occurring when I’m using Safari logged into my account on my Mac Mini Studio.


The certificate presented by the NAS looks like this


Jan 13, 2025 3:21 AM in response to MrHoffman

Ok, to clarify;

1) I am not adding www. to the IP address, Safari does that all by itself. I only included that to show I have tried all possible ways of entering the address.

2) The new NAS firmware has not changed the problem

3) The problem is Safari in my personal account on my Mac Mini Studio is behaving differently to;

  • Safari in a different account on the Mac Mini Studio
  • A different browser in the same account on the Mac Mini Studio
  • Safari in my account on several different machines


Whilst the Certificate issue is why all the browsers throw up a security concern, it is not why Safari on my account on the Mac Mini Studio is behaving differently to all other browsers and accounts. There is clearly something messed up with Safari on my Mac Mini Studio account. The question is, What?

Jan 16, 2025 6:23 AM in response to MrHoffman

"That cert is still invalid"


To be pedantic, it is perfectly valid for accessing the NAS over the Internet. And it works fine as I can access my photos from the pub.

It is only being flagged as "Invalid" when trying to access the NAS over a local network using the IP address of the NAS. This is expected behaviour and was not the reason I could not access my NAS over my local network. :-)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Safari will not allow login to QNAP NAS

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.