# "Not Secure" | https://url:34000" Question **URL:** \ **Category:** General Discussions\ **Created:** [October 7, 2017, 9:51pm UTC](https://forums.plex.tv/t/not-secure-https-url-34000-question/209290 "2017-10-07T21:51:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![sam.fleischer](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sam.fleischer/32/12484_2.png) [@sam.fleischer](https://forums.plex.tv/u/sam.fleischer)\ **Post date:** [October 7, 2017, 9:51pm UTC](https://forums.plex.tv/t/not-secure-https-url-34000-question/209290/1 "2017-10-07T21:51:00Z")
Hi everyone, This has been doing my head in for some time now. When I log into my NAS PMS, I use the shortcut “[https://192.168.0.200:3400](https://192.168.0.200:3400)” (which is the ip of my NAS) and I get a popup - ![](https://sea1.discourse-cdn.com/plex/uploads/default/original/3X/b/7/b74d86cd44a0cc92e3dc1fb45a02db89347c7a84.png) If I click on ‘Advanced’, I get - ![](https://sea1.discourse-cdn.com/plex/uploads/default/original/3X/5/7/5731d4eed6fc69991214fe162fa9dc83507363ac.png) And then click proceed to 192.168.0.200 (unsafe), I see my PMS screen, but at the top in the address bar, it shows me the [https://app.plex.tv](https://app.plex.tv) signin page, via email for me and then it shows me my PMS, but the address bar shows - ![](https://sea1.discourse-cdn.com/plex/uploads/default/original/3X/b/b/bb3ae33a25792c0860fc4a6063885e74a13bfb85.png) Is there a way to show it as Secure, so as to not go through the other nonsense? Thanks, Sam ---
**Author:** ![lazybones](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/lazybones/32/3815_2.png) [@lazybones](https://forums.plex.tv/u/lazybones)\ **Post date:** [October 7, 2017, 10:01pm UTC](https://forums.plex.tv/t/not-secure-https-url-34000-question/209290/2 "2017-10-07T22:01:40Z")
HTTPS requires the certificate to match the NAME of the service, you CAN’T get valid certificates for IP addresses. The connection is still encrypted but the browser is correctly warning you that the certificate does not match the host name in the browser. To Avoid this always connect via the [https://plex.tv](https://plex.tv) public interface. ---
**Author:** ![OttoKerner](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/ottokerner/32/10079_2.png) [@OttoKerner](https://forums.plex.tv/u/OttoKerner)\ **Post date:** [October 7, 2017, 10:04pm UTC](https://forums.plex.tv/t/not-secure-https-url-34000-question/209290/3 "2017-10-07T22:04:24Z")
You don’t have a cryptographic certificate which is valid for the “domain” 192.168.0.200 No valid certificate - no secure TLS connection, hence the warning from your web browser. Don’t use the http_s_ prefix. Or load the web app from [plex.tv](http://plex.tv) instead or disable Secure Connections in the server preferences or configure your router, if possible, and disable the DNS Rebinding protection for the domain plex.direct: > **[Why does my direct connection keep failing?](https://forums.plex.tv/discussion/comment/1448011/#Comment_1448011)** > > This may have to do with #a) unreliable domain name resolution. There are some ISPs, whose DNS servers are not reliable when it comes to resolve domain names on the .direct TLD. Plex assigns your server a unique subdomain on the \*.plex.direct... ---
**Author:** ![chapindad](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@chapindad](https://forums.plex.tv/u/chapindad)\ **Post date:** [October 8, 2017, 4:30am UTC](https://forums.plex.tv/t/not-secure-https-url-34000-question/209290/4 "2017-10-08T04:30:53Z")
It is secure. It is just warning you that it could be a man in the middle attack, so the browser is doing the right thing. I would not worry about it. ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [January 7, 2020, 11:57pm UTC](https://forums.plex.tv/t/not-secure-https-url-34000-question/209290/5 "2020-01-07T23:57:09Z")