Note
This is the first module release of software currently in beta, and official Docker images are not yet available. For now, it should be used only for testing or quick evaluation of Pegaprox. It looks very nice and promising, with integration of proxLB and proxsnap tools.
More importantly, I had made a mistake in the first release of the module and the configuration data was not being preserved. I’ve now updated it to 0.6.3, and persistence should be working correctly as well. Sorry about that.
Reset of the default user pegaprox is not possible. The new password has not been saved. There is no error message.
new users in settinges --> unser management --> add user cannot be created.
Adding a cluster ist also not possible, because the root credentials are nor acepted. The error messsage is Unauthorized.
I used the exisiting root user.
Thank you, Markus
I did exactly what you showed me in three new installations. It’s not that complicated or unusual. It never worked.
It is now functioning after I restarted the NS8 server.
I also tried to reproduce it, but I didn’t encounter any issues on a fresh installation without any additional modules installed. Do you have some other modules installed?
I’ll try to run some more tests this afternoon.
update module to 0.0.6, should be available on the repository.
Quick note: looks like LDAP support has been added. For now I’ve left it as-is, so if needed it has to be configured manually from Pegaprox. I’ll try to look into integrating it directly with NS8 when I get some time.
@capote sorry, didn’t have time this weekend — I’ll try to replicate the setup using your modules.
The AD/LDAP integration test results in an error that I cannot interpret.
Apparently, the ‘DN’ attribute cannot be found.
✗ invalid attribute type dn
✓ Server connection XYZ.dargels.de:636
✓ Service account bind CN=ldapservice,CN=Users,DC=XYZ,DC=XYZ,DC=dargels,DC=de
✗ Connection invalid attribute type dn
The change to the classic LDAP syntax for “Bind DN” instead of ldapservice@XYZ.XYZ.dargels.de has no effect.
How could I proceed now?
P.s:
The role mapping with DN for users, administrators and viewers has no effect on the error message.
@capote I tried to replicate the password change issue as well. Not sure if it was your case, but I found that it doesn’t work if you access Pegaprox over HTTP instead of HTTPS. Basically, the http2https option in the module configuration should always be enabled — and it will be by default for new installations.
I also noticed that the VM console connection from Pegaprox isn’t working. I ran a few tests and the connection is established on ports 444/445. I adjusted the module configuration, but those ports would also need to be opened on the NS8 firewall. I’m not entirely sure yet what the best way to handle this setting is.
<7>dump_env() is deprecated and implemented as a no-op
Job for pegaprox.service failed because the control process exited with error code.
See "systemctl --user status pegaprox.service" and "journalctl --user -xeu pegaprox.service" for details.
026-03-02T09:14:34+01:00 [1:pegaprox3:systemd] pegaprox.service: Scheduled restart job, restart counter is at 4.
2026-03-02T09:14:34+01:00 [1:pegaprox3:systemd] Stopped pegaprox.service - Podman pegaprox.service.
2026-03-02T09:14:34+01:00 [1:pegaprox3:systemd] Starting pegaprox.service - Podman pegaprox.service...
2026-03-02T09:14:34+01:00 [1:pegaprox3:systemd] Created slice user-libpod_pod_8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09.slice - cgroup user-libpod_pod_8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09.slice.
2026-03-02T09:14:34+01:00 [1:pegaprox3:podman]
2026-03-02T09:14:34+01:00 [1:pegaprox3:podman] 2026-03-02 09:14:34.331136319 +0100 CET m=+0.100711361 container create e7bd77863e61a95a05af01b791d14dd136d30d9cf063341fd34a2ad06f557d71 (image=localhost/podman-pause:4.3.1-0, name=8f335b2e3135-infra, pod_id=8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09, io.buildah.version=1.28.2, PODMAN_SYSTEMD_UNIT=pegaprox.service)
2026-03-02T09:14:34+01:00 [1:pegaprox3:podman] 2026-03-02 09:14:34.338667351 +0100 CET m=+0.108242395 pod create 8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09 (image=, name=pegaprox)
2026-03-02T09:14:34+01:00 [1:pegaprox3:podman] 8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09
2026-03-02T09:14:37+01:00 [1:pegaprox3:podman] Error: starting container e7bd77863e61a95a05af01b791d14dd136d30d9cf063341fd34a2ad06f557d71: rootlessport listen tcp 0.0.0.0:445: bind: address already in use
2026-03-02T09:14:37+01:00 [1:pegaprox3:systemd] pegaprox.service: Control process exited, code=exited, status=125/n/a
2026-03-02T09:14:37+01:00 [1:pegaprox3:podman] 2026-03-02 09:14:37.647266228 +0100 CET m=+0.123648736 container remove e7bd77863e61a95a05af01b791d14dd136d30d9cf063341fd34a2ad06f557d71 (image=localhost/podman-pause:4.3.1-0, name=8f335b2e3135-infra, pod_id=8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09, PODMAN_SYSTEMD_UNIT=pegaprox.service, io.buildah.version=1.28.2)
2026-03-02T09:14:37+01:00 [1:pegaprox3:systemd] Removed slice user-libpod_pod_8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09.slice - cgroup user-libpod_pod_8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09.slice.
2026-03-02T09:14:37+01:00 [1:pegaprox3:podman] 2026-03-02 09:14:37.663939597 +0100 CET m=+0.140322115 pod remove 8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09 (image=, name=pegaprox)
2026-03-02T09:14:37+01:00 [1:pegaprox3:podman] 8f335b2e313578d79e8f5e8c0873e44f3e41d308bf84463ac165b834a2a3ef09
2026-03-02T09:14:37+01:00 [1:pegaprox3:systemd] pegaprox.service: Failed with result 'exit-code'.
2026-03-02T09:14:37+01:00 [1:pegaprox3:systemd] Failed to start pegaprox.service - Podman pegaprox.service.
2026-03-02T09:14:37+01:00 [1:pegaprox3:systemd] Dependency failed for pegaprox-app.service - Podman pegaprox-app.service.
2026-03-02T09:14:37+01:00 [1:pegaprox3:systemd] pegaprox-app.service: Job pegaprox-app.service/start failed with result 'dependency'.
