[{"data":1,"prerenderedAt":189},["ShallowReactive",2],{"seo-verification":3,"blog-self-host-lldap-vps-ldap-directory-ma-en":6,"promo-bar-likely":188},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-self-host-lldap-vps-ldap-directory-ma-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"noindex":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":27,"featuredImage":29,"bgImage":30,"posterImage":31,"relatedSolution":32,"intro":35,"keyPoints":36,"sections":37,"ctaTitle":124,"ctaBody":125,"ctaButton":126,"ctaUrl":127,"relatedPosts":128},584,"self-host-lldap-vps-ldap-directory",{"fr":12,"en":10,"ar":13,"es":14},"self-host-lldap-vps","استضافة-lldap-على-vps","autoalojar-lldap-vps-directorio-ldap","LLDAP on a VPS: a lightweight LDAP directory for your apps","Install LLDAP on a VPS with Docker Compose: one account for Authelia, Gitea and Nextcloud, a web interface over HTTPS and an LDAP port kept private.",7,0,false,"2026-11-18T00:00:00+00:00","2026-11-20T14:16:42+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},"Self-hosting","self-hosting","bg-indigo-500\u002F10 text-indigo-400","cloud",[28],{"id":17,"name":23,"slug":24,"color":25,"icon":26},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fself-host-lldap-vps-poster.svg",{"categorySlug":33,"appSlug":34},"cybersecurity-bastion","lldap","Every self-hosted application arrives with its own user list: a Gitea account, a Nextcloud account, a Grafana account, and as many passwords to revoke the day someone leaves the team. An LDAP directory has solved this for twenty years, but OpenLDAP puts most small teams off. LLDAP keeps the essentials in a single lightweight container. This guide installs it on a VPS with Docker Compose, publishes its interface over HTTPS behind nginx, keeps the LDAP port private and connects your applications to it.",[],[38,42,52,83,86,102,106,109,112,115,118,121],{"type":39,"title":40,"body":41},"h2","What LLDAP does","LLDAP is a free directory server written in Rust. It stores users and groups in an SQLite database, presents them to applications over the LDAP protocol, and gives administrators a web interface to manage them. It does not try to do everything: no schema to write, no replication, no fine-grained ACLs. It does what Authelia, Gitea, Nextcloud, Keycloak or Jellyfin need — check a password, list the members of a group — and nothing more.",{"type":43,"title":44,"items":45},"ul","What LLDAP gives you",[46,47,48,49,50,51],"**One account per person** — the same username and password in all your applications.","**Offboarding in one click** — disable the account in LLDAP and access closes everywhere.","**Groups that grant access** — one group per application, and each application only lets its members in.","**A web interface** — create, edit and organise accounts without ever writing an LDIF file.","**Self-service reset** — each user changes their password by email.","**A tiny footprint** — a few megabytes of memory, next to the applications it serves.",{"type":53,"title":54,"headers":55,"rows":59},"comparison","Local accounts, OpenLDAP or LLDAP",[5,56,57,58],"Local accounts per application","OpenLDAP","LLDAP",[60,64,69,74,79],[61,62,63,63],"Accounts to manage","One per application","One per person",[65,66,67,68],"Administration","In each application","LDIF files and command line","Web interface",[70,71,72,73],"Getting started","None","Schemas and ACLs to write","One container and four variables",[75,76,77,78],"Memory at rest","—","A few tens of MB","A few MB",[80,81,82,82],"When someone leaves","Account to close everywhere","A single account",{"type":39,"title":84,"body":85},"Prepare the server","An Ubuntu 24.04 VPS with 1 GB of RAM is plenty: LLDAP uses a few megabytes, and it will usually share the machine with the applications it serves. Install Docker and the Compose plugin, and plan a subdomain such as `ldap.example.com` pointing to the VPS: the administration interface must be served over HTTPS, since passwords go through it. The LDAP port itself will never be published on the Internet.",{"type":87,"title":88,"steps":89},"steps","Install LLDAP with Docker Compose",[90,93,96,99],{"title":91,"body":92},"Prepare the folder and the .env file","Three secrets: the password of the `admin` account, the key that signs interface sessions and the seed of the server's private key.\n```bash\nmkdir -p \u002Fopt\u002Flldap && cd \u002Fopt\u002Flldap\ncat > .env \u003C\u003CEOF\nADMIN_PASSWORD=$(openssl rand -hex 16)\nJWT_SECRET=$(openssl rand -hex 32)\nKEY_SEED=$(openssl rand -hex 32)\nEOF\nchmod 600 .env\n```",{"title":94,"body":95},"Write the docker-compose.yml file","A single service. Both ports are only published on the loopback: the web interface (17170) will go through nginx, and the LDAP port (3890) stays reserved for the VPS. Replace `dc=example,dc=com` with the base of your choice, for example `dc=yourcompany,dc=com`.\n```yaml\nservices:\n  lldap:\n    image: lldap\u002Flldap:v0.6.3-alpine\n    restart: unless-stopped\n    ports:\n      - \"127.0.0.1:17170:17170\"\n      - \"127.0.0.1:3890:3890\"\n    environment:\n      TZ: UTC\n      LLDAP_LDAP_BASE_DN: \"dc=example,dc=com\"\n      LLDAP_LDAP_USER_PASS: ${ADMIN_PASSWORD}\n      LLDAP_JWT_SECRET: ${JWT_SECRET}\n      LLDAP_KEY_SEED: ${KEY_SEED}\n      LLDAP_HTTP_URL: \"https:\u002F\u002Fldap.example.com\"\n    volumes:\n      - lldap-data:\u002Fdata\n    networks:\n      - lldap\nnetworks:\n  lldap:\n    name: lldap\nvolumes:\n  lldap-data: {}\n```",{"title":97,"body":98},"Start and check","On first start, LLDAP creates its system groups and the `admin` account with the password from the `.env` file. It answers within seconds.\n```bash\ndocker compose up -d\ndocker compose logs lldap | grep -i admin\ncurl -sI http:\u002F\u002F127.0.0.1:17170\u002F | head -n 1\n```",{"title":100,"body":101},"Test the directory over LDAP","The `lldap` Docker network lets a container reach the directory by name. `ldapwhoami` must answer with the DN of the admin account.\n```bash\ndocker run --rm --network lldap alpine:3.20 sh -c \\\n  \"apk add -q openldap-clients && ldapwhoami -x -H ldap:\u002F\u002Flldap:3890 \\\n   -D uid=admin,ou=people,dc=example,dc=com -W\"\n```",{"type":103,"title":104,"body":105},"tip","Change the admin password and keep the LDAP port private","The `LLDAP_LDAP_USER_PASS` password is only used on first start: change it afterwards in the interface and it will no longer be overwritten. And never publish port 3890 on `0.0.0.0`: LDAP without TLS carries passwords in clear text, and your applications have no need to reach it from the Internet.",{"type":39,"title":107,"body":108},"Publish the interface over HTTPS behind nginx","Get a certificate with certbot (`certbot certonly --nginx -d ldap.example.com`), then declare a server block that forwards to local port 17170. Remember to put the same address in `LLDAP_HTTP_URL`: password reset links use it.\n```nginx\nserver {\n    listen 443 ssl;\n    server_name ldap.example.com;\n    ssl_certificate     \u002Fetc\u002Fletsencrypt\u002Flive\u002Fldap.example.com\u002Ffullchain.pem;\n    ssl_certificate_key \u002Fetc\u002Fletsencrypt\u002Flive\u002Fldap.example.com\u002Fprivkey.pem;\n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:17170;\n        proxy_set_header Host $host;\n        proxy_set_header X-Forwarded-Proto https;\n    }\n}\n```",{"type":39,"title":110,"body":111},"Connect your applications to the directory","First create, for each application, a service account (for example `svc-gitea`) and put it in the `lldap_strict_readonly` group: it can read the directory without changing anything. Then attach the application's container to the `lldap` network and enter the directory in its authentication settings:\n```bash\ndocker network connect lldap gitea\n# Server URL     : ldap:\u002F\u002Flldap:3890\n# Bind DN        : uid=svc-gitea,ou=people,dc=example,dc=com\n# User base      : ou=people,dc=example,dc=com\n# Filter         : (&(objectClass=person)(uid=%s))\n```\n\nThe same pattern works for Nextcloud (the LDAP user and group backend app), Authelia (`authentication_backend.ldap` with the `lldap` implementation) or Keycloak (LDAP user federation). To let only some users in, add a `memberOf` condition on the application's group to the filter.",{"type":39,"title":113,"body":114},"Enable password reset by email","Without an SMTP server, only the administrator can change a forgotten password. Add the following variables to the `lldap` service, with a sending account from your mail provider, then run `docker compose up -d` again: the “Forgot password” link appears on the login screen, and the email it sends points to the address in `LLDAP_HTTP_URL`.\n```yaml\n    environment:\n      LLDAP_SMTP_OPTIONS__ENABLE_PASSWORD_RESET: \"true\"\n      LLDAP_SMTP_OPTIONS__SERVER: smtp.example.com\n      LLDAP_SMTP_OPTIONS__PORT: \"587\"\n      LLDAP_SMTP_OPTIONS__SMTP_ENCRYPTION: STARTTLS\n      LLDAP_SMTP_OPTIONS__USER: ldap@example.com\n      LLDAP_SMTP_OPTIONS__PASSWORD: ${SMTP_PASSWORD}\n      LLDAP_SMTP_OPTIONS__FROM: \"LLDAP \u003Cldap@example.com>\"\n```\n\nTest with an ordinary account before announcing the feature to the team: a link pointing to `localhost` means the public address was not declared correctly.",{"type":39,"title":116,"body":117},"Example: Authelia backed by LLDAP","Authelia knows LLDAP and offers a dedicated implementation that sets the filters and attributes for you. The `svc-authelia` service account must belong to the `lldap_password_manager` group if you want users to change their password from Authelia; otherwise `lldap_strict_readonly` is enough.\n```yaml\nauthentication_backend:\n  ldap:\n    implementation: lldap\n    address: ldap:\u002F\u002Flldap:3890\n    base_dn: dc=example,dc=com\n    user: uid=svc-authelia,ou=people,dc=example,dc=com\n    password: '\u003Cservice-account-password>'\n```\n\nFinally attach the Authelia container to the `lldap` network, restart it and sign in with an account created in LLDAP: the same identity now opens every application protected by Authelia.",{"type":39,"title":119,"body":120},"Backup and updates","LLDAP's whole state lives in the `lldap-data` volume: the SQLite database, the configuration and the server's private key. An archive of the volume, with LLDAP stopped for a few seconds, is enough to restore everything.\n```bash\ncd \u002Fopt\u002Flldap\ndocker compose stop lldap\ndocker run --rm -v lldap_lldap-data:\u002Fdata -v \"$PWD\":\u002Fbackup alpine:3.20 \\\n  tar czf \u002Fbackup\u002Flldap-$(date +%F).tar.gz -C \u002Fdata .\ndocker compose start lldap\n```\n\nTo update, change the image tag in `docker-compose.yml`, read the release notes, then run `docker compose pull && docker compose up -d`: LLDAP migrates its database on start.",{"type":39,"title":122,"body":123},"LLDAP in one click on ServOrbit","The ServOrbit Marketplace installs exactly this stack: the official `lldap\u002Flldap` image, secrets drawn at install time, an `admin` account created with a generated password, the web interface published over HTTPS on a subdomain of your domain or on the VPS's free subdomain, and the LDAP port kept on the loopback. The password is shown in your client area; all that is left is to create your users and connect your applications.","One directory for all your applications","A ServOrbit Ubuntu 24.04 VPS with 1 GB of RAM is enough for LLDAP. One-click install from the Marketplace, HTTPS on your domain or on the VPS's free subdomain, LDAP port kept private.","Install LLDAP","\u002Fapplications\u002Fcybersecurity-bastion\u002Flldap",[129,153,170],{"id":130,"slug":131,"slugs":132,"title":136,"excerpt":137,"readTime":138,"views":139,"isPinned":19,"noindex":19,"publishedAt":140,"updatedAt":141,"category":142,"categories":148,"featuredImage":29,"bgImage":30,"posterImage":150,"relatedSolution":151},162,"self-host-authelia-on-a-vps-mfa-and-sso-for-your-whole-stack",{"fr":133,"en":131,"ar":134,"es":135},"self-host-authelia-vps","استضافة-authelia-على-vps-مصادقة-ثنائية-ودخول-موحد-لمنظومتك","alojar-authelia-en-un-vps","Self-hosting Authelia on a VPS: MFA and SSO for your entire stack","Deploy Authelia on a VPS with Docker Compose: TOTP, WebAuthn\u002Fpasskey, OIDC, LLDAP migration, Prometheus monitoring, and comparison with Authentik.",10,6,"2026-07-04T00:00:00+00:00","2026-11-20T14:17:07+00:00",{"id":143,"name":144,"slug":145,"color":146,"icon":147},8,"Security & Monitoring","securite-monitoring","bg-rose-500\u002F10 text-rose-400","security",[149],{"id":143,"name":144,"slug":145,"color":146,"icon":147},"\u002Fblog\u002Fcovers\u002Fself-host-authelia-vps-poster.svg",{"categorySlug":147,"appSlug":152},"authelia",{"id":154,"slug":155,"slugs":156,"title":160,"excerpt":161,"readTime":138,"views":18,"isPinned":19,"noindex":19,"publishedAt":162,"updatedAt":163,"category":164,"categories":165,"featuredImage":29,"bgImage":30,"posterImage":167,"relatedSolution":168},112,"deploy-keycloak-for-sso-on-your-vps",{"fr":157,"en":155,"ar":158,"es":159},"keycloak-sso-vps","نشر-keycloak-لتسجيل-الدخول-الموحد-sso-على-خادمك-vps","desplegar-keycloak-sso-en-un-vps","Deploy Keycloak for SSO on Your VPS","Deploy Keycloak on your VPS for enterprise-grade SSO: OIDC, SAML, realms and federation. A complete Docker guide and comparison.","2026-02-28T00:00:00+00:00","2026-11-04T16:30:25+00:00",{"id":143,"name":144,"slug":145,"color":146,"icon":147},[166],{"id":143,"name":144,"slug":145,"color":146,"icon":147},"\u002Fblog\u002Fcovers\u002Fkeycloak-sso-vps-poster.svg",{"categorySlug":33,"appSlug":169},"keycloak",{"id":171,"slug":172,"slugs":173,"title":177,"excerpt":178,"readTime":139,"views":179,"isPinned":19,"noindex":19,"publishedAt":180,"updatedAt":181,"category":182,"categories":183,"featuredImage":29,"bgImage":30,"posterImage":185,"relatedSolution":186},272,"authentik-authelia-or-keycloak-choosing-your-sso-on-vps",{"fr":174,"en":172,"ar":175,"es":176},"authentik-vs-authelia-keycloak-sso-vps-2026","authentik-أو-authelia-أو-keycloak-اختيار-sso-على-vps","authentik-authelia-o-keycloak-elegir-sso-en-vps","Authentik, Authelia or Keycloak: Choosing Your SSO on VPS","Authentik, Authelia or Keycloak on VPS: compare real memory footprint, covered protocols and Keycloak 26.7.1 CVEs to choose the right self-hosted SSO.",3,"2026-08-16T00:00:00+00:00","2026-11-04T16:30:27+00:00",{"id":143,"name":144,"slug":145,"color":146,"icon":147},[184],{"id":143,"name":144,"slug":145,"color":146,"icon":147},"\u002Fblog\u002Fcovers\u002Fauthentik-vs-authelia-keycloak-sso-vps-2026-poster.svg",{"categorySlug":33,"appSlug":187},"authentik",true,1795186180687]