Environment: Debian 12, MongoDB 7, RabbitMQ 4, Datagerry DEV (from git repo 2025-04-07), DG behind Apache 2 (HTTPS) reverse proxy (DG bound to 127.0.0.1:4000)
##########################
NOTE: I had to redact the reported error lines as Jira does not allow to have more than 2 weblinks in a bug report
##########################
Using the current DEV version I’m not able to login via admin/admin with the current Firefox 137.0.
In contrast logging in with Chromium works!
Note: This error seems to be in the Dev version since several days but I did not report this until now.
- In FF (private mode) in the DEV console I got the following during opening DG start page:
A) FF 137
- NO USER → REDIRECT TO LOGIN
ERROR DOMException: XMLHttpRequest.open: ‘(http://):4000/rest/’ is not a valid URL.
in: main.e0060d0ade8c9523.js:1:1258780
- Trying to login with admin/admin gives (FF debugger set to halt on all exceptions)
6935/</ee</< - polyfills.cd68ac3d2ecce35f.js:1:33577
SyntaxError: XMLHttpRequest.open: ‘(http://):4000/rest/auth/login’ is not a valid URL.
Seems to me that this is some kind of redirect error to the reverse proxy?
B) Chromium 134.0.6998.165
No JS error, login successful!
C) Konqueror
Error no login possible:
main.e0060d0ade8c9523.js:1 ERROR DOMException: Failed to execute ‘open’ on ‘XMLHttpRequest’: Invalid URL
at (https://)cmdb12.brain.zz/polyfills.cd68ac3d2ecce35f.js:1:33578
at XMLHttpRequest.Ee.n. [as open] ((https://)cmdb12.brain.zz/polyfills.cd68ac3d2ecce35f.js:1:3876)
at P._subscribe ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:3249102)
at P._trySubscribe ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2187509)
at (https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2187451
at t ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2216907)
at P.subscribe ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2187358)
at D.subscribe.X ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2208662)
at t._next ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2202596)
at t.next ((https://)cmdb12.brain.zz/main.e0060d0ade8c9523.js:1:2191762)
D) Chrome
Error no login possible:
same error as above for Konqueror
Hi,
Thanks for the detailed report.
Could you please try clearing your browser cache and cookies?
Sometimes cached data or old cookies can cause issues with login and API calls.
Let me know if it helps or if the issue still persists.
Best regards,
Abdullah
Hi,
- With git repo from today (2025-04-09) still no login with FF, Chrome,
Konqueror
- tested with completely new blank profile
Chromium still works
- Could it be that this was influenced by me using an Apache2 Reverse Proxy?
Using the settings from the DG documentation:
As I see the following in the DG console:
[2025-04-09 06:52:52][ERROR ] — [redirect_index] 404 Error: 404 Not Found:
The requested URL was not found on the server. If you entered the URL manually
please check your spelling and try again. (app_routes.py)
Here login with Konqueror WORKS, but not with Chromium/Chrome/FF
-
=> In summary I guess its time for me to setup a testbed for automatically
testing the DG dev versions in MY environment so that you will get further
information for zeroing in on this problem. May take me some time, though.
-
BTW: While building the DEV versions I regularly get npm warnings in the CLI
about security issues - 10 of them are “high” severity.
But I do not see them in the compile log (in target/temp/datagerry) - where is
the complete compile log (that is shown at the console) stored?
I know I could get me this one with “tee”, but I wonder if you might already
have the CLI log stored somewhere 
cu
Holger
Hi,
Thanks for the detailed report. I’ve added the issue to our backlog and will investigate it further. I’ll keep you updated as soon as I have more information.
Best regards,
Abdullah Khalid
Hi,
In regards to narrowing down the “not possible login” problem it might be
helpful for you to have my approach in writing:
client: Ubuntu 24.04.2 LTS, Chromium 135.0 (snap)
server: Debian 12, Mongo 7.0.17 , Rabbitmq 4.0.7
Further investigation by me in regards to the JS/login problem showed the
following to have a REPRODUCIBLE behaviour (at least for tests with
Chromium) - i.e. to have an environment to reproducibly see the error.
-
If I test against the release version (2.2.0) via calling from CLI (i.e.
NOT via systemctl service) some datagerry processes still remain
→ I HAD to kill them manually - else other DG versions afterwards re-use
THIS remaining process and do NOT show the behaviour of the new version!
→ This information was crucial to reproduce the error with newer versions
-
I had to use a separate Chromium profile and HAD to kill ALL cache/cookie
etc. information (Ctrl-Shift-Del → ALL) in Chromium and restart this session.
-
To see the errors I always use the Dev-Tools (F12) with showing the JS
console
-
As an extra measure I used Refresh (Ctrl-Shift-R/F5) to enforce a refresh
of the browser
-
All of these tests I currently do WITHOUT a proxy i.e. DIRECTLY to
http://myhost:4000
→ to have proxy config problems out of the debugging equation
Hi,
as an addition to my previous comprehensive mail from today the following
observation:
If I
1)
- clear cache + cookies in Chromium
- start WITHOUT proxy the release DG version (2.0.2)
- login
- KEEP being logged in and stop release version and start DEV repo version as
of 2025-04-07
THEN I can use the new dev version
i.e. the mentioned login problems seem to not affected the working of the dev
version except the login dialog.
(BTW: This is consistent with my previous reports as I did not logoff/logon but
switched the dev versions “on the fly” - and therefore I did not experience the
underlying problem because of some kind of caching of the session)
-
BUT:
If I restart the session or logoff and try to logon (with the new dev version
running) than I get the error.
-
In Firefox I see the following error at loading the start page (with the
dev version)
ERROR DOMException: XMLHttpRequest.open: ‘http://:4000/rest/’ is not a valid
URL
For me it looks like there is something fundamentally wrong with setting up
and holding the session and initializing some base URLs - as the host part is
completely missing in the above URL.
Maybe this will help in reproducing and fixing the error.
cu
Thanks again for the detailed inpu. I’ll have a look at it and get back to you.
Best regards,
Abdullah Khalid
Hi,
unfortunately with the repo version of yesterday and today I’m no longer able
to use my “trick” to login with the release version and switch to the dev
version on the fly without logging out 
(the last dev version working with the “trick” is 2025-04-08 morning)
Therefore it is currently not possible for me to report further on the current
dev version as my priority is now on filling our CMDB. As soon as this is done
I will resume checking the current dev version with real world data.
Or maybe you have a workaround for me to try? - clearing the cache completely
and even using a separate profile and DG without proxy did not help at least
until now.
Please inform me when the login problem is fixed.
Thank you very much
Holger