Is it possible to add the German channels Magenta Sport 1-18 and the channel “der aktionär” does not have EPG in any source.
Thanks in advance :)
Brought to you by Jan van Straaten
Program Development - Jan van Straaten ------- Web design - Francis De Paemeleere
Supported by: servercare.nl
Just set in your config update "c" run wg++ once, then set it back to its previous value. You will find new channel list in wg++ directory
Okay thanks :) but Der Aktionär TV doenst work i can find not EPG in any source
many channel lists have it but none have any actual epg data.
looks like its a stock market channel.
if you want to add dummy(fake) epg data use the fixed.ini(misc folder).
read the fixed_info.txt file for instructions.
Okay thanks I will try it. my last question is is there EPG for Amazon Prime Sportsbar or Amazon Prime Channel in general or do I have to use the fake EPG
tvtv.us.ini(usa folder) has amazon prime channels.
when you make your channel list(open ini and read remarks) its best to refer to the site as the channel names are mostly abbreviated or use a callsign.
the channel name includes the channel number so by referring to the site u can usually figure out the channel by the logo or viewing the epg data.
sportsbar sounds like a ppv channel?
if so there prob no epg for it..
it is this one? https://uat.deraktionaer.tv/programm.html
Amazon Sportsbar is a channel in Germany which is included with the prime membership. It runs exclusive games from the Champions League, but nothing else is played there
Yes, that is the right EPG for Der Aktionär TV
i have a source that isnt public as it requires a api key.
here's the prime sportsbar(germany and italian) and the Der Aktionär TV.
data is downloaded from my server,updates once a day 00:30 my timezone(America/Halifax).
checking prime sportsbar epg it shows "Sendepause" for the next 7 days,i assume this because there no events airing within the next week?
edit:
fixed the rating value.
download again and replace ini.
Yes, that's correct, it seems that nothing is currently scheduled on Prime Sportsbar. I will test it.
After the initial tests, everything looks good so far. Thank you for your great work!
i forgot to mention that if u have any problems u can check the epg status..
https://bb199.ddns.net:15501/analyzer/analyzer.php
Okay perfect, thank you!
Hey Blackbear199, unfortunately it no longer works, can you check this? thank you.
yup.server is down.
i am at my camp(middle no where)
sorry.i tried do a remote reboot which i knew was risky.
i be back in town in few days and fix it.
i cant do it remotely.needs a hard reboot.
shud be enough epg to cover till i get it fixed.
Okay all good no problem thank you for your reply. :)
ok and again sorry.
remote reboots aint good.
i was havint issue with secure login.letsencrypt showed all good but via browser it said ssl cert expired.
i know i sudnt have done a remote reboot.i dont like doin it when its beside me.
its hung on the shutdown.fooker does it now and then.
only fix is a hard reboot via pwr button.
No worries, everything's fine! As an IT guy myself, I totally get it. These types of issues can be a real pain sometimes. Perhaps you could hook up a SwitchBot to your power button for remote hard reboots in the future. That way, when things freeze up again, you can still manage it without needing to be physically there. ;)
being it guy maybe u can help as i dont see where issue is.
i not it guy but jack of all trades.
let encrypy runs every 15 days.
last log..
this has worken fine for years ans no sudden expired cert.i dont get it as its says all good?
2024-09-16 05:00:14,779:DEBUG:certbot._internal.main:certbot version: 1.25.0
2024-09-16 05:00:14,781:DEBUG:certbot._internal.main:Location of certbot entry point: /raid/data/module/Letsencrypt/sys/venv/bin/certbot
2024-09-16 05:00:14,782:DEBUG:certbot._internal.main:Arguments: ['--config-dir', '/raid/data/MOD_CONFIG/letsencrypt', '--logs-dir', '/raid/data/MOD_CONFIG/letsencrypt/log', '--work-dir', '/raid/data/MOD_CONFIG/letsencrypt/lib']
2024-09-16 05:00:14,782:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2024-09-16 05:00:14,936:DEBUG:certbot._internal.log:Root logging level set at 30
2024-09-16 05:00:14,979:DEBUG:certbot._internal.display.obj:Notifying user: Processing /raid/data/MOD_CONFIG/letsencrypt/renewal/bb199.ddns.net.conf
2024-09-16 05:00:15,285:DEBUG:certbot._internal.plugins.selection:Requested authenticator and installer
2024-09-16 05:00:15,285:DEBUG:certbot._internal.cli:Var config_dir=/raid/data/MOD_CONFIG/letsencrypt (set by user).
2024-09-16 05:00:15,288:DEBUG:certbot._internal.cli:Var logs_dir=/raid/data/MOD_CONFIG/letsencrypt/log (set by user).
2024-09-16 05:00:15,288:DEBUG:certbot._internal.cli:Var work_dir=/raid/data/MOD_CONFIG/letsencrypt/lib (set by user).
2024-09-16 05:00:15,704:DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): r10.o.lencr.org:80
2024-09-16 05:00:16,105:DEBUG:urllib3.connectionpool:http://r10.o.lencr.org:80 "POST / HTTP/1.1" 200 504
2024-09-16 05:00:16,109:DEBUG:certbot.ocsp:OCSP response for certificate /raid/data/MOD_CONFIG/letsencrypt/archive/bb199.ddns.net/cert9.pem is signed by the certificate's issuer.
2024-09-16 05:00:16,112:DEBUG:certbot.ocsp:OCSP certificate status for /raid/data/MOD_CONFIG/letsencrypt/archive/bb199.ddns.net/cert9.pem is: OCSPCertStatus.GOOD
2024-09-16 05:00:16,154:DEBUG:certbot._internal.display.obj:Notifying user: Certificate not yet due for renewal
2024-09-16 05:00:16,157:DEBUG:certbot._internal.plugins.selection:Requested authenticator standalone and installer None
2024-09-16 05:00:16,157:DEBUG:certbot._internal.display.obj:Notifying user:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2024-09-16 05:00:16,158:DEBUG:certbot._internal.display.obj:Notifying user: The following certificates are not due for renewal yet:
2024-09-16 05:00:16,159:DEBUG:certbot._internal.display.obj:Notifying user: /raid/data/MOD_CONFIG/letsencrypt/live/bb199.ddns.net/fullchain.pem expires on 2024-10-29 (skipped)
2024-09-16 05:00:16,159:DEBUG:certbot._internal.display.obj:Notifying user: No renewals were attempted.
2024-09-16 05:00:16,160:DEBUG:certbot._internal.display.obj:Notifying user: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2024-09-16 05:00:16,161:DEBUG:certbot._internal.renewal:no renewal failures
i use a pkcs12 which i make via the web hooks.
only emby and plex use this.
why i confused (both work fine)...
why broswer says expired and letsencrypt say current got me stumped.
i deleted current certs and was doin reboot hoping it fix it.
now i dead till i go home.
use apache and gets all from the letencrypt source.
apache is using the direct path to the letencrytpt sources
as i said i am stumped at why browser sat cert expired.
worked fine for years.now dead.
cud it be a openssl isue?
my dam sever is a thecus,run fedora 12...ya acient.
think open ssl need a update?
think its like 1.1.1 now..again acient as latest like 3.x?
i could try build module(i know how) but nothing runs on the dam things as old lib files.
use a chroot to get around this,ubuntu 22.04
not sure what to do from here?
but fro letencrypt log all looks good?
?
try
https://bb199.ddns.net:15501/analyzer/analyzer.php
u will se wht i mean..wtf?
to me lets encrypt hasnt been updating.
log above says all good but lokking at actual files last modified date 7/31/2024
why all sudden this as worked fine years.
no idea as i usually figure it out.
not a it guy like u.
i learn the hard way(usually)
stackovershage usually has my answer.
Hey, I’m kind of stumped too since the Let’s Encrypt logs say everything is fine, but the browser still shows the cert as expired. One thing that comes to mind is that maybe Apache didn’t reload properly after the cert got renewed, so it’s still using the old one. You could try manually reloading Apache to see if that fixes it. Also, if your server’s time is out of sync, that might be causing some confusion with the cert’s expiration date.
I noticed you’re running an older system (Fedora 12), so it might also be worth checking if the OpenSSL version is causing any issues. I know it’s a bit tricky with old systems, but maybe give that a look too.
Hey it seems like Prime isn't working properly, I have the next dates for Prime Events here: https://www.amazon.de/b?ie=UTF8&node=22974459031 or this https://www.amazon.de/salp/championsleague/