# Headless Plexamp using wrong url to connect to PMS **URL:** \ **Category:** Plex Labs\ **Tags:** plexamp\ **Created:** [May 15, 2023, 2:01pm UTC](https://forums.plex.tv/t/headless-plexamp-using-wrong-url-to-connect-to-pms/841199 "2023-05-15T14:01:23Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [May 15, 2023, 2:26pm UTC](https://forums.plex.tv/t/headless-plexamp-using-wrong-url-to-connect-to-pms/841199/2 "2023-05-15T14:26:56Z")
> [@jogolama](#): > > `WARNING - DEVICE: Server connection https://192-168-1-2.6b457c35a226490ead5df71e52754d01.plex.direct:32400 didn't work for plex: HTTP status -60` Do you have your own certificate involved? Error 60 implies MITM (names are complete mismatch) Your certificate log shows you got a new certificate yesterday followed by a new certificate today. Did you restart the apps today so they could get the new certificate ? Info: > [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/25): > > OpenSSL v3.0.0 and PMS. For those using their own domains and certificates with PMS , PMS 1.32.0.6865 and above updates OpenSSL from v1.1.1 to v3.0.0 . (changed the numbering scheme in the process) The consequence of this is OpenSSL v3 removed several “less secure” encryption methods. The impact on you, if you’re using an older distributions where openssl v3 is not the default, if not already doing so, you will need pay special attention to how your certificates are generated As example,… --- _[View the full topic](https://forums.plex.tv/t/headless-plexamp-using-wrong-url-to-connect-to-pms/841199)._