Only one open port?

Trying unsuccessfully to get Remote Access working again. Seeing that outside world can’t connect to my server, I’m looking into the causes of that situation. I’ve mapped 32400 to go to 32400 internally. I’ve run the canyouseeme app and yougetsignal. The latter scanned 20 common ports and determined that only Port 22 SSH was open. Windows Firewall, Norton Security turned off. My ISP is Xfinity.

Dunno where to go from here, can anyone help guide me?

I suppose 32400 is not a common port – hence I wouldn’t necessarily stop after checking those.

Have you checked if the port is available through http://canyouseeme.org (no need for an extra app)?

  • If it’s not, this implies the issue is either on your router or between router and internet (could be your ISP) – your next step should be to verify the router configuration for the port forward.
  • If it is working, this implies the issue is in/on the actual Plex Media Server and the router.

Personally I like the related support article on troubleshooting remote access which helped me in the past… it has some additional tips/checks in particular for scenario #2:
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/

Thanks for the reply. I did use canyouseeme - couldn’t see anything but port 22. Ran another port checker and got the following ports that didn’t work:

  • 21 FTP
  • 22 SSH … did work. Open!!!
  • 23 TELNET
  • 25 SMTP
  • 53 DNS
  • 80 HTTP
  • 110 POP3
  • 115 SFTP
  • 135 RPC
  • 139 NetBIOS
  • 143 IMAP
  • 194 IRC
  • 443 SSL
  • 445 SMB
  • 1433 MSSQL
  • 3306 MySQL
  • 3389 Remote Desktop
  • 5632 PCAnywhere
  • 5900 VNC
  • 6112 Warcraft III

Looking at your support article, I don’t know what you mean by scenario #2.

If canyouseeme.org cannot access the given port, the issue appears to be in your router configuration (let’s not dig into your ISP potentially blocking the port for you).

Can you elaborate how you have configured your router to establish the port forward?

PS: #2 referred to my 2nd bullet point -> the port is visible from the outside but users cannot access it (=issue in your home network or on the Plex Media Server).

Thanks again for the quick reply.

I have an Orbi router. Logged in to the router, went to ADVANCED > Advanced Setup > Port Forwarding/Port Triggering. Set External Port at 32400, Internal Port at 32400, Internal IP Address as 192.168.1.55 (static IP that I established).

The indication of non-communication in Plex goes from my computer IP (Public) to the 192… IP above.

I’ll look at the article.

Sometimes, the indicator within Plex (Settings > Remote Access) doesn’t get its status updates in time and might end up showing a false error.

Have you verified it’s not working from a device outside your home network? You could do this by accessing your server via https://app.plex.tv/desktop from your mobile while it’s not connected to your wireless home network.

Thanks one more time. Yes, I’ve turned off wi-fi on my cell, and get the “Houston, we have a problem…” screen.

hmm… in that case you might want to contact your ISP and ask them if they block certain ports.
As an alternative you could assign a different external port (e.g. tcp 8080) and link this to the internal port 32400. When doing this, don’t forget to change the configuration in Settings > Remote Access to match the public port you used in the port forwarding settings of your router (check Manually specify public port and enter e.g. 8080 as the “public” port).

Hi, a lot has happened since we last communicated - I’m confused about what’s going on with all the IPs. I went to my Orbi and changed the “Internet Setup”, putting in info on the 192.168.1.55 static IP that I set for my “Intel ® Ethernet Connection (2) I219-V”. Well, that crashed the network and I had to reboot the Orbi. When it was coming up, it said it was resetting the Orbi Router IP from 10.0.0.50 to 172.16.0.1. Fine, I said, not knowing the significance of that.

When I reran Plex and went to Remote Status, it showed the “Private” Address as 172.16.0.5:32400, close to what Orbi had said it set itself to, but not exactly the same. Still a red X at the right. Do I need to indicate anything about a static IP in the Orbi “Internet Setup”? (I used PortForward to specify a static IP for my Intel Ethernet Connection, to 192.168.1.55) Confused yet??

Now more crazy things. After rebooting Orbi, trying Remote Access a few times, I now get blanks in the Private and Public fields (with red Xs), but above, it says "Fully accessible outside … ", and I can access it from my cell.

That’s great, but I’d love to know what’s going on. I hope the success lasts.

It lasted for about half an hour. Now we’re back to the page showing Private and Public IPs, with X by Public IP, with no remote access.

Is this plugged into your own modem or a Comcast modem?

My Orbi is connected to an Xfinity XB6, set to Bridge Mode. Thanks for any help.

Login to your Orbi, if the WAN address starts with a 10.xxx.xxx.xxx, 172.16.xxx or 192.168.xxx.xxx then you are no longer in bridge mode.

Don’t I want to be in Bridge Mode, to ensure no double-NAT?

Yes, you want to be in bridge mode but it sounds like the Xfinity reverted to normal mode.

When I log in to my Xfinity router it still says I’m in Bridge Mode. Now Plex is saying it’s not available outside, but it also shows one person streaming, and it’s me on my wifi-less cell phone.

Is the wan / internet ip showing on the wan status page on the orbi router, the same as the ip that shows on canyouseeme.org ? If not then you have a double NAT

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.