-
Posts
91 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Jimmy90
-
-
-
14 hours ago, Zonediver said:
Example?
-
On 10/27/2018 at 8:15 PM, deaerator said:
Thank you for the help.
I had to move the keyfile temparory to that location until it was formatted and mounted. Then I deleted and did a re-boot and everything is working correctly.
You just made my day! Thanks for sharing your resolution steps! I was equally successful in that manner!
-
LibreELEC v6.7.1 working fine now with Hauppauge USB (rc2 wasn't).
Thank you CHBMB!
- 1
-
-
-
-
Dear CHBMB,
LibreElec_v6.7.1rc2 is failing to locate /dev/dvb/ on reboot.
We had the same issue with 6.7.0rc8 a while back and you fixed it by recompiling if i recall correctly.
Thanks again for you kind support "in the blind"
-
18 minutes ago, CHBMB said:
OK guys, recompiled all of the dvb builds. Also managed to build Digital Devices, using their master branch instead of their latest release.
She is buttery smooth again now! Thanks so much for your kind support CHBMB!
-
I'm in the same boat.
LibreELEC 6.7.0-RC8 + Hauppauge 955Q.
The Plex Docker errors that /dev/dvb is non-existent.
Something's obviously wrong
-
This container is flawless and so useful! Thanks for your outstanding V2 work on this ninthwalker!
-
-
Indeed, we need a Hero! This would be so much appreciated!
-
Dear ninthwalker,
Yet again, Thanks so much for your brilliant contributions to this community. Now Showing is alive and kickin' over here! Impeccable!
-Jimmy
- 1
-
Port 993 is meant to receive on IMAP (SSL), not send....
try one of those for SMTP:
SMTP Server (Outgoing Messages)
Non-Encrypted AUTH 25 (or 587)
Secure (TLS) StartTLS 587
Secure (SSL) SSL 465
EDIT: just checked for you, Time Warner Cable uses port 587 for SMTP, try that
-
-
Ok, well, I guess I was able to get it right after much trial and errors
First and foremost, your library must be impeccable in terms of ID3 tagging. I've got well over 2500 tracks in mine and to be honest, i hadn't really kept it clean since my OS X Leopard days So in the end, it took a couple of hours Pathetic....I know...
Anyhow, here's what I've done. Koel is syncing fine now, just like a homemade Spotify:
1) Used an App called TagStripper in MacOS and stripped all tags from my library (in my case, Music share). The automation process took about an hour.
2) Installed Mp3Tag software in a WIndows VM and processed my entire collection using the Action "Filename - Tag"
3) Then, followed this guide to reassign and embed Album Art as it should to my library: https://tinyapps.org/blog/windows/201409100700_batch_download_embed_cover_art.html
I'm pooped! But hey, its working now! Using /media in the settings.
Thanks for yet another much appreciated Docker contribution Binhex!
Jimmy
-
So i've mapped my /media path to /mnt/user/Music but for some reason, nothing shows up in koel's library. I've tried scanning for for /media , /media/ or even media in the settings, but no joy
No permission issues with the Music share either, i triple checked that.
Anyone? Thanks
-
Thank you for maintaining this docker Ninthwalker! It's never failed to deliver weekly since day 1 with absolutely zero interaction on my part! Very much appreciated sir!
-
-
you need to make sure your browser is set to use privoxy otherwise you wont be able to get to the config page.
...and then you proceed to https://www.privoxy.org/config/ and BINGO! Thanks very much Binhex! Finally found it again!
-
By the way, anyone getting such an error when attempting to load privoxy in the browser?
Invalid header received from client.
Yup same here for some time now. Something must've changed with the latest update....
i think you guys might be misunderstanding how to use privoxy, you dont point your browser AT privoxy, you configure the browser to USE the proxy, if you just try going to http://<server ip>:8118 then yes you will receive the above message, instead you should be doing something like this (example is for chrome):-
To set up or change network connections, follow these steps:
Click the Chrome menu on the browser toolbar.
Select Settings.
Click Show advanced settings.
In the "Network" section, click Change proxy settings
Now in LAN settings enter in ip of your server and port of 8118
Click OK and test
Tested and working with the latest docker image.
Thanks Binhex, I was already very familiar with that part But in the past, clicking on the server:8118 link would take you to the config page where you could adjust filters and such. I've been using your outstanding container since day 1 and I'm pretty sure i didn't dream this one up!
And for the record, yes, you are absolutely correct, the proxy functions as designed though, so no worries here
-
By the way, anyone getting such an error when attempting to load privoxy in the browser?
Invalid header received from client.
Yup same here for some time now. Something must've changed with the latest update....
-
That's a very good question! But I'm afraid I don't have the savvy answer for it.
Perhaps JonP or someone else with equal Qemu-KVM wisdom will jump in to provide some guidance on the matter.
"Unmountable: No file system" (SOLVED)
in General Support
Posted
Dear johnnie.black,
You're a Life Saver! This thread made my day! I had honestly been pulling my hair for 2 whopping days here with this!
Thanks a Bunch!