# "Image not found on registry" error when upgrading from CE to BE or self-updating on Synology NAS

{% hint style="info" %}
**Affected versions:** 2.17.0 and above
{% endhint %}

#### Issue Description

When running an in-app upgrade within Portainer that is running on a Synology NAS, users may receive an error "Image not found on registry".

#### Cause

Our team is currently investigating the cause of this issue, but we suspect this is a consequence of Synology's custom Docker build.

#### Workaround

The workaround for this is to follow the legacy upgrade steps found in the [Portainer documentation](/2.33-lts/start/upgrade.md) and follow the manual steps option for your environment. This will guide you through the steps to update your Portainer install.

Some users have also reported success with [manually pulling](/2.33-lts/user/docker/images/pull.md) the missing image first, then attempting the in-app upgrade.

You can find more details on this issue in the [GitHub Issue](https://github.com/portainer/portainer/issues/8590).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.portainer.io/2.33-lts/faqs/known-issues/image-not-found-on-registry-error-when-upgrading-from-ce-to-be-or-self-updating-on-synology-nas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.