Hello All. I had a violation about access to http://api.graylog.com:443 2020-06-02T22:04:11.061Z WARN [LicenseChecker] License violation - Failed to report license status to Graylog, Inc. - consecutive failures: 234, limit: 72 2020-06-02T22:04:11.062Z WARN [LicenseChecker] License violation - D…

he @RodrigoNCF Did you restart your Graylog? Did you still have the same error?

Hello Jan. Thanks for your prompt answer. Yes, my friend, already restarted Gralog App, and the server as well. And the error is still there. Do you know if this violation message should disappear is my Graylog start to communicate with api.graylog.com for license check task?

he @RodrigoNCF Do you know if this violation message should disappear is my Graylog start to communicate with api.graylog.com for license check task? yes, once the communication is possible again the status will clear again.

Hello Jan. The Proxy is set ok. We can see that the transaction is allowed, and has return from api.graylog.com . CURL test is OK (by Proxy): “… root@innolog3v0001:~# root@innolog3v0001:~# curl https://api.graylog.com You have reached the Graylog, Inc API. Please contact Graylog support for as…

a new license will not change @RodrigoNCF that your Graylog is not able to communicate with the API. is your proxy tampering the connection?

We have collected the pcap file from the transaction, and analyzed it. It seems that the comunnication is complety and finish with sucess. Is it possible for someone in Graylog side to to check the log? Src: 118.185.21.42 Prx: 165.225.76.89 Dst: 34.192.84.136 Date: 09/jun/2020 [ZScalerProxy_…

he @RodrigoNCF we have a single hit 2020-06-09 18:13:57 +02:00 coming in for report. Something in your Network might tamper the connections, but that is only a guessing.

Hey Jan. Thanks again for your answer. We have removed Proxy from the flow/traffic. Now, the Internal Graylog Srv is communicating direct to https://api.graylog.com . But the Violation error is still there, not fixed. We fixed the IP for api.graylog.com in /etc/host (for FW rule setup), and curl…

Graylog License Check Violation >72

Graylog Central (peer support)

ttsandrew June 19, 2020, 4:21pm 10

I think this is telling. Here is an older post with this same error, and for them it was a time issue.

Topic		Replies	Views
Recursive graylog license violation Graylog Central (peer support)	5	2318	August 10, 2018
License Violation Issues Graylog Central (peer support)	31	8120	March 26, 2018
Yet Another License violation Graylog Central (peer support)	6	913	March 10, 2020
Failed to report license status Graylog Central (peer support)	3	890	July 9, 2018
Get License violation without over traffic limited Graylog Central (peer support)	4	439	March 5, 2021

Graylog License Check Violation >72

Related topics