Hey there Infisical people! We're having an issue ...
# infisical-help
j
Hey there Infisical people! We're having an issue with a 404 error on our previously working great self-hosted instance. We're seeing it primarily with v.100 of the CLI, and NOT in v.85 and earlier, did something in the setup change?
Copy code
Response Code: 404 Not Found
Message: Route GET:/api/v4/secrets?environment=dev&expandSecretReferences=true&includeImports=true&includePersonalOverrides=true&projectId=e90811e9-4c65-407a-8eef-8df58d25e4ce&recursive=false&secretPath=%2F not found
✅ 1
p
Hi @jeremy477, Thanks for reporting this, we found the cause. Starting with CLI
v0.43.99
, the CLI fetches secrets through a newer endpoint
/api/v4/secrets
) that was added in server
v0.150.0
. Your self-hosted instance is on an older version that doesn't have that endpoint yet, so the CLI gets a 404. Upgrading your server to
v0.150.0
or later will fix it! If upgrading isn't practical right now, pinning the CLI to v0.43.85 will get you unblocked in the meantime since that version still uses the v3 endpoints. Happy to help if anything comes up during the upgrade.
j
appreciate that! We're now on 0.146.0, realize this is older, are there any major migrations to be aware of in going from 0.146 to latest
I see the upgrade tool but it doesn't go back that far, we're clearly way behind
p
You should be all good to upgrade!
j
so I've upgraded, and the logs indicate everything is successful, but the browser just presents a blank screen
d
Hi @jeremy477, can you please open the developer console and share any output you see?
Note that you may need to open the developer console, and then refresh the page to see any meaningful output
j
image.png
this is what we see
d
Thank you @jeremy477, let me check with the team!
j
is this worth me rolling back? am I going to corrupt a DB?
d
I would highly discourage rolling back, as this can cause migration issues without a pre-existing backup. Your secrets will remain available and all your workflows will continue working. The issue you're facing is isolated to the UI itself!
j
got it. Yeah the service API surface is all working fine, confirmed that just now
looks like this is the same error github.com/Infisical/infisical/issues/5675
the fix in that comment does work to unblock us, but there's definitely an issue with the self-hosted version and that call
I just saw a fix roll in, that's great! Thanks for the immediate help here!
d
Hi @jeremy477, thank you for keeping an eye on it proactively! We've just rolled out a patch in version
v0.161.11
, please let me know if this helps solve your issue! 🙌
🙏 1
j
solid, I'll definitely be sure to drop the patch on our deployment when we roll there. Thanks for the heads up and quick action, we are huge fans of the product, you guys are moving quick