Jump to content

Bug after update to 4.3.0.26


Go to solution Solved by jasonborn,

Recommended Posts

Posted
Hello,

 

I just installed the 4.3.0.26 version of emby and since then I can't find my media.

 

I tried to return to the previous version no change....

 

I scan my media on a second network server via samba and I have not had any problems so far at this level.

 

Anyone have any ideas?

 

Sincerely.

  • Like 1
Posted

What previous version were you running?

From this server, can you view your media via it's mount point?  e.g. cd /mnt/MyMedia

Posted

Exactly the same issue, installed on a rpi4 with raspbian, working well with the previous version of emby

 

since the update to emby-server-deb_4.3.0.26_armhf.deb, i cant find my media through emby

 

ive checked if they disappear from my nas but medias are still there

 

Whats happened ?

Posted
I finally deleted completely emby because even after installing the latest version, it was impossible to find my files on the network.

 

In such cases, do you know how to save users and media playback status?

 

Sincerely.

Posted

We have to wait for a fix I think. For now my libraries are 'empty'.

Posted

We have to wait for a fix I think. For now my libraries are 'empty'.

Happy2Play
Posted

Do your library folders have a trailing slash when you added them?

 

But follow the linked topic in post 4.

Posted

Hi happy,

 

\\ip/folder/folder

 

Ik use a synology NAS.

 

Kind regards

Posted

Just 'downgraded' to 24b. Libraries are still 'empty'.

Posted

Did a clean install of the .26 version on DietPI and the libraries are still showing empty.

Posted

Hmmm, adding a library with format \\ip\folder\subfolder results in my situation in an empty librarie. I just added a library with format smb://IP/folder/subfolder and now the library get's filled with movies.  :o

Posted

Yes I noticed this detail while in the concrete it doesn't change much it's weird, in any case I'll wait for a more stable update at this level.

Posted

You're right TECH3, in the concrete it doesn't change much. I to will wait for a more stable release.

Posted

I just saw that this problem has been fixed in version 4.0.30 I'm testing this tonight once my backup is done, you can never be too careful ^^

Posted

Aha, a new version is available. I will give it a try tonight !

  • Solution
Posted

Upgrade to .30 went succesfull ! Thanks foks for the hard work !!

  • Like 1
Posted

Thanks for the feedback !

  • Like 1

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
×
×
  • Create New...