https://linen.dev logo
Join Slack
Powered by
Hello Infisical Team i just update my instance to ...
# general
c
Hello Infisical Team i just update my instance to v0.160.0 and now i have an issue i had two cert manager project and now i lost one of them i set the first one as active , but how i can access to the second one ?
s
Hey @Christophe Jauffret, sorry for the disruption here. With v0.160.0 we moved Certificate Manager to a single active instance per org, which is why your second project isn't showing up. We're working on two things: a fix that lets you access your existing projects again, and a migration tool to duplicate your CAs and certificates into the active instance. Profiles and policies will need to be recreated manually. We have a migration guide here that we're currently updating to reflect the full story: https://infisical.com/docs/documentation/platform/pki/migration We'll update you as soon as everything is ready.
c
is it possible to downgrade back to the previous version for now or il will break something
Okay, I was reading the documentation and, since I don't have a snapshot of my database, it seems that it's not an option.
s
This should be addressed in the latest release. Can you please upgrade to v0.160.2 @Christophe Jauffret
c
on my way, you are developing so fast 😄
s
Hey @Christophe Jauffret, while you are upgrading, just a heads up that we have also updated our migration documentation to reflect the full story, so it should have everything you need: https://infisical.com/docs/documentation/platform/pki/migration If you have any specific questions about the migration process, feel free to drop them right here and I will help walk you through it
c
let me try it
looks like there is some typo in the doc Go to Organization Settings → Products → Certificate Manager is normally Organization Settings → Products Settings→ Certificate Manager and Migrate Entities actions seems called Export to active instance and you don't have choice of the target project But despite that it seems to be working correctly
ok wait is it expected that my existing cert are not migrated ?
s
Thank you for flagging this. We prioritized getting this out quickly to unblock everyone's workflows, so we are already in the process of cleaning things up across the documentation and the UI and will be rolling that out shortly. Regarding your question on existing certificates not being migrated, that is actually expected for now. The idea behind the new setup is that it is designed for new workflows going forward, so once you have migrated your existing processes over to the new active project, everything should continue from there. Could you help me understand why you would need your existing certificates migrated as well?
c
mainly for visibility about what was already distributed
i also miss my external CA and their corresponding app connections
s
For visibility on your existing certificates, your previous projects are not going away, so you will still be able to access them there. For your external CA and app connections, those will need to be recreated manually in the new active project. There is no rush on this though, so you can plan that out at your own pace. In the meantime, everything in your existing projects will continue to work as normal. The idea is to gradually move your workflows over to the new default project and use applications for issuing certificates going forward. Does that help?
c
that's clear, will clean everything and will give you additional feedback later if i have 😄
@Sheen Santos Capadngan i have a weird error i create a new profile using an migrated policy add this profile to an app, enable ACME enrolment for this profile in the app settings and when i make an ACME request on the URL i get the following infisical error
Copy code
{
  "level": 50,
  "time": 1779287824646,
  "pid": 1,
  "hostname": "infisical-infisical-standalone-infisical-c575986fc-64td4",
  "reqId": "req-OTVG3DVd0Dc4Ao",
  "severity": "ERROR",
  "err": {
    "type": "NotFoundError",
    "message": "Certificate profile is not configured for ACME enrollment",
    "stack": "NotFound: Certificate profile is not configured for ACME enrollment\n    at validateAcmeProfile (/backend/src/ee/services/pki-acme/pki-acme-service.ts:197:13)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async Object.respondToAcmeChallenge (/backend/src/ee/services/pki-acme/pki-acme-service.ts:1551:21)\n    at async Object.handler (/backend/src/ee/routes/v1/pki-acme-router.ts:472:9)",
    "name": "NotFound"
  },
  "msg": "Certificate profile is not configured for ACME enrollment"
}
👀 1
looks like only my pre 0.160.0 profile are working again for ACME
s
we're checking this out now
Open in Slack
PreviousNext
Powered by