Jump to content

Problème d'autorisation avec Emby Premiere


Pierregdrlt
 Share

Recommended Posts

Pierregdrlt

Bonjour à vous...

J'ai installé Emby server sur un Raspberry Pi (OS RaspBian).  Le serveur fonctionne tres bien. Cependant, lorsque je veux entrer ma clef Emby Premiere, j'ai comme message "Clé Emby Premiere introuvable ou incorrecte" .  Le support d'Emby me mentionne que le problème viendrais que mon Pi (le processus Emby) ne peut communiquer avec le serveur d'autorisation ("Connection to https://www.mb3admin.com/admin/service/EmbyPackages.json timed out").

Ma version de Raspbian est la version de base, aucun autre sécurité supplémentaire n'a été installé...      Comment faire pour trouver ce qui bloque la communication entre le Pi et le serveur mb3admin ??

 

Merci d'avance pour votre aide !!

 

Link to comment
Share on other sites

HI, it looks like something is blocking your Emby Server's outgoing connections.

2021-11-27 09 h09 h20.048 Error App: Error downloading news
	*** Error Report ***
	Version: 4.6.7.0
	Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffdetect /opt/emby-server/bin/ffdetect -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb
	Operating system: Linux version 5.10.63-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1459
	Framework: .NET Core 3.1.21
	OS/Process: arm/arm
	Runtime: opt/emby-server/system/System.Private.CoreLib.dll
	Processor count: 4
	Data path: /var/lib/emby
	Application path: /opt/emby-server/system
	MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://emby.media/community/index.php?/blog/rss/1-media-browser-developers-blog timed out

Can you please look into this? Typical causes are firewall, security software, or VPNs.

Link to comment
Share on other sites

Pierregdrlt

Bon....

Après des jours et des jours de recherche et d'essais, j'en viens à ls conclusion que Emby sur Raspberry Pi, ca ne fonctionne pas...

Je fais des requêtes https à partir du pi dans Chromiuim, ca fonctionne parfaitement;
Je fais un "curl https://www.mb3admin.com/admin/service/Embypackages.json", et je recois un paquet de données, instantanément;
Il m'est impossible de me connecter à Emby en utilisant  "https://localhost:8920"  (directement sur le PI);
Il m'est impossible de lier Emby à mon compte sur Emby.media;
Et bien sûr, la clef Emby Premiere est inutilisable....

Et personne pour aider ou au moins donner des pistes pour tenter de trouver une solution....

Je crois que je vais laisser Emby de côté, et tenter de trouver une autre alternative.......

 

😪

Link to comment
Share on other sites

Pierregdrlt

Pour le moment, non.

@cayars est en train de regarder celà. Je lui ai fourni une copie image de mon Pi.    Il semble que l'application Emby ne soit pas en mesure d'utiliser son propre certificat.   

J'attends impatiemment des nouvelles de Carlo !!!

Merci !!!

Link to comment
Share on other sites

Yes, I received the image. About 10 minutes ago I just got a delivery from Prime with a couple new SD cards.

I should now be able to extract your image and load it up on my Pi.  Hopefully I'll be able to track this down.

Link to comment
Share on other sites

@Pierregdrlt I got this working.  It seems the OS needed updating followed by Emby.

I SSH into the Pi4 and did these commands:
systemctl stop emby-server
sudo apt-get update
sudo apt-get upgrade
I then VLCed to the desktop and noticed top right there were updates to apply so I did that as well. Might have been redundant at this point but won't hurt. Then back to SSH
cd /home/pi
sudo apt-get remove emby-server-deb_4.6.7.0_armhf.deb
sudo dpkg -i emby-server-deb_4.6.7.0_armhf.deb
systemctl start emby-server

(you already had Emby Server 32bit version downloaded so I used that)

I then opened up a browser on my computer and entered brought up the Emby Dashboard http://ip:8096
If you don't know the IP while still in SSH type "ip -4 addr" which should only show 1 or 2 ips and it will be obvious

At this point I https seems to work fine.  I was able to view the plugin catalog as well as enter my Emby Premiere code.

So you can try that and let us know how you make out.  However since that's the 32 bit OS and it's a fresh install may I suggest installing the 64 bit version of the OS and 64 bit version of Emby?  It seems to run a bit faster.  You've got the image file for the 32 bit setup so if you don't like the 64 bit version for any reason you can easily revert back and apply the above.

Download the 64 version from here.  https://downloads.raspberrypi.org/raspios_arm64/images/raspios_arm64-2021-11-08/2021-10-30-raspios-bullseye-arm64.zip
Unzip the image and flash it to your SD card, put it in the Pi and boot up.
After it installs, SSH in and update the OS with:
sudo apt-get update
sudo apt-get upgrade

That will make sure everything is up to date for the OS. Then you can install 64 bit Emby
Download from here https://emby.media/linux-server.html the Debian Arm64 (aarch64) version
sudo dpkg -i emby-server-deb_4.6.7.0_arm64.deb

Let me know how you make out.

Link to comment
Share on other sites

Pierregdrlt

@cayars @Luke

J'ai suivi à la lettre ce que Carlo a demandé de faire sur la version que je lui ai envoyé, rien ne fonctionne...

J'ai gravé une autre carte SD avec l'OS 64 bits, et j'y ai installé Emby 64 bits,  ca ne fonctionne pas plus....

😭😭😭😭😭😭😭😭

Link to comment
Share on other sites

I've followed those directions three different times now for the 64bit build and they work every time.

Even with the 32 bit version it works but you must update the OS to pull down updated software and certs otherwise you likely get failure on some sites using https (which Emby uses).

You can put the image you sent me back on the SD card then after it boots do this:
I SSH into the Pi4 and did these commands:
systemctl stop emby-server
sudo apt-get update
sudo apt-get upgrade
I then VLCed to the desktop and noticed top right there were updates to apply so I did that as well. Might have been redundant at this point but won't hurt. Then back to SSH
cd /home/pi
sudo apt-get remove emby-server-deb_4.6.7.0_armhf.deb
sudo dpkg -i emby-server-deb_4.6.7.0_armhf.deb
systemctl start emby-server

That is all that was needed to get your previous image to work correctly.

With that said the 64bit version as a whole seems a little faster but I've not really spent a lot of time with it.

4 hours ago, Pierregdrlt said:

I burned another SD card with the 64-bit OS, and I installed 64-bit Emby on it, it doesn't work anymore ....

What exactly happens that doesn't work? For the 64bit version you started clean correct and didn't try to put this overtop the 32 bit with an in place upgrade correct? You did the steps as outlined above?

Link to comment
Share on other sites

One last comment.  There really is nothin special that needs to be done on a clean install.  You just burn the image to the SD card, put it in the Pi and startup.
Then go to terminal or SSH in and do the updates, upgrades and any package upgrades. Then reboot and check each again.

These are just standard things you would do in any Linux environment.
Since Emby is installed on the host itself and not in docker, jail or other container there is nothing tricky going on so it's all straight forward.

Link to comment
Share on other sites

Pierregdrlt

J'ai refait encore une troisième fois la procédure donnée par @cayars, et ca ne fonctionne pas...   impossible d'accéder au catalogue d'extension, et impossible de saisir ma clef Emby Premiere !!!

 

😭

Link to comment
Share on other sites

Later tonight I'll wipe my Pi and do a clean install of the OS followed by updates as well as install Emby.  I'll test it with my activation key like I did previously then remove it and check the catalog as well.

I'll you a generic username in Emby like Admin and a password I'll send you that you can login and use to create your account and any others before deleting it.

I'll then pull the SD card and make an image of it and send it to you.  If you burn that known good image and still have an issue it's going to be something unrelated to the image itself but something environmental but let's do this and get you an image.

I can create a 32 or 64bit build, so let me know which you prefer as it makes no difference to me.

Link to comment
Share on other sites

I see bullseye InRelease' changed its 'Suite' value from 'unstable' to 'stable' in the repository which will usually cause you to fail updating as you'll have to normally have to deal with old dependencies that need removing, cleaning and replacing before you can continue. You then go back and update/upgrade again and keep doing this until you have everything fixed.  Then you reboot and one more time go through the update/upgrade commands and if there is anything needing a fix or update you keep repeating that over and over until you have no old dependencies and a completely updated OS with no errors.

If you get stuck and have no clue what to do the easiest thing these days is to copy/paste errors you get into Google, do a search and find a solution.  Having tons of reference material and search engines to find answers in a couple minutes sure is better than piling through books looking for something or having to go to the library in hopes of an answer or calling other people for some help in the old days. :)

It's no big deal as it's just part of learning Linux or any Unix type OS.

I'm building the images for you to make this simpler.  But if you have the 32 bit version handy, what do you get if you run these two commands?

If you do a sudo apt-get update
followed by sudo apt-get upgrade

I don't know when they changed the status so I'm rather hoping you have some errors from those two commands which would likely be the cause of Emby not working correctly with secured sockets.

 

Link to comment
Share on other sites

Pierregdrlt

@cayars     Bonsoir....

Je préfère la version 32 bits pour le moment, vu que la version 64 bits n'est pas une version stable...

Voici ce que me retourne les deux commandes :

pi@RaspPi4B4:~ $ sudo apt-get update

Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Fetched 15.0 kB in 1s (11.9 kB/s)
Reading package lists... Done

pi@RaspPi4B4:~ $ sudo apt-get upgrade

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libfuse2
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Mais comme j'avais déjà fait les mises à jour, je peut le refaire avec la version que je t'ai envoyé....

😉

Link to comment
Share on other sites

That doesn't look bad. did you run the sudu apt autoremove as shown to remove libfuse2?
You want to get in the habit of doing that when the OS lets you know something isn't needed.

Link to comment
Share on other sites

OK I'm getting read to pull the card and make an image of it.
Doing a couple checks.
image.png.f52ce1a0f65887850eec4971a8111b39.png 

I tested using my Premiere key before removing it.

Here's a view from the the catelog:
image.thumb.png.62ee3fee275297d91b481256437a1440.png

The hardware Decoders & Encoders

image.png.2409abee388b4922cf81ff29cb964b97.png

So https is working fine for me.

Download it from here.

http://ayars.synology.me:5000/sharing/iaTnH5H8r
You will want to change passwords.
Pi/Raspberry for for the OS
Admin/password for Emby

I didn't set geo, time zones or video resolution so you will want to adjust settings to your liking.

 

 

image.png

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...