-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebAdmin is empty in ejabberd 24.06 #4249
Labels
Milestone
Comments
prefiks
referenced
this issue
Jul 9, 2024
badlop
added a commit
that referenced
this issue
Jul 12, 2024
badlop
changed the title
WebAdmin is empty since ejabberd 24.06
WebAdmin is empty in ejabberd 24.06
Jul 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
I was using ejabberd's WebAdmin perfectly with ejabberd 24.02. Now I've updated to ejabberd 24.06 and
This is how the WebAdmin looks right now:
And the
ejabberd.log
file shows:What's the problem? How to solve it?
Explanation of WebAdmin in 24.06
Until ejabberd 24.02, when you login to webadmin successfully, you immediately had access to all the pages and content.
In ejabberd 24.06, the WebAdmin uses commands API to generate the page content. Let's view the process in detail:
1. Accessing URL
ejabberd.yml
contains something like this:And you can open a web browser with any of those URLs:
Let's assume that
example.org
directs to the IP address10.20.30.40
.2. The browser immediately requests the login credentials. If you configure like this:
Then you can login with
[email protected]
[email protected]
[email protected]
tim
or[email protected]
3. The WebAdmin site shows the logo, navigation menu and welcome page.
The WebAdmin also shows pages content depending on the permissions that the user has to execute API commands.
For example, this configuration gives access ONLY from
127.0.0.1
and::1
to user[email protected]
:api_permissions
configuration !!Solution to bug in 3.A/B/C
There is a bug in ejabberd 24.06 that appears when you visit an WebAdmin URL but login with an account in another vhost. A fix is already available in git (54f5db8).
You can update ejabberd from git and recompile, or wait for a newer ejabberd release, or:
If you want to login with account
[email protected]
, then please open the URL http://example.org:5280/admin/ , not localhost or 127.0.0.1 or anything else. That is, make sure the host in the URL matches the host in your login account.Solution to configuration problem in 3.E
The default
api_permissions
only allows to execute commands from localhost to admin accounts.Let's add a new permission in
api_permissions
to allow executing commands from ejabberd_web_admin to admin accounts from any machine:The text was updated successfully, but these errors were encountered: