@sa2000 said:
just so I understand … these codecs were in 1.9.x PMS version directory. Did the update to 1.11.1.4730 copy them across to this new directory or did you do that?
Upgrade copied them.
I just did as you instructed and stopped plex, deleted the directory completely. Upon restart, it made a new directory and did not put any codec’s in it.
correct - they will get downloaded as they are needed
if you had the proper codecs in the old version, then they would automatically reinstated and updated on the upgrade. Now we need to start from zero because of the unsupported action done back in August where you bypassed the system to get te codecs
If there was an issue, it should have been reported rather than find a zip from a colleague
@sa2000 said:
correct - they will get downloaded as they are needed
if you had the proper codecs in the old version, then they would automatically reinstated and updated on the upgrade. Now we need to start from zero because of the unsupported action done back in August where you bypassed the system to get te codecs
If there was an issue, it should have been reported rather than find a zip from a colleague
So I can appreciate that, however what I was saying is that I did a full reinstall in the wee hours of the morning and nothing was there.
However I can reproduce the error fairly quickly and send everything over. But I feel the root issue here is a corrupt codec or one that isn’t downloading (my guess here but obviously I’m shooting blind).
I do appreciate all of your help and am sorry for the headache this is causing both.
To be clear you are saying that if I attempt to watch a movie and it needs that codec, that Plex will on the fly go source that codec from your repository?
@sa2000 said:
correct - they will get downloaded as they are needed
if you had the proper codecs in the old version, then they would automatically reinstated and updated on the upgrade. Now we need to start from zero because of the unsupported action done back in August where you bypassed the system to get te codecs
If there was an issue, it should have been reported rather than find a zip from a colleague
So I can appreciate that, however what I was saying is that I did a full reinstall in the wee hours of the morning and nothing was there.
However I can reproduce the error fairly quickly and send everything over. But I feel the root issue here is a corrupt codec or one that isn’t downloading (my guess here but obviously I’m shooting blind).
I do appreciate all of your help and am sorry for the headache this is causing both.
To be clear you are saying that if I attempt to watch a movie and it needs that codec, that Plex will on the fly go source that codec from your repository?
Yes codecs are downloaded on demand - they stay there and get carried into the next version or updated
The bit I am not understanding now, is why they did not get updated,
@sa2000 said:
correct - they will get downloaded as they are needed
if you had the proper codecs in the old version, then they would automatically reinstated and updated on the upgrade. Now we need to start from zero because of the unsupported action done back in August where you bypassed the system to get te codecs
If there was an issue, it should have been reported rather than find a zip from a colleague
So I can appreciate that, however what I was saying is that I did a full reinstall in the wee hours of the morning and nothing was there.
However I can reproduce the error fairly quickly and send everything over. But I feel the root issue here is a corrupt codec or one that isn’t downloading (my guess here but obviously I’m shooting blind).
I do appreciate all of your help and am sorry for the headache this is causing both.
To be clear you are saying that if I attempt to watch a movie and it needs that codec, that Plex will on the fly go source that codec from your repository?
Yes codecs are downloaded on demand - they stay there and get carried into the next version or updated
The bit I am not understanding now, is why they did not get updated,
Wish I knew.
It’s sounding like a quick uninstall/reboot/re-install/reboot/test is in order.
I’m just puzzled because I’ve done that about 3x now. (Upgraded in place which doesn’t count), then did a full uninstall to revert to 1.10, that failed. Uninstall back to 1.11, no love. Uninstall back to 1.9, no love. Uninstall and back to 1.11 again.
So it’s still failing after the changes you requested so I’ll send over new logs. Just give me a quick moment. I’ve left the new library from the test up and in place
So it’s still failing after the changes you requested so I’ll send over new logs. Just give me a quick moment. I’ve left the new library from the test up and in place
At least we are using right files
and please a directory listing or zip of your codecs folder please - I want to compare the sha checksums
So it’s still failing after the changes you requested so I’ll send over new logs. Just give me a quick moment. I’ve left the new library from the test up and in place
At least we are using right files
and please a directory listing or zip of your codecs folder please - I want to compare the sha checksums
Updated Logs.
I killed the directory before, restarted the service, it re-created it - and then I attempted to play the TV Show I’ve been testing and tried to access it from my iphone.
The directory has no codecs in it, and nothing is there. The directory is here…
C:\Users\Administrator\AppData\Local\Plex Media Server\Codecs
Only items in place there are…
Folder named 6bd6751-1276-windows-i386
It is empty
and then a token file sits at the root of the Codecs directory as well.
.device-id
So it’s still failing after the changes you requested so I’ll send over new logs. Just give me a quick moment. I’ve left the new library from the test up and in place
At least we are using right files
and please a directory listing or zip of your codecs folder please - I want to compare the sha checksums
Updated Logs.
I killed the directory before, restarted the service, it re-created it - and then I attempted to play the TV Show I’ve been testing and tried to access it from my iphone.
The directory has no codecs in it, and nothing is there. The directory is here…
C:\Users\Administrator\AppData\Local\Plex Media Server\Codecs
Only items in place there are…
Folder named 6bd6751-1276-windows-i386
It is empty
and then a token file sits at the root of the Codecs directory as well.
.device-id
I am seeing this windows RSA issue
Jan 28, 2018 15:50:16.378 [0200] ERROR - Unexpected error configuring transcoder: boost::filesystem::unique_path: Key not valid for use in specified state
So it’s still failing after the changes you requested so I’ll send over new logs. Just give me a quick moment. I’ve left the new library from the test up and in place
At least we are using right files
and please a directory listing or zip of your codecs folder please - I want to compare the sha checksums
Updated Logs.
I killed the directory before, restarted the service, it re-created it - and then I attempted to play the TV Show I’ve been testing and tried to access it from my iphone.
The directory has no codecs in it, and nothing is there. The directory is here…
C:\Users\Administrator\AppData\Local\Plex Media Server\Codecs
Only items in place there are…
Folder named 6bd6751-1276-windows-i386
It is empty
and then a token file sits at the root of the Codecs directory as well.
.device-id
I am seeing this windows RSA issue
Jan 28, 2018 15:50:16.378 [0200] ERROR - Unexpected error configuring transcoder: boost::filesystem::unique_path: Key not valid for use in specified state
we have a risk of being rate limited if too many attempts to download the codec - once the rsa issue is addressed – but should be allowed an hour later
So I’ve done the requested items, and no bueno on my end.
C:\Users\USER\AppData\Roaming\Microsoft\Crypto\RSA
I went in this directory and re-named the files inside of it (just incase I didn’t want to delete them). I then rebooted, and started Plex.
Sounds like you are saying - we may be caught by a ‘to many requests so it blocks my IP for a bit’ issue?
Here are the new logs - Pretty much got an immediate error on the transcoding issue, which before it was stalling for a bit.
@sa2000 said:
we have a risk of being rate limited if too many attempts to download the codec - once the rsa issue is addressed – but should be allowed an hour later
So should I disable Plex and not stream anything for an hour? I don’t want someone to randomly connect and try to download a codec and reset my timer.
@sa2000 said:
we have a risk of being rate limited if too many attempts to download the codec - once the rsa issue is addressed – but should be allowed an hour later
So should I disable Plex and not stream anything for an hour? I don’t want someone to randomly connect and try to download a codec and reset my timer.
@“Jason.likens” said:
So I’ve done the requested items, and no bueno on my end.
C:\Users\USER\AppData\Roaming\Microsoft\Crypto\RSA
I went in this directory and re-named the files inside of it (just incase I didn’t want to delete them). I then rebooted, and started Plex.
Sounds like you are saying - we may be caught by a ‘to many requests so it blocks my IP for a bit’ issue?
Here are the new logs - Pretty much got an immediate error on the transcoding issue, which before it was stalling for a bit.
we are not rate limited yet
It is still the same error as before Key not valid for use in specified state
Jan 28, 2018 16:52:12.065 [4680] INFO - CodecManager: obtaining decoder 'h264'
Jan 28, 2018 16:52:12.696 [4680] ERROR - Unexpected error configuring transcoder: boost::filesystem::unique_path: Key not valid for use in specified state
Jan 28, 2018 16:52:40.922 [2316] INFO - CodecManager: obtaining decoder 'h264'
Jan 28, 2018 16:52:41.530 [2316] ERROR - Unexpected error configuring transcoder: boost::filesystem::unique_path: Key not valid for use in specified state
You could try again - without reboot
shutting down Plex Media Server
Renaming this time the parent directory %APPDATA%\Microsoft\Crypto\RSA
Restarting Plex Media Server
I do not know if it is ok to rename the parent directory (Crypto) - but I think a user did that before