Dear all,
thanks for hosting me and my small non-profit.
I have been experiencing the following error since today. Enabling Pages via Settings > Pages fails with a message “StaticHost API internal error. Please try again later.” on two repos under the same collective owner: datafora/TriviaEU and datafora/0801c3e4-4276-4189-9e3a-01d16a4077fd (this a throwaway with a never-used slug). Both are public, SHA-1, default branch main, index.html at the root of pages. Neither site exists. Conversely, datafora/bandometro, enabled 2026-09-08, works fine: https://bandometro.datafora.codefloe.page/
How could it be?
Thanks for considering this!
As suggestion, you may add a Pages-creation check to status.codefloe.com .
N.B. possibly not relevant: about this 2026-09-10: Introducing CI/CD quotas CI/CD quota is 0/2500 minutes of all CI time.
Thanks for notifying us!
Yes, there seems to be an issue with SH right now. We’ll try to notify them. Seems like an issue on their end.
Automatic discovery of this could be better, agreed, but we can’t issue a POST request to their API every few seconds or minutes. Hence, such issues are not so easy to catch. But we definitely need better monitoring here, fully agreed!
Your account hasn’t run any CICD yet, so the total seems correct?
I pointed to the CI/CD in case there was an explicit or implicit limit. So no limit on the number of projects with pages for a single organisation, right?
About the status: an API every hour or even day may be beneficial tho. I understand it is neither urgent not important at the moment. 
Nope. Let us know upfront in case you wanna create so many sites that this would challenge the integration 
SH unfortunately (still) has no public API and we are running somewhat in the dark here. We hoped for quite some time that this would have improved by now.
It might also be possible to provide the whole Pages service ourselves for a not so high cost (still fully free for users) on our own servers - yet ideally we wouldn’t need to do everything ourselves but could partner with others for such use cases.
It looks like pushing updates to pages is also broken. When I go to Deploymenttak, I see only Nothing has been published for this site yet. instead of a log. So perhaps the warning should be updated?
Yes, due to the Statichost API error, we’ve been working on migrating to a self-hosted git-pages alternative over the weekend. It is already working in our local tests and we will post an update soon that contains all important information around it.
The “log” tab doesn’t exist anymore as nothing is built anywhere anymore. Builds must now happen via the “git-pages” Forgejo Action. Already built sites should be served fine.
We will post an update as soon as possible. We will also write all affected users an email with migration instructions. If you wanna speed this up, you can already act and try reconfiguring your website to the new subpath-based approach.
Sorry for all the inconvenience and website downtime. In the end, we had to find a solution to get everything working again using an approach that we can act on ourselves instead of waiting on others. The solution is unfortunately breaking for some existing sites, which we would have liked to avoid!
You need to build your site and push the result to a branch, then serve the site from this branch.
@codefloe
The SH issues might be solved now. But looks like there’s an issue that feels like it might have been caused by the SH outage.
If I try to create a page on a project that ran in to issue earlier I see this error:
failed to save Pages settings: unique constraint violation: ERROR: duplicate key value violates unique constraint “UQE_repo_pages_site_label” (SQLSTATE 23505)
Feels like it might be that some portion of the page creation ran while SH was failing and some portion of the database on Codefloe side might have gotten created.
Just a guess.
Yes, that’s a bug on our side. Fixed now! Please try again.
We’re still working on details here, getting pulled away by other tasks and appointments…
Worked!
Thank you for the fantastic support. Keep up the good work