Test drive v4.0.0-rc1
I am trying to run version 4.0.0-rc1 on a server in my home network. I am using a local domain, and the port is 8080. On this release, the (embedded) console is not displaying at all. I had no error messages in the console during the startup phase.
http://localdomain.com:8080/ui/console -> redirects to
http://localdomain.com:8080/ui/v2/login/login?authRequest=V2_328122283870650372 this url return this JSON
{"code":5,"message":"Not Found"}
I attempted to set up a custom TypeScript login on my development machine, which connected to the backend on the home server. The display I saw was the language dropdown and the theme switch. I examined the browser's console, and an authentication error appeared. The authentication error is understandable because I was using a service user token, which was generated in the old backend (v3.2.2). The issue is that I cannot access the default console on the backend server, and I am unable to deploy a customised TypeScript login because I have not yet created a service user token.
Server Error fetching custom translations: ConnectError: [unauthenticated] Errors.Token.Invalid (AUTH-7fs1e)
http://localdomain.com:8080/ui/console -> redirects to
http://localdomain.com:8080/ui/v2/login/login?authRequest=V2_328122283870650372 this url return this JSON
{"code":5,"message":"Not Found"}
I attempted to set up a custom TypeScript login on my development machine, which connected to the backend on the home server. The display I saw was the language dropdown and the theme switch. I examined the browser's console, and an authentication error appeared. The authentication error is understandable because I was using a service user token, which was generated in the old backend (v3.2.2). The issue is that I cannot access the default console on the backend server, and I am unable to deploy a customised TypeScript login because I have not yet created a service user token.
Server Error fetching custom translations: ConnectError: [unauthenticated] Errors.Token.Invalid (AUTH-7fs1e)
