topic Re: Problem with Loginsight Content Pack Markplace access in VMware Aria Operations for Logs Discussions

Problem with Loginsight Content Pack Markplace access

fduranti — Fri, 17 Apr 2020 07:32:47 GMT

Starting from some days ago I'm not able to access the Content Pack Marketplace from vRealize Log Insight.

I just get a circle spinning in the middle of the screen just like it was trying to download something but not working.

It was working in the past.

I've the same problem on 3 different installation 2 of which are 8.0 and 1 is 8.1 just upgraded.

From my browser I'm able to reach the marketplace without any problem.

Anything I can check?

Re: Problem with Loginsight Content Pack Markplace access

fcardarelli — Sun, 19 Apr 2020 01:01:15 GMT

Hi, same error here on a new installation.

Any info will be appreciated.

Re: Problem with Loginsight Content Pack Markplace access

fduranti — Mon, 20 Apr 2020 07:54:05 GMT

I've got an answer from the support.

It work connecting with the ip address of the log insight server.

After it worked a first time with ip address it work also with fqdn.

It solved my issue.

Re: Problem with Loginsight Content Pack Markplace access

BenediktFrenzel — Mon, 20 Apr 2020 07:55:04 GMT

Hi,

sorry for the inconvenience, our Log Insight team is currently working on this issue.

The current workaround would be to connect to the Log Insight using the IP first.

This will assure that the Content will load, and after that you should be able to use the FQDN again.

Hope that helps. Best Regards from Cork

Benedikt

Re: Problem with Loginsight Content Pack Markplace access

ralish — Fri, 24 Apr 2020 01:17:26 GMT

Just wanted to add a bit more detail here, which hopefully can be relayed to the relevant engineers if they're not already aware.

The underlying issue is a cross-site request to the GitHub API to retrieve details for the vmw-loginsight/vlcp repository. The request fails with a HTTP 401 (Unauthorized) response. Why that is I'm not sure; it appears to be some odd CORS handling on GitHub's end. As Benedikt notes, it works if the Origin request header is an IP address instead of a hostname, and if you send the request using curl but strip the scheme from the origin (e.g. "Origin: my.vrli.site") it also works.