Admin Login won't work

[nebulon]

That difference is to be expected. Etherpad has two config files, which get merged on runtime, however the admin settings only show one of them. You should be able to change the settings via the filemanager from Cloudron though. Generally the admin UI is not too useful as it currently is

[David 0]

Both config files contain "defaultPadText" – and the one from the file manager seems to be 'active'. Does the last edited config file override the older version if they contain the same values?

Could it be beneficial to clear one of those files and work only with the other?

There are plenty of entries in the one in the admin panel that I do not have in the one in my file manager...

[nebulon]

The one from /app/data/ should overwrite the values from the other. But likely the config file structure in the package will change I assume. We have to see how upstream development improves the admin UI and if we maybe shouldn't even have that. Mostly a .json file textarea with a save button is not really much added value.

[sparkwise]

I think access to the admin UI will still be needed in order to access Etherpad's Plugin Manager. (I don't believe there's a way to specify or update plugins from the json file.)

[David 0]

...story continues:

As with the latest update (from etherpad 4.1.0 to 4.1.1.), I can't login via '/admin-auth' as mentioned earlier. Instead, I get this error:

RPError: outgoing request timed out after 3500ms
    at /run/etherpad-lite/src/plugin_packages/.versions/openid-client@5.7.0/lib/helpers/request.js:140:13
    at async Client.grant (/run/etherpad-lite/src/plugin_packages/.versions/openid-client@5.7.0/lib/client.js:1370:22)
    at async Client.callback (/run/etherpad-lite/src/plugin_packages/.versions/openid-client@5.7.0/lib/client.js:520:24)
    at async /run/etherpad-lite/src/plugin_packages/.versions/ep_openid_connect@3.0.7/index.js:144:11

The pad itself runs as usual.

[nebulon]

We also had to disable the webrtc plugin as it throws errors and @vladimir-d reported another issue at ep_comments_page which got fixed https://github.com/ether/ep_comments_page/issues/339

Overall etherpad seems to be in a rough situation right now, but the pace of development is positive.

[marylou]

Hello everyone,

I am logged in through Cloudron (my name shows up), but I cannot access the admin panel under /admin. I get forwarded to /admin/login. Neither "admin" / "changeme1" nor the Cloudron credentials worked.

It is such a nice app, it's sad it does not seem to work reliably.

[nebulon]

Looks like our docs are outdated. So what needs to happen is, set the username in settings.json as the Cloudron username who should be admin and then restart the app and then /admin should work for that user.

Will update the docs now

[marylou]

Does not work unfortunately. After changing "admin" to "username", I was no longer able to log in at all.

[nebulon]

Actually the docs at https://docs.cloudron.io/apps/etherpad/#admin-user are already correct.

@marylou did you restart the app after changing the file? Have you done any other modification to the settings? Etherpad can be very picky about those changes.

[marylou]

Restarted several times, no other modifications. But I will try again. I have already deinstalled it because there were other issues (editing rights for users) as well.

[sparkwise]

@marylou @nebulon Currently, accessing Etherpad's admin interface is a two-step process (after the config mentioned above):

1. First, visit /admin-auth/ to authenticate with your Cloudron user. If successful, you'll see the word "Authorized" appear.
2. Next, visit /admin. This should no longer redirect you to /admin/login, and should instead show you the Etherpad admin console.