Thanks for checking. When I go to my public IP:plex port, it shows that there is a cert there signed on 4th of Sept by LetsEncrypt that is ‘invalid’. I can show you the cert details if you need. I have made a few adjustments to my network settings but it should stay the same now. I can also access public IP:plex port remotely, just not securely. Any help or next steps would be greatly appreciated, thank you.
@BigWheel@ChuckPa after you reset my cert i built a new PC and decided to install my plex server on my new pc but now plex remote connections keep disconnecting in settings even though my port is open. this is fresh install of the plex server so this shouldnt be happening. i guess there is still a problem with your certfificate system.
can you please try resetting my cert one more time?
Edited:
nevermind, i switched the dns from cloudflare to google dns and now my p12 certificate gets created and remote connection is staying connected.
The main one giving me this issue is named “Alienware Server”. I’ve tried restarting, updating, uPNP as well as port forwarding. It was working just fine until I updated a couple of weeks ago. I’ve downloaded the logs. Which file should I be searching for the rate limit error?
Nothing in the logs about an api rate limit. I’m kind of at a loss here. It’s not a double NAT issue, a firewall issue or uPNP/port forwarding. It says "Fully accessible outside of your network, but all libraries still show unavailable.
@ben1703 i just reset it just for the sake of it. you should probably restart server. (or whole computer). Do you have any very aggressive anti virus or anything like that running? if you try http://ip:32400/web does it work?