Turkushan-auth

Self-hosted forward-auth login portal that adds single sign-on and per-site access approval to subdomains behind Nginx Proxy Manager, giving homelab users a…

  • Network Services
  • Security
Self-hosted forward-auth login portal that adds single sign-on and per-site access approval to subdomains behind Nginx Proxy Manager, giving homelab users a lightweight way to protect multiple sites with one login.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
77last commit 10 days ago
Popular
102 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
2
Open issues
4
Last commit
2026-11-10
Latest release
v1.3.0
License
MIT
Activity
declining

Checked yesterday - source: GitHub (turkushan490/turkushan-auth)

Resources & Compatibility

Requirements not published yet.

Checked 52 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Single container Use the single container as the forward-auth service for Nginx Proxy Manager subdomains; SQLite data is stored in /data and no database server or Redis is required. source
  • Runtime SQLite data is stored in /data; no external database, Redis, or compose file is required. source
  • Data storage SQLite data is stored in /data; no separate database server, Redis, or compose file is required. source
  • Container & storage Single container with no compose file needed: the Go backend and Svelte frontend ship as one binary, and the SQLite database is stored in the /data directory. source
  • First install Everything runs in one container: a Go backend and Svelte frontend in a single binary, with SQLite data in /data — no database server, Redis, or compose file required. source

Fetched 10 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Turkushan-auth require a separate database or Redis?

No. It runs as one container with SQLite stored in /data, and no database server, Redis, or compose file is required.

How does Turkushan-auth keep a user signed in across multiple subdomains?

It uses one login and a single session cookie across your subdomains. After signing in, visitors return to the page they originally opened.

Can access to a site be granted automatically by Discord role?

Yes. You can enable Discord login and create a group with a Discord role auto-add rule for selected sites. Access is granted when a user signs in with Discord and removed after the role is taken away at the next Discord sign-in.

How do I configure Nginx Proxy Manager for a new site?

The admin panel can add sites with a ready-to-paste Nginx Proxy Manager config and a Copy button.

What email provider can I use for verification and password resets?

It can send email through any SMTP provider for address verification and password resets.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads