eds

That variable is a beautiful addition, thanks for that. Docker update to NPM seems to fix my bigger issue, but now I am getting an issue with some buttons/images/labels. When using ssl its even worse. Out of curiosity what are your settings for the wallabag docker? Are you using the domain name name or ip in the settings? In NPM are you using ssl cert?

These changes are not working for me. Nginx Proxy Manager makes the whole ssl certificate, port forwarding process a snap. Confused as to why this is not working using npm.

Ah! You're right. Once I actually added the IP address in place of <IP> that did it. Thanks! EDIT One other thing I wonder if you can help me with.... I'm using nginx proxy manager to handle the app with my domain so I can access on the wan side, but this appears to be failing. Any ideas?

Hey OP, Thanks for wallabag docker. I've been dying for an app like this. Comparing what I installed to the actual program, the docker appears to be missing images and other textures. Was that an oversight or did I get something wrong here?

If that's the case I'm showing b2net and igb. Agreed.

I tried editing the line model type = 'virtio' by changing the value to 'e1000' and 'vmxnet3' and neither worked. I am a little lost here. I, of course, assume the drivers are installed in the Unraid host since this worked once before after passing through the nic. In addition, if the drivers were not installed in Unraid wouldn't the OS have an issue with network connects? How to check to see what network drivers are installed in Unraid?

I think folks may not be understanding the true nature of this problem. The vm is not looking for a driver. The vm is unable to see the nic. Again, this was solved in the previous version on unraid. All I had to do is pass through the nic so that the VM can see it (as seen in the post above) So the previous posts about needed a driver is moot. The centOS vm is unable to see the nic. Without seeing the nic, what good is a driver?

That did the trick. And it appears the youtube plugin was broken somehow. All is working well now. Thanks!

None of the links for YouTube work. Other sites work fine. I look to the plugin and I see no options unlike others. Could the plugin be broken? If so, how to fix?

This issue is pretty ridiculous. I had virtual machine capability on my qnap nas and it didn't have any of these issues. I thought Unraid would be much better in the implementation. Go figure it's worse! And the video in this thread which used to work is now useless.

This is interesting. When I paste a link it search for downloads for about five seconds and then disappears and nothing loads. I think this has been since the update to Unraid 6.8.1. Docker does not indicate update needed. I can't see any issue in the logs.

What your version? My build date is Feb 6 of this year. Docker is not reporting an updates.

Really surprised (and disappointed) no one can help with this issue.

Curious to know if anyone else if having a problem with this docker and youtube. Used to work flawlessly, now it doesn't. I thought, perhaps it was a network issue, but I did a download from another service and had no problems. So, is anyone having issues with YouTube?

Anyone able to get CentOS vm to see the network adapter?

replace names in json.list ... Dude, this is what I needed. Now I think I'm good. Thanks.

I'm running into this problem again - hope you can help. Passing through the nic no longer appears to be working with the update to 6.8.1. How can I emulate one of the existing generic nic's even if it means editing the xml?

As indicated in my post above. this line: docker exec -it guide2go ./config/cronjob.sh Produces the following: sed: /guide2go/CBLguide.json: No such file or directory sed: /guide2go/CBLguide.json: No such file or directory System info ----------- 2020/01/25 11:54:48 [guide2go] Version: 1.0.6 Get data from Schedules Direct ------------------------------ 2020/01/25 11:54:48 [guide2go] Config file: /guide2go/CBLguide.json 2020/01/25 11:54:48 [ERROR] - open /guide2go/CBLguide.json: no such file or directory sed: /guide2go/SATguide.json: No such file or directory sed: /guide2go/SATguide.json: No such file or directory System info ----------- 2020/01/25 11:54:48 [guide2go] Version: 1.0.6 Get data from Schedules Direct ------------------------------ 2020/01/25 11:54:48 [guide2go] Config file: /guide2go/SATguide.json 2020/01/25 11:54:48 [ERROR] - open /guide2go/SATguide.json: no such file or directory sed: /guide2go/SATSport.json: No such file or directory sed: /guide2go/SATSport.json: No such file or directory System info ----------- 2020/01/25 11:54:48 [guide2go] Version: 1.0.6 Get data from Schedules Direct ------------------------------ 2020/01/25 11:54:48 [guide2go] Config file: /guide2go/SATSport.json 2020/01/25 11:54:48 [ERROR] - open /guide2go/SATSport.json: no such file or directory curl: (7) Failed to connect to 192.168.1.2 port 34400: Operation timed out curl: (7) Failed to connect to 192.168.1.2 port 34400: Operation timed out Is this to be expected? Also, all this command does docker exec -it guide2go -configure /guide2go/lineup_name.json Is log me into schedules direct then offers options to: Edit configuration file ----------------------- 1. Change credentials from Schedules Direct 2. Add lineup 3. Remove lineup 4. Manage channels 0. Exit Select entry: 0 I don't want to do any of these things so I exit. This creates a json file with my username and password. Now what?

Thanks for getting back to me so quickly. So I decided for simplicity. I just need the guide and I have an SD account. So with the guide2go docker I ran all the necessary commands, created the json and have the cronjob script. When I run docker exec -it guide2go ./config/cronjob.sh, this is what I get: docker exec -it guide2go ./config/cronjob.sh sed: /guide2go/CBLguide.json: No such file or directory sed: /guide2go/CBLguide.json: No such file or directory System info ----------- 2020/01/25 00:37:14 [guide2go] Version: 1.0.6 Get data from Schedules Direct ------------------------------ 2020/01/25 00:37:14 [guide2go] Config file: /guide2go/CBLguide.json 2020/01/25 00:37:14 [ERROR] - open /guide2go/CBLguide.json: no such file or directory sed: /guide2go/SATguide.json: No such file or directory sed: /guide2go/SATguide.json: No such file or directory System info ----------- 2020/01/25 00:37:14 [guide2go] Version: 1.0.6 Get data from Schedules Direct ------------------------------ 2020/01/25 00:37:14 [guide2go] Config file: /guide2go/SATguide.json 2020/01/25 00:37:14 [ERROR] - open /guide2go/SATguide.json: no such file or directory sed: /guide2go/SATSport.json: No such file or directory sed: /guide2go/SATSport.json: No such file or directory System info ----------- 2020/01/25 00:37:14 [guide2go] Version: 1.0.6 Get data from Schedules Direct ------------------------------ 2020/01/25 00:37:14 [guide2go] Config file: /guide2go/SATSport.json 2020/01/25 00:37:14 [ERROR] - open /guide2go/SATSport.json: no such file or directory curl: (7) Failed to connect to 192.168.1.2 port 34400: Operation timed out curl: (7) Failed to connect to 192.168.1.2 port 34400: Operation timed out Is this to be expected? Not sure what those errors are about. I created a json file when the docker connected to SD. Also, I am not clear where the xml will be downloaded. The xmltv schedules direct docker allowed users to assign a custom directory. This does not appear to be the case here, so I assume it will download into the guide2go directory?

Hi Alturismo, For those of us not well skilled in docker and just want guide data for plex, is your guide2go app sufficient or should I use xteve_g2g_owi? What command to run at the unraid command prompt to get schedules direct account all setup with the docker? Thanks.

Wish everyone could be so lucky. Still crickets for my issue.

Had been using @L0rdRaiden's video to pass through a nic to my CentOS vm. Since upgrading to 6.8.1 that guide no longer appears to work. My XML is here: <interface type='bridge'> <mac address='52:54:00:fd:f4:bb'/> <source bridge='br1'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> What appears most obvious to me is the 'hostdev' tag is no longer in use on the xml. How to fix?

It's news if you're using that plugin like a lot of other people.

Upgraded from 6.8.0 to 6.8.1 and got the "killed" error as detailed in a few posts above. Put the USB in a windows machine which ran scan disk and found no errors. Popped the USB back in the server and it booted up. My opinion is the server just needed to be shut down instead of a warm reboot. In other news, nvidia plugin would not work and the only version they had was 6.8.0 so I installed version of the nvidia plugin and now I'm back to 6.8.0 of unraid. Damn!

Yes, the drive had mostly empty space so it does make sense the restore would move 23% - 100%. Good to know that urbackup would take that into consideration on the restore. Thanks again.