Skip to content

active 2025-03-092026-03-09 (UTC)

Partial coverage20,270 / 26,010 hourly files (78%) · 2 absent upstream · 5,737 failed, retryable2023-08-252026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
148
Pushes
0
Pull requests
0
Issues
80
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 366 days from 2025-03-09 to 2026-03-09. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 80 total, peak 5 in a day. Comments: 68 total, peak 8 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
keppler720043
TCRserver45009
freswa180010
Systemhaus-EHST4002
patrick-fox3001
bodeme2000
twink0r1001
speedloc1001
n0lz1000
PhilineGraystone1001

Recent activity

Latest issues, pull requests and releases

  • Issue#125keppler2026-03-09 14:25
    After uninstalling LAC, it is no longer possible to log in to the server.
  • Issue#125TCRserver2026-03-08 18:08
    After uninstalling LAC, it is no longer possible to log in to the server.
  • Issue comment#119keppler2026-03-06 15:26
    Can’t add TSIG key
  • Issue comment#118keppler2026-03-06 08:46
    Wrong port description for mail server
  • Issue comment#122freswa2026-03-05 17:12
    Chaging password of customer leads to `runtime_error`
  • Issue comment#122keppler2026-03-05 16:50
    Chaging password of customer leads to `runtime_error`
  • Issue#114freswa2026-01-12 19:28
    3 out of 16 servers reconnect endlessly due to `certificate expired` on lccp port
  • Issue#113keppler2025-12-12 14:38
    Error message after restart
  • Issue comment#113keppler2025-12-12 14:38
    Error message after restart
  • Issue comment#113TCRserver2025-12-12 12:08
    Error message after restart
  • Issue comment#113keppler2025-12-12 09:54
    Error message after restart
  • Issue#113TCRserver2025-12-12 09:40
    Error message after restart
  • Issue#86keppler2025-12-02 11:33
    Missig REST-API IFRAME Examples
  • Issue#96keppler2025-12-02 10:24
    SCP / SFTP access not possible, /usr/bin/scponly does not exist
  • Issue#98keppler2025-11-20 13:39
    Automatically increase customer number
  • Issue#91keppler2025-11-20 08:10
    Overwriting the backup options of a contract is not saved completely.
  • Issue comment#91keppler2025-11-20 08:10
    Overwriting the backup options of a contract is not saved completely.
  • Issue comment#99PhilineGraystone2025-11-17 15:20
    GUI not usable if LiveConfig is running behind reverse proxy
  • Issue#109TCRserver2025-11-13 18:53
    Logentry: Object not found or not authorised
  • Issue comment#106twink0r2025-11-09 17:15
    LiveConfig 3.1.0 fails to start due to database upgrade error (“Object not found or not authorised for it”)
  • Issue comment#106keppler2025-11-09 11:49
    LiveConfig 3.1.0 fails to start due to database upgrade error (“Object not found or not authorised for it”)
  • Issue comment#104speedloc2025-11-07 23:47
    Debian 13 / Migrating to Dovecot 2.4 Quota
  • Issue#104bodeme2025-11-03 11:44
    Debian 13 / Migrating to Dovecot 2.4 Quota
  • Issue#94keppler2025-10-31 09:42
    Activate backup - no feedback and no activation
  • Issue comment#81freswa2025-10-08 11:08
    Letsencrypt certificate fails to issue due to `Curl easy perform failed: Timeout was reached`

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.