1, Added the template
2. Click on Deployment
3. Have the error
Environment Information
VPS Provider: Onidel
Dokploy: Version: v0.28.8
When does this error occur?
During template deployment
Additional Context
No response
Will you send a PR to fix it?
No
Originally created by @xenstar on GitHub (Apr 8, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/777
### Template Name
Affine Pro
### Relevant Logs of the Error
The template fetches the version from here, but it's not working anymore
ghcr.io/toeverything/affine-graphql:stable-780dd83
<img width="977" height="749" alt="Image" src="https://github.com/user-attachments/assets/bcf2c0fc-5209-484f-8891-daf18ec20dac" />
**Here is the issue after deployment:**
<img width="1099" height="781" alt="Image" src="https://github.com/user-attachments/assets/05d7ddc7-3616-411e-af2d-24284e2ae796" />
### Steps to Reproduce the Error
1, Added the template
2. Click on Deployment
3. Have the error
### Environment Information
```bash
VPS Provider: Onidel
Dokploy: Version: v0.28.8
```
### When does this error occur?
During template deployment
### Additional Context
_No response_
### Will you send a PR to fix it?
No
GiteaMirror
added the bug label 2026-04-16 11:13:47 -05:00
Hi @xenstar! I'm Dosu and I’m helping the templates team.
The Affine Pro template currently pins both the main affinepro service and the migration service to ghcr.io/toeverything/affine-graphql:stable-780dd83[1], and the same version is set in meta.json[2]. That image tag appears to no longer be available upstream, which is what's causing the deployment failure.
To fix this, someone would need to:
Find a valid current tag from the AFFiNE GHCR packages (e.g., a newer stable-* tag).
Update ghcr.io/toeverything/affine-graphql:stable-780dd83 → the new tag in both services in blueprints/affinepro/docker-compose.yml[3].
Update the version field in meta.json to match the new tag [2].
Verify the image exists with docker manifest inspect ghcr.io/toeverything/affine-graphql:<new-tag> and test the deployment before submitting a PR.
As a temporary workaround, you can manually update the image tag in the Dokploy service settings after deploying the template — replace stable-780dd83 with a valid tag from the upstream registry for both the main and migration services.
<!-- gh-comment-id:4205411148 -->
@dosubot[bot] commented on GitHub (Apr 8, 2026):
<!-- Greeting -->
Hi @xenstar! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the templates team.
<!-- Answer -->
The Affine Pro template currently pins both the main `affinepro` service and the `migration` service to `ghcr.io/toeverything/affine-graphql:stable-780dd83` [[1]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/affinepro/docker-compose.yml#L4), and the same version is set in `meta.json` [[2]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/meta.json#L108-L124). That image tag appears to no longer be available upstream, which is what's causing the deployment failure.
To fix this, someone would need to:
1. Find a valid current tag from the [AFFiNE GHCR packages](https://github.com/toeverything/AFFiNE/pkgs/container/affine-graphql) (e.g., a newer `stable-*` tag).
2. Update `ghcr.io/toeverything/affine-graphql:stable-780dd83` → the new tag in both services in `blueprints/affinepro/docker-compose.yml` [[3]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/affinepro/docker-compose.yml).
3. Update the `version` field in `meta.json` to match the new tag [[2]](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/meta.json#L108-L124).
4. Run `npm run process-meta` [[4]](https://app.dosu.dev/6bf07378-6531-485c-acb5-f8edab4b0c01/documents/607ba7f6-a597-4b27-bfae-d763edb9010b).
5. Verify the image exists with `docker manifest inspect ghcr.io/toeverything/affine-graphql:<new-tag>` and test the deployment before submitting a PR.
As a temporary workaround, you can manually update the image tag in the Dokploy service settings after deploying the template — replace `stable-780dd83` with a valid tag from the upstream registry for both the main and migration services.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=brand-link).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-great_response#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-irrelevant_answer#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-incorrect_sources#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-too_verbose#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-hallucination#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-bug_report#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-other#message_id=e86a2b1e-72ed-45da-93c3-c829b6b85015&feedback_type=other)</sup>
[](https://app.dosu.dev/6bf07378-6531-485c-acb5-f8edab4b0c01/ask?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=chat-badge) [](https://cursor.com/link/prompt?text=The%20Affine%20Pro%20template%20currently%20pins%20both%20the%20main%20%60affinepro%60%20service%20and%20the%20%60migration%60%20service%20to%20%60ghcr.io/toeverything/affine-graphql%3Astable-780dd83%60%20%5B%5B1%5D%5D%28https%3A//github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/affinepro/docker-compose.yml%23L4%29%2C%20and%20the%20same%20version%20is%20set%20in%20%60meta.json%60%20%5B%5B2%5D%5D%28https%3A//github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/meta.json%23L108-L124%29.%20That%20image%20tag%20appears%20to%20no%20longer%20be%20available%20upstream%2C%20which%20is%20what%27s%20causing%20the%20deployment%20failure.%0A%0ATo%20fix%20this%2C%20someone%20would%20need%20to%3A%0A%0A1.%20Find%20a%20valid%20current%20tag%20from%20the%20%5BAFFiNE%20GHCR%20packages%5D%28https%3A//github.com/toeverything/AFFiNE/pkgs/container/affine-graphql%29%20%28e.g.%2C%20a%20newer%20%60stable-%2A%60%20tag%29.%0A2.%20Update%20%60ghcr.io/toeverything/affine-graphql%3Astable-780dd83%60%20%E2%86%92%20the%20new%20tag%20in%20both%20services%20in%20%60blueprints/affinepro/docker-compose.yml%60%20%5B%5B3%5D%5D%28https%3A//github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/affinepro/docker-compose.yml%29.%0A3.%20Update%20the%20%60version%60%20field%20in%20%60meta.json%60%20to%20match%20the%20new%20tag%20%5B%5B2%5D%5D%28https%3A//github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/meta.json%23L108-L124%29.%0A4.%20Run%20%60npm%20run%20process-meta%60%20%5B%5B4%5D%5D%28https%3A//app.dosu.dev/6bf07378-6531-485c-acb5-f8edab4b0c01/documents/607ba7f6-a597-4b27-bfae-d763edb9010b%29.%0A5.%20Verify%20the%20image%20exists%20with%20%60docker%20manifest%20inspect%20ghcr.io/toeverything/affine-graphql%3A%3Cnew-tag%3E%60%20and%20test%20the%20deployment%20before%20submitting%20a%20PR.%0A%0AAs%20a%20temporary%20workaround%2C%20you%20can%20manually%20update%20the%20image%20tag%20in%20the%20Dokploy%20service%20settings%20after%20deploying%20the%20template%20%E2%80%94%20replace%20%60stable-780dd83%60%20with%20a%20valid%20tag%20from%20the%20upstream%20registry%20for%20both%20the%20main%20and%20migration%20services.) [](https://go.dosu.dev/discord-bot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=join-discord) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/Dokploy/templates/issues/777)
Yes, the templates need to be updated, and also, Cloudflare R2 is mandatory. I was looking to add the dokploy volume disk. I think if the dokploy team works on it, it can be fixed instantly.
<!-- gh-comment-id:4205513778 -->
@xenstar commented on GitHub (Apr 8, 2026):
Yes, the templates need to be updated, and also, Cloudflare R2 is mandatory. I was looking to add the dokploy volume disk. I think if the dokploy team works on it, it can be fixed instantly.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @xenstar on GitHub (Apr 8, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/777
Template Name
Affine Pro
Relevant Logs of the Error
The template fetches the version from here, but it's not working anymore
ghcr.io/toeverything/affine-graphql:stable-780dd83
Here is the issue after deployment:
Steps to Reproduce the Error
1, Added the template
2. Click on Deployment
3. Have the error
Environment Information
When does this error occur?
During template deployment
Additional Context
No response
Will you send a PR to fix it?
No
@dosubot[bot] commented on GitHub (Apr 8, 2026):
Hi @xenstar! I'm Dosu and I’m helping the templates team.
The Affine Pro template currently pins both the main
affineproservice and themigrationservice toghcr.io/toeverything/affine-graphql:stable-780dd83[1], and the same version is set inmeta.json[2]. That image tag appears to no longer be available upstream, which is what's causing the deployment failure.To fix this, someone would need to:
stable-*tag).ghcr.io/toeverything/affine-graphql:stable-780dd83→ the new tag in both services inblueprints/affinepro/docker-compose.yml[3].versionfield inmeta.jsonto match the new tag [2].npm run process-meta[4].docker manifest inspect ghcr.io/toeverything/affine-graphql:<new-tag>and test the deployment before submitting a PR.As a temporary workaround, you can manually update the image tag in the Dokploy service settings after deploying the template — replace
stable-780dd83with a valid tag from the upstream registry for both the main and migration services.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@xenstar commented on GitHub (Apr 8, 2026):
Yes, the templates need to be updated, and also, Cloudflare R2 is mandatory. I was looking to add the dokploy volume disk. I think if the dokploy team works on it, it can be fixed instantly.