[GH-ISSUE #41] frontend docker error #24

Closed
opened 2026-02-27 08:14:40 +03:00 by kerem · 6 comments
Owner

Originally created by @nikhil96widhani on GitHub (Sep 20, 2021).
Original GitHub issue: https://github.com/lldap/lldap/issues/41

Hi thanks for making this. I was looking to something lightweight for my 10 user home-server. Unfortunately i am not able to make it work using docker compose. Here is my compose

services:
  lldap:
    image: nitnelave/lldap
    container_name: lldap
    user: "1000:1000"
    ports:
      # For LDAP
      - 3890:3890
      # For the web front-end
      - 17170:17170
    volumes:
      - /home/test123/volumes/lldap/data:/data
    environment:
      - JWT_SECRET=test123
      - LDAP_USER_PASS=test123
      - LDAP_BASE_DN=dc= test123,dc=com

i cannot access web app as i get error: No such file or directory (os error 2)
logs show internal server error
i have also created lldap_config.toml in data dir

Originally created by @nikhil96widhani on GitHub (Sep 20, 2021). Original GitHub issue: https://github.com/lldap/lldap/issues/41 Hi thanks for making this. I was looking to something lightweight for my 10 user home-server. Unfortunately i am not able to make it work using docker compose. Here is my compose ``` services: lldap: image: nitnelave/lldap container_name: lldap user: "1000:1000" ports: # For LDAP - 3890:3890 # For the web front-end - 17170:17170 volumes: - /home/test123/volumes/lldap/data:/data environment: - JWT_SECRET=test123 - LDAP_USER_PASS=test123 - LDAP_BASE_DN=dc= test123,dc=com ``` i cannot access web app as i get error: No such file or directory (os error 2) logs show internal server error i have also created lldap_config.toml in data dir
kerem closed this issue 2026-02-27 08:14:40 +03:00
Author
Owner

@nikhil96widhani commented on GitHub (Sep 22, 2021):

Can anyone help me to solve this please?

<!-- gh-comment-id:924508262 --> @nikhil96widhani commented on GitHub (Sep 22, 2021): Can anyone help me to solve this please?
Author
Owner

@nitnelave commented on GitHub (Sep 22, 2021):

Hi!

Thanks for the report! Keep in mind that I'm doing this in my spare time, as a best effort, so there's no need to update the issue merely a day later.

Also note that the first line of the README is "WARNING: This project is still WIP, it's still missing core functionality. For updates, follow @nitnelave1." The project is not yet functional, I haven't made an official release for a good reason.

As for your problem, could you paste the server error log? That way we can see which file is missing.

<!-- gh-comment-id:924753009 --> @nitnelave commented on GitHub (Sep 22, 2021): Hi! Thanks for the report! Keep in mind that I'm doing this in my spare time, as a best effort, so there's no need to update the issue merely a day later. Also note that the first line of the README is "WARNING: This project is still WIP, it's still missing core functionality. For updates, follow @nitnelave1." The project is *not yet functional*, I haven't made an official release for a good reason. As for your problem, could you paste the server error log? That way we can see which file is missing.
Author
Owner

@nikhil96widhani commented on GitHub (Sep 22, 2021):

Hi thank you for the reply, I understand the repo is maintained by one person and there might be bugs. I will still like to use your docker and solve the issues for me because the idea of this project is exactly what i was looking at.

Regarding the issue i updated my docker compose in above email and server logs show no error basically. I am pasting log below and let me know if you need anything to solve my issue.

Sep 22 12:56:00.933  INFO CREATE TABLE IF NOT …; rows: 0, elapsed: 263.339µs


CREATE TABLE IF NOT EXISTS `jwt_storage` (

  `jwt_hash` integer NOT NULL PRIMARY KEY,

  `user_id` text(255) NOT NULL,

  `expiry_date` text NOT NULL,

  `blacklisted` integer DEFAULT FALSE NOT NULL,

  FOREIGN KEY (`user_id`) REFERENCES `users` (`user_id`) ON DELETE CASCADE ON

  UPDATE

    CASCADE

)

  

Sep 22 12:56:00.934  INFO SELECT `jwt_hash` FROM `jwt_storage`; rows: 0, elapsed: 318.005µs  

Sep 22 12:56:00.935  INFO Starting 1 workers    

Sep 22 12:56:00.936  INFO Starting "ldap" service on 0.0.0.0:3890    

Sep 22 12:56:00.936  INFO Starting "http" service on 0.0.0.0:17170    

Sep 22 12:56:00.936  INFO DB Cleanup Cron started    

files inside data folder are:

lldap_config.toml  private_key  users.db  users.db-shm  users.db-wal

when i open the the ip:port i get this error

No such file or directory (os error 2)
<!-- gh-comment-id:924905640 --> @nikhil96widhani commented on GitHub (Sep 22, 2021): Hi thank you for the reply, I understand the repo is maintained by one person and there might be bugs. I will still like to use your docker and solve the issues for me because the idea of this project is exactly what i was looking at. Regarding the issue i updated my docker compose in above email and server logs show no error basically. I am pasting log below and let me know if you need anything to solve my issue. ``` Sep 22 12:56:00.933 INFO CREATE TABLE IF NOT …; rows: 0, elapsed: 263.339µs CREATE TABLE IF NOT EXISTS `jwt_storage` ( `jwt_hash` integer NOT NULL PRIMARY KEY, `user_id` text(255) NOT NULL, `expiry_date` text NOT NULL, `blacklisted` integer DEFAULT FALSE NOT NULL, FOREIGN KEY (`user_id`) REFERENCES `users` (`user_id`) ON DELETE CASCADE ON UPDATE CASCADE ) Sep 22 12:56:00.934 INFO SELECT `jwt_hash` FROM `jwt_storage`; rows: 0, elapsed: 318.005µs Sep 22 12:56:00.935 INFO Starting 1 workers Sep 22 12:56:00.936 INFO Starting "ldap" service on 0.0.0.0:3890 Sep 22 12:56:00.936 INFO Starting "http" service on 0.0.0.0:17170 Sep 22 12:56:00.936 INFO DB Cleanup Cron started ``` files inside data folder are: ``` lldap_config.toml private_key users.db users.db-shm users.db-wal ``` when i open the the ip:port i get this error ``` No such file or directory (os error 2) ```
Author
Owner

@nitnelave commented on GitHub (Sep 22, 2021):

Try again with the new version that was pushed to docker, it should fix things.

<!-- gh-comment-id:925016346 --> @nitnelave commented on GitHub (Sep 22, 2021): Try again with the new version that was pushed to docker, it should fix things.
Author
Owner

@nikhil96widhani commented on GitHub (Sep 22, 2021):

It works, Thanks So much. I will test it today to see how well it integrates with Nextcloud and jellyfin

<!-- gh-comment-id:925026229 --> @nikhil96widhani commented on GitHub (Sep 22, 2021): It works, Thanks So much. I will test it today to see how well it integrates with Nextcloud and jellyfin
Author
Owner

@nitnelave commented on GitHub (Sep 22, 2021):

Thanks for the feedback, but once again, it doesn't work yet, the basic features are not complete! I invite you to follow https://github.com/nitnelave/lldap/milestone/1 to see how far we are to basic functionality, though, and I'd love your feedback on integration with other components. Keep in mind that LDAP interaction is thoroughly untested, and in particular group membership is not implement.d

<!-- gh-comment-id:925029857 --> @nitnelave commented on GitHub (Sep 22, 2021): Thanks for the feedback, but once again, _it doesn't work yet_, the basic features are not complete! I invite you to follow https://github.com/nitnelave/lldap/milestone/1 to see how far we are to basic functionality, though, and I'd love your feedback on integration with other components. Keep in mind that LDAP interaction is _thoroughly untested_, and in particular group membership is not implement.d
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#24
No description provided.