The repository ' jammy InRelease' is not signed (FIXED)

I’ve got this error when I tried to update Ubuntu jammy (22.04):

Err:5 jammy InRelease
403 Forbidden
Reading package lists… Done
E: Failed to fetch 403 Forbidden
E: The repository ‘ jammy InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Need some help, please

It’s the same as always with Insync.They have never(!) managed to get the repos ready for the release of a new Ubuntu or Fedora version,etc.

The release dates are known, there are daily images…developer…betas…more than enough time to prepare their own product for a new release.

That means you can now wait again until Insync will make it available at some point in the near future…and thus entire workflows will come to a standstill.

The customer does not buy the product without a reason…it is needed for work(!).

And no, any workarounds for insync’s failings for a paid(!) product are not okay at all.
As already mentioned, this is not an exception but the standard behavior.

EDIT: Excuse my english, i am not a native speaker.


Hello, @Trumpet34! Your pain points regarding how we release updated versions are understandable. :slight_smile:

To give some context on how we map out our releases: while I can suggest working on releasing a version while a distro is in beta, we cannot guarantee that it will not crash nor cause any issues as there are still plenty of changes happening during this stage that may affect how Insync runs.

Regardless, I will bring this up with our team to see how we can implement improvements to align with our user’s feedback. For context, we are working on releasing our Ubuntu 22 (Jammy) build in an upcoming release.

Thank you!

Hi @Andre_do_Eirado_Silv, could you try this out for me? Insync not working with Ubuntu Jammy (with workaround)

Hi @mia
I agree with @Trumpet34.
The workaround that you suggest has nothing to do with my problem. This is only the invalid signature of Insync repositories. Wouldn’t there be a way to make it valid?
Best regards

Hi @Andre_do_Eirado_Silv,

The reason why it’s not yet signed is that we haven’t released it. We are working on doing so as soon as possible. We don’t release soon after the beta versions are available due to the following:

  1. There could be future releases for those distros soon after the beta is released that fix those issues themselves. If we do the fixes for these issues, the builds might break again later due to the changes made by the distro which can cause further trouble on our users’ end.
  2. The releases are built using docker images so the images for those beta distros may not be available yet.

I will be updating all the related threads as soon as we have released the build. Thank you for your patience.

Please check out this post for our latest update: