Closed cfoellmann closed 7 months ago
Can u try the master
docker image?
That's the latest master branch of features/bug fixes,
Also can u verify the showpaths output afterwards?
As I think the above is different from the other post?
Also can you share the folder structure of /opt/meshcentral/meshcentral-web-csystems?
have you tried the latest release 1.1.22 and see if you still have this issue?
I was about to get back to this issue tomorrow. I just updated to 1.1.22 in docker and my second domain (csystems) "broke" with a 404 page. I will see what that is.
@si458 are you open for a paid debug? So you get something back for all your free help for meshcentral users?
@cfoellmann oh dear thats not good! contact me via email and sure i can help!
@si458 I reverted to 1.1.21 and it comes up normal. So there must be a bug in 1.1.22
1.1.22 did have some changes to do with saml if i remember? https://github.com/Ylianst/MeshCentral/releases/tag/1.1.22 you might need to update your saml config, trying to find the commit/issue about it
EDIT: https://github.com/Ylianst/MeshCentral/pull/5856 - https://ylianst.github.io/MeshCentral/meshcentral/#generic-saml-setup
The issue is about openid not SAML and there seems to be no changes. My main domain works and SAML login works.
I have activated normal password login on my second domain and that works. So SAML is "broken" and the assets are still not split between the domains :-(
i cant understand if BOTH domains use saml, and one works but the other doesnt, how can saml be broken? what about this issue? https://github.com/Ylianst/MeshCentral/issues/4725 im just going to try setup an Authentik server and see what i find
EDIT: what page is getting the 404? the login page? the default page? after login? p.s i did also email you i think :)
The SAML action is initiated through /auth-saml
and that one is not working on the second domain -> 404
The issue disappears when switching from DNS to path based for the second domain
ok have fixed the saml issue you was having #6015 ive also verified the customise issue too! its yet again the DNS value causing the issue! remove it and use path format, and works no problems!
We run the "official" docker image with an additional domain. I want to customize (templates, images, styles, etc) differently on both domains (main + 2nd domain).
config.json
Moved from #5496