Hyper-V FLR Web UI

Heya,

maybe someone has a tip for me on this.

I setup a test environment to get more familiar with NetWorker and Hyper-V.

Since it's a test environment I'm playing around with the latest versions.

Backup-Server: CentOS 7.6

NetWorker 18.2.0.0 downgraded to 18.1.0.2 - It seems that 18.2 on Linux does NOT bring the Hyper-V FLR Web GUI. The Windows version has it, though. I sent this to my Dell EMC contacts so that they can verify this.
Because of that I downgraded to 18.1.0.2 where the GUI at least appears.

Hyper-V: Windows 2016 with 2 VMs. One VM with Windows 2016, the other with CentOS 7.6

NetWorker & NMM 18.2.0.0

No firewalls. I also disabled the CentOS & Windows Firewalls.

lgtoadpt.rpm has also been installed on the backup server.

Backups are working fine. Restores via NMM (GLR & Image) are also working fine.
But GLR restores do not allow a recovery of single files directly into the target VM. That's where the web-based UI comes into play.

Now according to the NMM Hyper-V documentation this should be quite simple:
Open a browser, go to http://backupserver:10000, login, select what you want and restore.

I'm stuck at the login part. I'm using the administrator account which I also use to login to NMC.

When I provide wrong credentials it immediately tells me so.

When I provide correct credentials it says "Logging In" for quite some time.

And then it goes back to the login screen and there's a red exclamation mark at the bottom of the page - but no other information or an error message. Mouse-over or clicking the exclamation mark doesn't bring up anything.

I tested this with various browsers (Edge, Firefox, Internet Explorer) and from various PCs (Open website on backup server itself, My own PC, Hyper-V Host, Hyper-V Guest). Same result everywhere.

The only log I could find on the backup server is the localhost_access_log..2019-01-04.txt in /nsr/authc/logs .
This log is updated whenever I try a login. I can see that it sends HTTP code 201 - which basically should be fine.

No entries in daemon.log or other logfiles I could find.

127.0.0.1 - - [04/Jan/2019:14:06:17 +0100] "POST /auth-server/api/sec/authenticate HTTP/1.1" 201 11532

Using netstat -anv on both the machine where I opened the browser and on the backup server I can see that the connection has been established.

Backup Server (VERBUNDEN means ESTABLISHED - it's German):

[root@xxx logs]# netstat -anv|grep 11000

tcp        0      0 0.0.0.0:11000           0.0.0.0:*               LISTEN 

tcp        0      0 x.x.x.x:11000     x.x.x.x:56673    VERBUNDEN

netstat: no support for `AF INET (sctp)' on this system.

netstat: no support for `AF INET (sctp)' on this system.

netstat: no support for `AF IPX' on this system.

netstat: no support for `AF AX25' on this system.

netstat: no support for `AF X25' on this system.

netstat: no support for `AF NETROM' on this system.

[root@xxx]#

Hyper-V Host:

C:\Users\Administrator>netstat -anv|findstr 11000

  TCP    x.x.x.x:56673   x.x.x.x:11000    ESTABLISHED

Does anyone have an idea what's causing the non-working login? Or where I could find additional logs which may give some more info?

Thanks!