AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 12:56:59 +00:00

[GH-ISSUE #8135] [Bug] Error "Failed to publish: internal" #3585

New issue

Closed

opened 2026-03-23 21:31:34 +00:00 by mirror · 5 comments

mirror commented

2026-03-23 21:31:34 +00:00

Owner

Originally created by @genseirin on GitHub (Jul 24, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8135

Bug Description

Publishing pages used to work in old versions, now a message "Failed to publish: internal" appears on bottom of the page. I tried since 4 days, so it doesn't seem to be a temporary server issue.

The document in question contains only photos, galleries and text.

Saving and syncing across devices is no issue.

How to Reproduce

Create a document with photos, galleries and text.
Click on "Share"
Tab "Publish"
Click "Publish"

Expected Behavior

The page should be published and a link created.

Operating System

macOS 15.5

AppFlowy Version(s)

0.9.5

Screenshots

No response

Additional Context

No response

Originally created by @genseirin on GitHub (Jul 24, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/8135 ### Bug Description Publishing pages used to work in old versions, now a message "Failed to publish: internal" appears on bottom of the page. I tried since 4 days, so it doesn't seem to be a temporary server issue. The document in question contains only photos, galleries and text. Saving and syncing across devices is no issue. ### How to Reproduce 1. Create a document with photos, galleries and text. 2. Click on "Share" 3. Tab "Publish" 4. Click "Publish" ### Expected Behavior The page should be published and a link created. ### Operating System macOS 15.5 ### AppFlowy Version(s) 0.9.5 ### Screenshots _No response_ ### Additional Context _No response_

mirror closed this issue

2026-03-23 21:31:34 +00:00

mirror commented

2026-03-23 21:31:35 +00:00

Author

Owner

@annieappflowy commented on GitHub (Jul 24, 2025):

Hi @genseirin , please email support at appflowy.io with your appflowy account. Once we confirm the flagged published pages, we'll remove the restriction for you. Thank you!

@annieappflowy commented on GitHub (Jul 24, 2025): Hi @genseirin , please email support at appflowy.io with your appflowy account. Once we confirm the flagged published pages, we'll remove the restriction for you. Thank you!

mirror commented

2026-03-23 21:31:35 +00:00

Author

Owner

@genseirin commented on GitHub (Jul 29, 2025):

Maybe it would make sense to improve the criteria for blocking pages. Particularly a page containing not a single link is not of much use for bad guys.

I'm also wondering if your spam filter got triggered by words from a foreign language, since the blocked page is not in English and there is nothing else than photos and text.

@genseirin commented on GitHub (Jul 29, 2025): Maybe it would make sense to improve the criteria for blocking pages. Particularly a page containing not a single link is not of much use for bad guys. I'm also wondering if your spam filter got triggered by words from a foreign language, since the blocked page is not in English and there is nothing else than photos and text.

mirror commented

2026-03-23 21:31:35 +00:00

Author

Owner

@genseirin commented on GitHub (Aug 5, 2025):

Updated to v0.9.6, still the same issue of wrongly flagging the page. I hope that support received my email.

@genseirin commented on GitHub (Aug 5, 2025): Updated to v0.9.6, still the same issue of wrongly flagging the page. I hope that support received my email.

mirror commented

2026-03-23 21:31:35 +00:00

Author

Owner

@Jabuk commented on GitHub (Aug 20, 2025):

I was experiencing this a lot since yesterday using self-hosted instance. I was actively updating some pages, unpublishing and publishing pages again to see the changes (which, by the way, could be improved - it would be nice to be able update changes on published page live, or at least publish new version with one action instead of unpublishing and publishing).

Minor changes (adding some heading, text, or link) would often lead to "Failed to publish: internal". Sometimes reverting changes would allow me to publish again, sometimes it did not, which was frustrating and did not allow me to reliably reproduce the issue and understand which part of the page leads to errors. Sometimes copying content to a new page with a different name would help, but not always.

For now, my workaround is to avoid creating long pages and splitting content into multiple short ones - while it doesn't fix the issue, it seems that less complex pages are more happily accepted by Appflowy, and it's easier to hunt for problematic part of the document using trial-and-error method. Also, when I can't republish only one part of the site goes offline, and not all of it.

App version: 0.9.7

@Jabuk commented on GitHub (Aug 20, 2025): I was experiencing this a lot since yesterday using self-hosted instance. I was actively updating some pages, unpublishing and publishing pages again to see the changes (which, by the way, could be improved - it would be nice to be able update changes on published page live, or at least publish new version with one action instead of unpublishing and publishing). Minor changes (adding some heading, text, or link) would often lead to "Failed to publish: internal". Sometimes reverting changes would allow me to publish again, sometimes it did not, which was frustrating and did not allow me to reliably reproduce the issue and understand which part of the page leads to errors. Sometimes copying content to a new page with a different name would help, but not always. For now, my workaround is to avoid creating long pages and splitting content into multiple short ones - while it doesn't fix the issue, it seems that less complex pages are more happily accepted by Appflowy, and it's easier to hunt for problematic part of the document using trial-and-error method. Also, when I can't republish only one part of the site goes offline, and not all of it. App version: 0.9.7

mirror commented

2026-03-23 21:31:35 +00:00

Author

Owner

@annieappflowy commented on GitHub (Sep 2, 2025):

@genseirin , plz try again and let me know if your issue persists
@Jabuk , it's built in AI content detector on published pages to prevent spam activities. You can reach out me on Discord and share the published pages you don't think that should be flagged as spam.

@annieappflowy commented on GitHub (Sep 2, 2025): @genseirin , plz try again and let me know if your issue persists @Jabuk , it's built in AI content detector on published pages to prevent spam activities. You can reach out me on Discord and share the published pages you don't think that should be flagged as spam.