Hi everyone,
I’m currently working on a fresh Segura/Senhasegura PAM Core v3.33.2 deployment and have encountered several issues during the initial configuration. I would appreciate any guidance from the community or anyone who has experienced something similar.
Environment
- PAM Version: v3.33.2
- Deployment: Proxmox VE
- Type: Standalone / Primary
- AD Domain:
cybrixaz.local - Domain Controller:
CybrixAZ-DC01 - DC IP:
192.168.18.91
Issue 1 – Domain Device Creation
I attempted to add our Active Directory Domain Controller:
- Device Type: Domain
- Vendor: Microsoft
- Device:
CybrixAZ-DC01 - IP:
192.168.18.91 - Domain:
cybrixaz.local
The operation did not complete successfully and returned an HTTP 500/505 server-side error.
However, after the failed operation, the device was still visible in the device-selection field under Credentials → Add Credential.
Issue 2 – Credential Creation / Keyring Error
I then attempted to create a domain credential for the AD bind account:
- Username:
pambind - Password Type: Domain user
- Device:
CybrixAZ-DC01 - Domain:
cybrixaz.local - Automatic Password Change: No
The credential creation failed with:
System Error – Something went wrong! Please try again later.
Error processing keyring info. Code []
Issue 3 – Master Key
PAM is also reporting:
Master Key not set. It is not possible to create a backup of your credentials.
When I go to Settings → Master Key → Set Master Key and attempt to generate a new key, I receive the same:
Error processing keyring info. Code []
Other Orbit Server Manager Incidents
The fresh deployment is also reporting several other incidents:
- Master Key not set
- Elasticsearch Error:
Decryption proccess error: error:03000082: digital envelope routines::invalid key length - Proxy Web: activating / auto-restart / exit-code
- RDP Proxy: inactive (dead)
- SSH Proxy: inactive (dead)
- NATS: connection refused
- Disk: 250 GB allocated, while Orbit reports 500 GB as the minimum recommended capacity
The majority of these incidents started around the initial deployment on 09/08/2026.
Troubleshooting
I checked the available Orbit commands:
orbit key shows only:
keygenagent
Attempting:
orbit key sync
returns:
orbit: error: unexpected argument sync
sudo orbit sync status reports:
Application: Active
Replication: Inactive
Instance: Primary
Maintenance: No
MultiTenant: No
Main: Yes
I also checked for ssenv, but it is not available.
I attempted orbit application init, but it did not resolve the issue.
At this point, I have stopped making further changes to the keyring/cryptographic configuration because I don’t want to regenerate or modify encryption-related components without following the supported procedure.
Questions
Has anyone encountered Error processing keyring info. Code [] on a fresh PAM Core v3.33.2 deployment?
In particular:
- Could the Elasticsearch
invalid key lengtherror be related to the Master Key/keyring issue? - Is there a required initialization procedure for the Master Key on a fresh standalone/primary deployment?
- Could the Proxy Web, RDP Proxy, SSH Proxy, and NATS incidents be symptoms of the same underlying issue?
- Could the HTTP 500/505 error when adding the Domain Controller be related to the keyring/cryptographic problem?
- Is the 250 GB disk allocation likely to contribute to these issues?
- Are there any recommended diagnostics or logs I should collect before proceeding?
I would especially appreciate guidance from anyone who has deployed PAM Core v3.33.2 on Proxmox and encountered similar keyring or Master Key issues.
Thanks in advance!