LAM not starting

Support
, ,
1

NethServer Version: NS8
**Module:**LAM 1.3.6

Hi,

Just install the LAM module but i cannot acces is.
In the past i had it running and removed it since i didn’t uses it anymore
Now installed is, but nothing happening

This this the log

2026-06-11T15:49:01+02:00 [1:lam2:systemd] Starting agent.service - Rootless module/lam2 agent... 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Starting lam.service - Ldap account manager instance... 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Started agent.service - Rootless module/lam2 agent. 2026-06-11T15:49:01+02:00 [1:lam2:runagent] Updating existing lam-config/lam.conf with LDAP settings. 2026-06-11T15:49:01+02:00 [1:lam2:podman] 2026-06-11 15:49:01.854548678 +0200 CEST m=+0.026720737 container create 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 (image=ghcr.io/ldapaccountmanager/lam:9.5.2, name=lam, PODMAN_SYSTEMD_UNIT=lam.service, maintainer=Roland Gruber <post@rolandgruber.de>) 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Created slice session.slice - User Core Session Slice. 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Starting dbus.service - D-Bus User Message Bus... 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Started dbus.service - D-Bus User Message Bus. 2026-06-11T15:49:01+02:00 [1:lam2:dbus-daemon] [session uid=1016 pid=501159 pidfd=5] Successfully activated service 'org.freedesktop.systemd1' 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Created slice user.slice - Slice /user. 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Started libpod-8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2.scope - libcrun container. 2026-06-11T15:49:01+02:00 [1:lam2:podman] 2026-06-11 15:49:01.905940428 +0200 CEST m=+0.078112491 container init 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 (image=ghcr.io/ldapaccountmanager/lam:9.5.2, name=lam, maintainer=Roland Gruber <post@rolandgruber.de>, PODMAN_SYSTEMD_UNIT=lam.service) 2026-06-11T15:49:01+02:00 [1:lam2:podman] 2026-06-11 15:49:01.90849881 +0200 CEST m=+0.080670865 container start 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 (image=ghcr.io/ldapaccountmanager/lam:9.5.2, name=lam, PODMAN_SYSTEMD_UNIT=lam.service, maintainer=Roland Gruber <post@rolandgruber.de>) 2026-06-11T15:49:01+02:00 [1:lam2:podman] 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 2026-06-11T15:49:01+02:00 [1:lam2:podman] 2026-06-11 15:49:01.844626908 +0200 CEST m=+0.016798988 image pull 582faf5092a3368a7b8714d8a985cccb6f0611f92f37ae3136ffdec187a0a03a ghcr.io/ldapaccountmanager/lam:9.5.2 2026-06-11T15:49:01+02:00 [1:lam2:lam] Starting Apache 2026-06-11T15:49:01+02:00 [1:lam2:systemd] Started podman-pause-359fbeec.scope. 2026-06-11T15:49:01+02:00 [1:lam2:lam] AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.2.100. Set the 'ServerName' directive globally to suppress this message 2026-06-11T15:49:01+02:00 [1:lam2:lam] AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.2.100. Set the 'ServerName' directive globally to suppress this message 2026-06-11T15:49:02+02:00 [1:lam2:lam] [Thu Jun 11 13:49:02.007107 2026] [mpm_prefork:notice] [pid 2:tid 2] AH00163: Apache/2.4.67 (Debian) OpenSSL/3.5.5 configured -- resuming normal operations 2026-06-11T15:49:02+02:00 [1:lam2:lam] [Thu Jun 11 13:49:02.007129 2026] [core:notice] [pid 2:tid 2] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' 2026-06-11T15:49:02+02:00 [1:lam2:podman] 2026-06-11 15:49:02.126670663 +0200 CEST m=+0.026140922 container exec 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 (image=ghcr.io/ldapaccountmanager/lam:9.5.2, name=lam, maintainer=Roland Gruber <post@rolandgruber.de>, PODMAN_SYSTEMD_UNIT=lam.service) 2026-06-11T15:49:02+02:00 [1:lam2:podman] 2026-06-11 15:49:02.187514287 +0200 CEST m=+0.054650031 container exec_died 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 (image=ghcr.io/ldapaccountmanager/lam:9.5.2, name=lam, PODMAN_SYSTEMD_UNIT=lam.service, maintainer=Roland Gruber <post@rolandgruber.de>) 2026-06-11T15:49:02+02:00 [1:lam2:podman] 2026-06-11 15:49:02.189009103 +0200 CEST m=+0.088479354 container exec_died 8f56d17825c14f334b71603d411b83a7583fcafaf33f4983f9b1c21cc210a6b2 (image=ghcr.io/ldapaccountmanager/lam:9.5.2, name=lam, maintainer=Roland Gruber <post@rolandgruber.de>, PODMAN_SYSTEMD_UNIT=lam.service) 2026-06-11T15:49:02+02:00 [1:lam2:runagent] First Configuration done. We push custom configuration files. 2026-06-11T15:49:02+02:00 [1:lam2:runagent] Copying configuration files to the container

2

I can’t reproduce, it’s working here.

Do you get an error when accessing it?

The log looks ok.

3

No. I can’t reach the page

4

Maybe you entered a wrong FQDN when configuring? Is DNS correct?

Bad gateway or 404?

5

Yes.

image
image730×332 4.67 KB

image
image514×256 7.21 KB

6

I can reach it but there’s no valid certificate.

7

I think this is you ?

2026-06-11T16:08:43+02:00 [1:lam2:lam] 10.0.2.100:80 10.0.2.100 - - [11/Jun/2026:14:08:43 +0000] "GET / HTTP/1.1" 302 540 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0" 2026-06-11T16:08:43+02:00 [1:lam2:lam] 10.0.2.100:80 10.0.2.100 - - [11/Jun/2026:14:08:43 +0000] "GET /lam/ HTTP/1.1" 200 530 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0" 2026-06-11T16:08:43+02:00 [1:lam2:lam] 10.0.2.100:80 10.0.2.100 - - [11/Jun/2026:14:08:43 +0000] "GET /favicon.ico HTTP/1.1" 404 482 "https://lam.pdebrabander.nl/lam/" "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0" 2026-06-11T16:08:44+02:00 [1:lam2:lam] 10.0.2.100:80 10.0.2.100 - - [11/Jun/2026:14:08:44 +0000] "GET /lam/style/100_lam.1775050407.min.css HTTP/1.1" 200 15371 "https://lam.pdebrabander.nl/lam/templates/login.php" "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0" 2026-06-11T16:08:44+02:00 [1:lam2:lam] 10.0.2.100:80 10.0.2.100 - - [11/Jun/2026:14:08:44 +0000] "GET /lam/templates/lib/100_lam.1775050407.min.js HTTP/1.1" 200 103219 "https://lam.pdebrabander.nl/lam/templates/login.php" "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0" 2026-06-11T16:08:44+02:00 [1:lam2:lam] 10.0.2.100:80 10.0.2.100 - - [11/Jun/2026:14:08:44 +0000] "GET /lam/pwa_worker.js HTTP/1.1" 200 942 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0"

8

certificate added.

9

Yes, now the cert is valid.
As I can reach it, please check your DNS or port forwarding/reverse proxy.

10

but i’ve you can reach it, then the reverse proxy should be ok
All other reverse proxy are working

11

Is the LAM FQDN resolved correctly in DNS?

12

hmm.. how ?
To my knowledge i’ve no reverse proxies setup differently.
Nothing setup in the DNS (using Nethsecurity)

13

strange thing is
I’m going to HTTPS://lam.pdebrabander.nl and it goes to http://lam.pdebrabander.nl/lam/

14

Please check DNS with nslookup or dig…

nslookup lam.pdebrabander.nl

…and compare it with a working FQDN of another app.

Please also try another browser, it could also be a cache issue.

EDIT:

Please also check the HTTP routes, maybe there’s a wrong route.

15

nslookup lam.pdebrabander.nl
Server: NethSecurity.home
Address: 192.168.1.1

Non-authoritative answer:
Name: lam.pdebrabander.nl
Address: 213.93.150.14

C:\Users\patrick>nslookup sogo.pdebrabander.nl
Server: NethSecurity.home
Address: 192.168.1.1

Non-authoritative answer:
Name: sogo.pdebrabander.nl
Address: 213.93.150.14

C:\Users\patrick>nslookup ns8.pdebrabander.nl
Server: NethSecurity.home
Address: 192.168.1.1

Non-authoritative answer:
Name: ns8.pdebrabander.nl
Address: 213.93.150.14

After adding lam to DNS

C:\Users\patrick>nslookup lam.pdebrabander.nl
Server: NethSecurity.home
Address: 192.168.1.1

Name: lam.pdebrabander.nl
Address: 192.168.1.4

16

nslookup http://lam.pdebrabander.nl
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
Name: http://lam.pdebrabander.nl
Address: 213.93.150.14

17

Sorry, I meant the HTTP routes in the cluster-admin, see HTTP routes — NS8 documentation

Please check if it works in another browser.

18

HTTP route details

Naamlam2

URLhttp://127.0.0.1:20021

Skip certificaat validatie

Uitgeschakeld

Hostlam.pdebrabander.nl

Verzoek een Let’s Encrypt certificaat

Uitgeschakeld

HTTP naar HTTPS

Ingeschakeld

Beperk de toegang van-

NodeNode 1

Traefik instantietraefik1

19

Done.
Chrome and Edge on PC

also on Iphone.
Local not working.
5G access

20

I get “Forbidden” now when accessing your LAM, did you restrict it in the NethSec reverse proxy?

I think you need to remove the DNS entry in NethSec again when there are no entries for the other apps.