Remote Access on or off!?

you might want to do the ‘clean bundles’ to and all that to recover what must be a significant amount of disk space.

@ChuckPA said:

@silver1973 said:
I am having the same issue…attaching screenshot and logs.

Thank you.

Would you mind repeating the process please? Please augment:

Here is screenshot and log after repeating. Thank you

Thank you.

To confirm, At this point, what happens if you roll back to a pre-1.3.x version of PMS?

@ChuckPA said:
Thank you.

To confirm, At this point, what happens if you roll back to a pre-1.3.x version of PMS?

No issues with downgrade to 1.2.7.2987. Everything works as intended.

@silver1973

Do you have existing log files in 1.2.7?? Post?

If not, if I may impose?

  1. Using the sequence I outlined above, first begin by deleting all the old log files with PMS stopped.
  2. Run the enable ./ disable / verbose / and all sequence in Verbose mode to capture it.
  3. Capture those log files
  4. Stop PMS
  5. Upgrade to 1.4.3 but do not start until after deleting the 1.2.7 log files
  6. Repeat the sequence again in 1.4.3
  7. Captures those log files.

Now, with two clearly distinct sets, prefix each with PMS_version_and the existing name. (e.g. PMS_1.3.4_PMS_Logs… zip)

Attach both sets together here please.

This is the smoking gun I seek and need… It will allow me to track back and look at source changes in both front and back end to find.

@ChuckPA said:
@silver1973

Attach both sets together here please.

Here you go. Hope this helps! Upon upgrade, remote access no longer works again.

EDIT: it’s now ten minutes later and suddenly, remote access is working

Those are, unfortunately, the sweetest words I’ve heard today! you truly have helped profoundly.

Now for me to start digging, line by line, to see what exactly changed.

@silver1973

What is your currently showing Remote Accessibility state? Yes? or no?

@ChuckPA said:
@silver1973

What is your currently showing Remote Accessibility state? Yes? or no?

right now i am fully accessible outside my network

just when I think i have it cornered…

it changes!

:tired_face:

I got it… :smiley: >:)

@silver1973 and anyone else reading.

In my testing, I discovered something that hints of a solution (temp bandaid for us and quick easy fix for the dev team).

(Linux and Mac only)

  1. Setup manual port mapping if you don’t already use it.
  2. After it fails to connect (you’ve enabled but without success)
  3. Try to set your manual port if you can… if not, no fear.
  4. Stop PMS
  5. Edit Preferences.xml
  6. Make sure it has these fields defined as I show below
  7. Start PMS
  8. Don’t change / touch Remote Access but you should find it comes up ‘green’ and remotely accessible.

The values to set are:

LastAutomaticMappedPort="0"
ManualPortMappingMode="1"
ManualPortMappingPort="32401" (put your manual port number here)

Let me know how your mileage varies.

@silver1973 @chuckpa Thanks guys for working on this, sorry to say after reporting the issue I got tied up with other peoples priorities.

@ChuckPA said:
@silver1973 and anyone else reading.

In my testing, I discovered something that hints of a solution (temp bandaid for us and quick easy fix for the dev team).

(Linux and Mac only)

  1. Setup manual port mapping if you don’t already use it.
  2. After it fails to connect (you’ve enabled but without success)
  3. Try to set your manual port if you can… if not, no fear.
  4. Stop PMS
  5. Edit Preferences.xml
  6. Make sure it has these fields defined as I show below
  7. Start PMS
  8. Don’t change / touch Remote Access but you should find it comes up ‘green’ and remotely accessible.

The values to set are:

LastAutomaticMappedPort="0"
ManualPortMappingMode="1"
ManualPortMappingPort="32401" (put your manual port number here)

Let me know how your mileage varies.

I can’t find preferences.xml - i found the .plist file in preferences folder, but i have no software that can edit it…is there anything i can do at this point short of just uninstalling everything and waiting for a fix?

FYI I completely uninstalled it, reinstalled 1.4.3, rescanned the whole library, and everything worked perfectly until the minute I linked PMS with Plex on my AppleTV…then immediately, the remote server went red. I don’t know if that helps any but I’ll wait for your response. Thanks much

That tells me a great deal unfortunately. The moment it got connected to the outside world, your world went sideways. :frowning:

They are working on it pretty feverishly to resolve. The moment I know more, I’ll be quite loud about it.

Thanks so much for all your help. Hope it can be resolved soon.

Wait, why is this marked as “answered?”

It has to be green marked as “correct” answered. This is only that someone answered to this question

update - flushed dns cache, deleted port forwarding rule, reapplied port forwarding rule, restarted router and…so far, so good? Version 1.4.3.3433

The ‘acid test’. Will it hold > 60 minutes? PMS does a connectivity test at least 1x per hour.