Evolution skin broken

Joined
May 13, 2024
Messages
3
Hello all,

I am not an DirectAdmin expert. So please be gentle. :)

Since a couple of weeks/months now an update of DirectAdmin broke the Evolution skin after login. And I am getting lost.
We get the following error after login.

Data Error
Could not load session data. Please, contact your administrator.
Code:
nt@https://my.domain.com:2222/evo/index.DhbmIBaM.js:34:456
SF@https://my.domain.com:2222/evo/index.DhbmIBaM.js:103:50835
async*hue@https://my.domain.com:2222/evo/index.DhbmIBaM.js:126:24632
mue@https://my.domain.com:2222/evo/index.DhbmIBaM.js:126:24425
Cue@https://my.domain.com:2222/evo/index.DhbmIBaM.js:126:25732
async*@https://my.domain.com:2222/evo/index.DhbmIBaM.js:126:26040

In the browser console the following error is reported:

Code:
'Validation failed:\n{\n  "customDomainItems": [\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    },\n    {\n      "type": "Expected \\"checkbox\\" | \\"text\\" | \\"listbox\\", but was string"\n    }\n  ]\n}.\nObject should match { allowedCommands: string[]; configFeatures: { auth2FA: boolean; bruteforceLogScanner: boolean; cgroup: boolean; clamav: boolean; composer: boolean; dnssec: number; git: boolean; imapsync: boolean; inode: boolean; ipv6: boolean; jail: number; mxWithoutDNSControl: boolean; netdataSock: boolean; nginx: boolean; nginxProxy: boolean; nginxTemplates: boolean; oneClickPMALogin: boolean; phpmyadmin: boolean; redis: boolean; resellerCustomizeSkinConfigJson: boolean; roundcube: boolean; rspamdSock: boolean; securityQuestions: boolean; squirrelMail: boolean; unit: boolean; webmail: boolean; wordpress: boolean; }; customDomainItems: { checked: boolean; default: string; description: string; hidden: boolean; label: string; name: string; options: { text: string; value: string; }[]; readOnly: boolean; type: "checkbox" | "text" | "listbox"; }[]; custombuildOptions: { modSecurity: boolean; }; demo: boolean; directadminConfig: { allowForwarderPipe: boolean; ftpSeparator: string; homeOverrides: string[]; loginKeys: boolean; maxFilesizeBytes: number; resellerWarningBandwidthPercentage: number; showPointersInList: number; tableDefaultIPP: number; userWarningBandwidthPercentage: number; userWarningInodePercentage: number; userWarningQuotaPercentage: number; webappsSSL: boolean; webmailHideLinks: boolean; webmailLink: string; }; effectiveRole: "user" | "reseller" | "admin"; effectiveUsername: string; havePluginHooksAdmin: boolean; havePluginHooksReseller: boolean; havePluginHooksUser: boolean; homeDir: string; loginAsDNSControl: boolean; phpmyadminPublic: boolean; realUsername: string; selectedDomain: string; sessionID: string; ticketsEnabled: boolean; }'

We are currently running DA version 1.663.
I think this might be a related fixed issue:
https://docs.directadmin.com/change...ain-items-configuration-breaks-evolution-skin

Can someone point me in the right direction?
If I should provide more information please let me know.
 
Anybody here to help me find a solution? Currently the DA management UI is compelely broken and unusable and I can still not find even a hint why this is broken?
 
You might open a ticket with DirectAdmin support and let them investigate it for you, if your license includes their support. In other case, you might completely remove all the skin customization and the skin itself, and re-install Evolution skin the way the user Active8 offered.

- /usr/local/directadmin/data/users/<USER>/skin_customizations/
- /usr/local/directadmin/data/skins/evolution/
 
Back
Top