A tool for tagging Emby content

[MBSki 1114]

13 minutes ago, VicMoore said:

This is the latest plugin - i changed the version number - let me know if it works

Emby.Bulky.dll 241 kB · 2 downloads

Multi-select for folders works now. Thanks @VicMoore!

[Cheesegeezer 3104]

16 minutes ago, VicMoore said:

shows I am teachable

 

I did try, but Rich is obviously better at it than me lol  

[Cheesegeezer 3104]

Vic gimme an hour and ill be back at the laptop if you need me for anything

[Junglejim 385]

Hi @VicMoore, got it installed and working but I don't seem to be getting any images. I wasn't sure if you wanted bug reports here or maybe create a new thread in the plugin section?

Other than that this look's great!

[Cheesegeezer 3104]

4 minutes ago, Junglejim said:

Hi @VicMoore, got it installed and working but I don't seem to be getting any images. I wasn't sure if you wanted bug reports here or maybe create a new thread in the plugin section?

Other than that this look's great!

Hey Jim, try refreshing/clearing your browser cache. That might work

[Junglejim 385]

17 minutes ago, Cheesegeezer said:

Hey Jim, try refreshing/clearing your browser cache. That might work

Yeah I tried that and it didn't make any difference, thanks for the suggestion though. I running Emby via a docker in OMV if that helps.

After I cleared the cache the images now have a broken icon in the top left, not sure whats going on there..

 

Edited March 29, 2023 by Junglejim

[Cheesegeezer 3104]

3 minutes ago, Junglejim said:

Yeah I tried that and it didn't make any difference, thanks for the suggestion though. I running Emby via a docker in OMV if that helps.

No probs, i can’t see why it wont work. On the page with no images, hit CTRL+SHIFT+I to open the the dev tools and then click on the console tab, see if there are any errors in the console and post those errors. You may be able to click on the link in the error and it will show the bit of code that is failing in the console.

[Cheesegeezer 3104]

12 minutes ago, Junglejim said:

After I cleared the cache the images now have a broken icon in the top left, not sure whats going on there..

 

Thats progress at least lol  

[Junglejim 385]

8 minutes ago, Cheesegeezer said:

No probs, i can’t see why it wont work. On the page with no images, hit CTRL+SHIFT+I to open the the dev tools and then click on the console tab, see if there are any errors in the console and post those errors. You may be able to click on the link in the error and it will show the bit of code that is failing in the console.

I think it maybe because my docker container is running in bridged mode??

Usually it shouldn't matter and the address is resolved to  192.168.20.100.. ?

Edited March 29, 2023 by Junglejim

[rbjtech 5284]

4 minutes ago, Junglejim said:

I think it maybe because my docker container is running in bridged mode??

Usually it shouldn't matter and the address is resolved to  192.168.20.100.. ?

Possibly related to CORS ? (Cross-origin resource sharing (CORS) is a browser mechanism which enables controlled access to resources located outside of a given domain.)

If you use the plugin within the container/vm itself (if possible) - do the images then show ?

[Cheesegeezer 3104]

6 minutes ago, Junglejim said:

I think it maybe because my docker container is running in bridged mode??

Usually it shouldn't matter and the address is resolved to  192.168.20.100.. ?

Ahhh i see, yeah it’s attempting to get address from 172.xxx etc. Hmmm, that looks like a bug and should use the manual address in the serverinfo shown in the console. As it then getsa new address. Is that your remote ip for the server? 

[Cheesegeezer 3104]

3 minutes ago, rbjtech said:

Possibly related to CORS ? (Cross-origin resource sharing (CORS) is a browser mechanism which enables controlled access to resources located outside of a given domain.)

If you use the plugin within the container/vm itself (if possible) - do the images then show ?

Nope no big bright yellow text in the console lol  

Edited March 29, 2023 by Cheesegeezer

[Junglejim 385]

2 minutes ago, rbjtech said:

Possibly related to CORS ? (Cross-origin resource sharing (CORS) is a browser mechanism which enables controlled access to resources located outside of a given domain.)

If you use the plugin within the container/vm itself (if possible) - do the images then show ?

The only way I can access the container is via webapp or ssh, may nas is headless. Other plugins seem to work ok in bridged mode.

I can add "network_mode: host" to my stack and rebuild the container to see if that helps.

[rbjtech 5284]

1 minute ago, Junglejim said:

The only way I can access the container is via webapp or ssh, may nas is headless. Other plugins seem to work ok in bridged mode.

I can add "network_mode: host" to my stack and rebuild the container to see if that helps.

I wouldn't change it for the moment - the Plugin needs to accomodate Docker for sure.    I'm sure Vic and Dave will have a fix to try..

[Junglejim 385]

11 minutes ago, Cheesegeezer said:

Ahhh i see, yeah it’s attempting to get address from 172.xxx etc. Hmmm, that looks like a bug and should use the manual address in the serverinfo shown in the console. As it then getsa new address. Is that your remote ip for the server? 

192.168.20.100 is the static IP on my network that I access my NAS with, from there each container is accessed via its port 8096 in this case. With bridged mode it then usually gets directed the the docker container ip 172.xxx.xxx.xxx

Edited March 29, 2023 by Junglejim

[Cheesegeezer 3104]

2 hours ago, rbjtech said:

I wouldn't change it for the moment - the Plugin needs to accomodate Docker for sure.    I'm sure Vic and Dave will have a fix to try..

it should be easy to fix, its just what address is being used. There are 2 addresses available in Jim’s console and it’s choosing the wrong one.

@Junglejimis that 172.xxx your emby remote IP? 
 

 

Edited March 29, 2023 by GrimReaper
Hid remote IP

[Cheesegeezer 3104]

2 minutes ago, Junglejim said:

192.168.20.100 is the static IP on my network that I access my NAS with, from there each container is accessed via its port 8096 in this case. With bridged mode it than usually gets directed the the docker container ip 172.xxx.xxx.xxx

Right might need you to do some testing then. I may need some refactoring to use the ApiClient. GetImages and let deal with the backend rather than sending raw api calls. I’ll check the code now.

[Junglejim 385]

2 hours ago, Cheesegeezer said:

it should be easy to fix, its just what address is being used. There are 2 addresses available in Jim’s console and it’s choosing the wrong one.

@Junglejimis that 172.xxx your emby remote IP? 

As you can see by the webapp address "http://192.168.20.100:8096/web/index.html#!/dashboard" that's how I access emby.

In bridged mode emby will show the internal docker container address 172.xxx.xxx.xxx.

If I change the container stack to use "network_mode: host" (I used that mode before ), emby will show the real address 192.168.20.100.

I hope that's not too confusing.

I think I can set ip in emby's network settings to but I've never had to do that. The 172.xxx crap has never bothered me, I know what the real address is

Also there is no way I can access "http://127.21.0.2:8096/" directly on my local network, that's a docker container IP.

 

Edited March 29, 2023 by GrimReaper
Server details removed

[Cheesegeezer 3104]

21 minutes ago, Junglejim said:

As you can see by the webapp address "http://192.168.20.100:8096/web/index.html#!/dashboard" that's how I access emby.

In bridged mode emby will show the internal docker container address 172.xxx.xxx.xxx.

If I change the container stack to use "network_mode: host" (I used that mode before ), emby will show the real address 192.168.20.100.

I hope that's not too confusing.

I think I can set ip in emby's network settings to but I've never had to do that. The 172.xxx crap has never bothered me, I know what the real address is

Also there is no way I can access "http://127.21.0.2:8096/" directly on my local network, that's a docker container IP.

 

perfect so if you were to copy the address for an image in the console that was red and paste that into the addressbar and then change the physical address to 192.168.blah do you get an image

 

[Junglejim 385]

4 minutes ago, Cheesegeezer said:

perfect so if you were to copy the address for an image in the console that was red and paste that into the addressbar and then change the physical address to 192.168.blah do you get an image

 

Yep

[Cheesegeezer 3104]

@Junglejimso i can see the code that is getting confused by your "bridged  mode".  

 

server_url = (server_data.IsLocalServer) ? server_data.LocalAddress : server_data.RemoteAddress;
            server_url += "/";
            console.log("=== Server url = ", server_url);

The url is returning a remote address rather than the local address.  I'm sure Vic doesn't wasn't a toggle but it might be worth adding it to "force" Use local IP's

 

[Cheesegeezer 3104]

2 minutes ago, Junglejim said:

Yep

Excellent, just need to figure out an elegant way to hand this.  You may be one of the few edge cases, so i'll propose some changes to vic and see if he is happy with it.  This is his baby after all!!

[Junglejim 385]

Just now, Cheesegeezer said:

Excellent, just need to figure out an elegant way to hand this.  You may be one of the few edge cases, so i'll propose some changes to vic and see if he is happy with it.  This is his baby after all!!

Cheers mate! I can use "network_mode: host" with the container and I'm sure that will fix it, that's not a prob.

It would be nice to get it to play nice with docker though, not everyone will like to use host mode, I'm just local so all good.

Lets see what Vic thinks.

[Cheesegeezer 3104]

4 minutes ago, Junglejim said:

Cheers mate! I can use "network_mode: host" with the container and I'm sure that will fix it, that's not a prob.

It would be nice to get it to play nice with docker though, not everyone will like to use host mode, I'm just local so all good.

Lets see what Vic thinks.

I'm gonna fire an old version 0.0.0.8 as this is the latest version i have.  and i'll call it 0.0.0.8jj  for you to test to see if it fixes it.

standby.....

 

EDIT: YOUR TEST VERSION WILL BE 0.0.0.1

Edited March 29, 2023 by Cheesegeezer

[Cheesegeezer 3104]

8 minutes ago, Junglejim said:

Cheers mate! I can use "network_mode: host" with the container and I'm sure that will fix it, that's not a prob.

It would be nice to get it to play nice with docker though, not everyone will like to use host mode, I'm just local so all good.

Lets see what Vic thinks.

Does this description read correctly?