I have two Prisma Cloud Compute instances which have their intelligence streams updated via the twistcli (v31).
31.03.103 - updates with no issues whatsoever.
33.00.169 - stopped accepting updates a few days ago with a 504 gateway error.
As a test, I have tried: Setting 33.00.169 to get updates from 31.03.103 server, but I get the same 504 gateway error that twistcli gives.
Nothing has changed. Why would this suddenly happen? My only thought is perhaps something has changed with the IS payload that would cause this issue?
It's hard to comprehend why v.31 works and v.33 suddenly does not.
These are gov instances, so changing versions is off the table. Connecting directly to Palo Alto IS updates is also off the table. My understanding is it's a broken feature until v.34 anyway.
It attempts the upload, and it seems like the upload completes, or mostly completes, but then throws this error:
Status: 504 Gateway Timeout
PUT https://xxxxxxxxxxxxxxxxx.gov/api/v31.03/feeds/bundle failed.
Error: <html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
</body>
</html>
Failed to upload intelligence stream to Twistlock consoleFWIW, the console shows that the IS was updated.
