Server Version#: 7.3.2-86009 update1
Player Version#: 1.43.0.10492
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
I just updated synology DSM to 7.3.2-86009 update 1 and now I have lost remote access. I have clicked disable and re-enable many times but all i get is “not available outside your network” Does anyone know what is going on? Was working fine before this update. Thanks
Try rebooting your modem/router and everything connected to it, including any wireless devices.
If that does not help, then please provide your server logs, thanks.
I’m having the same issue. Only mine started after the latest PLEX server update. I didn’t have an update for my router at all. I’ve rebooted the router, the modem, completely redid the port forwarding. Sometimes I will get the green “fully accessible” message for a few seconds. Sometimes for a minute or so. Then it reverts to not available. I can connect on the TVs (obviously–same network), I can also seem to connect on my phone, even if the wifi is off and I’m using the carrier. My friend cannot connect at her house though.
I’m having this exact issue. Restarted router, server, removed server and reconnected, nothing. Now it even hangs at 33% loading content on the tv connected.
Same story as @signup27 here. Version 1.43.0.10492
The „green remote access status switching back to red within seconds“ means nothing. That’s just Plex listing the status as „green“ while still testing the connection.
As for re-doing your port forwarding etc… have you verified your setup is visible/accessible from outside your home network (e.g. using a service like canyouseeme.org?
While doing that… does the public IP recognized by canyouseeme.org match that listed in the Plex Media Server‘s remote access settings and your routers WAN IP?
I can confirm.
Okay, here’s the update. No problems with port forwarding. IPs match. My friend IS able to watch SOME shows, but not all. (She’s not technically adept, so one or two didn’t work, so she stopped checking.) My thought is that something in the latest update broke the transcoding. I compared some of the files that did/didn’t work for her with Media Info, but didn’t see anything consistent. I did find out, though that the ones that play for her show up in my dashboard as DirectPlay across the board: video, audio, subs. Plus, she had watched the beginning of a show with no issues, then, after I updated the Plex server software, was not able to finish the rest of it, so the issue seems to have been triggered with the update. And so far, nothing she’s gotten to work seems to require transcoding. If it was a connection issue, I would think it would be an all or nothing thing: either she can watch everything or nothing. I also tried deleting the contents of the transcoding folder and let Plex rebuild it. No joy. Is there a way to roll back to a previous version and check if it works again?
Edit: Not sure if this is helpful, but watching the dashboard, I see nothing when she tries to connect (except, I think, a small jump in the remote bandwidth). On her end, all she gets is a buffering circle.
Then you’re issue doesn’t seem to be related to the remote access setup.
You could check your server logs for references to the transcoding decisions related to the problematic streams. I haven’t looked into those for some time… iirc, they used to have an [MDE] label (for „media decision engine“).
Make sure your logs are set to include debug logs (but not verbose!)
No, ended up not being that. Just a red herring. I suspected a double-NAT, so I had my provider put the modem in bridge mode, but that didn’t fix the issue. I didn’t mention it in the last post because I didn’t want to confuse things more. (I mean it DID fix the red message, but not the transcoding issue.)
Edit: I’ll check the logs as soon as I get a chance.
I forgot to ask again: do you know if there’s a way to roll back the software for the server? Everything worked fine before the update.
This is still a problem for me. Anyone have any info on if/when it’s going to be fixed?
To roll back Plex versions, first you need to uninstall Plex and then install Plex using an earlier package. Don’t go too far back, that can upset your database.
I doubt that will fix your issue, it is most likely network related.
Reboot your modem/router and everything connected to it, including any wireless devices. That should clear any DNS cache corruption that may be causing your issues.
No, it’s not network related. I’ve done all of the rebooing multiple times. I’ve fixed the CGNAT issue. I’ve made sure the ports are working properly. It’s still happening. It started with the update of the plex server. Since then, there’s been a transcoding issue. Like I said, if it was a connection issue, I would think no files would work. It’s the ones that require transcoding that don’t work. If I create optimized Plex versions of the files, it will work. But I don’t have the space for so many double files. My guess is that when they wrote the new update, whether accidentally or on purpose, they changed some of the transcoding. It looks as though there are other posts about this problem, too. I’m hoping that rolling back to the previous version will fix it. Thanks for the information about that.
Update on my end, this appears to be working now.
I was lazy about enabling debug logging. Yes, I know, crappy way to troubleshoot, but we’ve all done it before.
Here’s what I did.
So far, connections outside of my network have been solid.
