 |
bareos-error.PNG (23,787 bytes) |
|
|
Additional information: Created a second admin account. Can temporary work around issue switching accounts in the webui when error is encountered. |
|
|
same problem here, 18.2.5 updated from 17.2.4, system ubuntu 16.04 lts |
|
|
I originally posted this in another bug report, but I believe it applies better here: The observation I have found, regarding this issue, is that intentionally logging out (before doing anything that triggers a session expiry response/notification) avoids triggering this bug on subsequent login. Typically, if you remain logged in and your session expires by the time you try to perform an action, you have to log back in. This is when you encounter this bug. Following a long idle period, if you avoid performing any action, so as to avoid being notified that your session has expired, and instead click your username and properly logout from the drop-down, you can log back in successfully without triggering this bug. In fact, I have found that if I always deliberately logout, such that I avoid triggering the session expiry notice, I can always successfully login on the next attempt. I have not yet tested a scenario of closing all browser windows, without logging out, then trying to login again. However, so far it seems that deliberately logging out -- even after session expiry (but without doing anything to trigger a session expiry notification) -- avoids triggering this bug. Hope that helps with figuring out where the bug resides. |
|
|
Can you please check whether deleting your cookies for the bareos-webui actually helps? |
|
|
closing due to no response on feedback request |
|
|
Hello, I'm facing the exact same issue, and I can confirm that cleaning the cookies is not helping. I tried using multiple console, admin, user1, user2 .. the "admin" (using the webui-admin) worked well, but when I started switching to a different account the problem appeared. I thought it was because of the ACL (as the error would eventually say) but even with similar profile the bug would still appear and trying to log back to admin also fails. bareos-webui-18.2.6-58.1.el7.noarch redhat 7.7 Thank you |
|
|
So the webui-admin worked, but the others don't? Do you have "TLS Enable = no" in the other configurations? If not this might be the cause (and we will need a better way to detect and report that problem). |
|
|
Just a "me too". Ubuntu 18.04 Firefox with Adblocker Ultimate installed and pi-hole. bareos 19.2.6-2 bareos-dir Version: 19.2.6 (11 February 2020) Linux-3.10.0-1062.9.1.el7.x86_64 ubuntu Ubuntu 18.04 LTS xUbuntu_18.04 x86_6 bareos-webui directors.ini (comment lines removed for brevity): [localhost-dir] enabled = "yes" diraddress = "sophie" dirport = 9101 tls_verify_peer = false server_can_do_tls = false server_requires_tls = false client_can_do_tls = false client_requires_tls = false [another-host-dir] enabled = "no" diraddress = "192.168.120.1" dirport = 9101 I haven't been in the web-ui for a couple of weeks. I haven't cleared out Firefox in months. I just tried going into the web-ui and experienced this same error as the OP posted including in the httpd logs. After reading this bug tracker, I cleared out only my local cookies and tried going into the web-ui again and it works, although the values for # of jobs running, waiting, successful, warn and failed all have a spinner and no values. If I tab over to Jobs then back to dashboard, they correctly display values. I haven't tried creating multiple users. Happy to help provide further info and try additional steps. |
|
|
Any insight into getting this fixed or working properly? Clearing the cookies only works for me some of the time and the WebUI is not working for me. I'm using Firefox under Devuan (Debian Sid) and Bareos is running on Devuan Beowulf (Debian 10). About the only thing that has worked reliable for me recently is to access the webui using a Chrome Incognito session then closing it when I'm done. |
|
|
This should be fixed in the latest maintanance releases 18.2.10, 19.2.9 and in 20.0.0, too. If it is still broken in these (or later) releases, please reopen. Thank you! |
- Anonymous
