Install went fine, but when I try to go back in to the Lookup Table, I get this error message (I think, it flashes a lot of them very fast … LOL),
Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.
And I can sort of see the error message, it’s trying to go to the machine IP (which is fine), http, and to the api … but seems to fail?
I have set up another Lookup Table (dns), to test it out - it’s fine. And I can access the API from curl or Postman (both http, not https - it’s on my local network). And interestingly enough, if I go on the server machine, and access the Lookup Table (configuration) from localhost … no issues (even going to the LAN IP, not just localhost / 127.0.0.1). But I can’t access it on my local LAN, even though I can get to the API.
not sure but I guess it has nothing todo with the lookup table at all … what have you done exactly? What did you see in the Graylog server.log? What Graylog version are you using?
I created a second Lookup Adapter, the only difference being that it uses GeoIP-ASN data, instead of City. It’s just fine, no issues. I also see that in a pipeline I created, the “troubled” Lookup Adapter works, it’s just “broken” through the web interface. As soon as I try to “Edit” it, or select the title - that’s when the error message shows up.
now you make me curious … can you reproduce what you have done? Can you describe it step by step? It is odd that you run into this strange issue and I just want to check if this can be solved or not.
Yes, you and me both (curious) … LOL. In terms of the steps, I did exactly what is in the (Graylog) link above … heck, I even used the same names. A couple very odd things,
I created two Lookup Tables (and Data Adapters, Caches). They are almost identical - the only difference being that one uses City data (the “troubled” one), the other ASN … and naming is different slightly due to that.
They both seem to work fine, from my Pipeline (and Rule). It’s just the web interface that causes issues. And,
The web interface has issues only when accessed remotely (still on the subnet).
what does “remotely” means for you - is Graylog running on your local computer and it works on that machine but when you access that from your co-workers machine it does not work?
. It’s fine on the server machine (i.e. localhost), but not another machine on the subnet.