Hey there, i tried to enable Pages for one of my projects, but i get an error saying StaticHost API internal error. Please try again later. This has been the case for weeks now.
We just checked this and couldn’t find any issues on our end.
Judging by your repos, we also don’t see any repo currently having pages enabled. If you tried it on your drns.dev repo, did you specify the correct branch? Note that the Pages service expects the website’s public files in the root of the respective branch (your drns.dev repo doesn’t have that).
We can check in more detail if you continue to encounter errors but we’d need more details on what you’ve tried exactly.
Well i get the error when i try to enable it. I click on Enable, then on Save and then it shows me the error. It is the drns.dev repo you mentioned, and the build files are there, in public dir. I now tried adding a statichost.yml, which didn’t work. Also creating a seperate pages branch where the build files are at root level did not work.
The problem is the dot in your repo name which breaks DNS as it creates another subdomain level.
We’ll slugify it so the dot is replaced with dash instead.
statichost.yml doesn’t have an effect and isn’t honored by the backend.
ah ok, that makes sense. i can also just rename the repo.
I was hoping to just use the hugo config for statichost as mentioned here.
Ah, the docs entry is still from a point in time when we thought/hoped it would be honored. Maybe it even works - but the honest answer right now though is that we don’t know either. We also need to ask the statichost people and a reply has been taken multiple days to weeks lately. The statement that the YAML isn’t honored was from a previous conversation with them around our use of their API.
The underlying issue is that SH doesn’t expose it’s API publicly and there are also no docs for the existing endpoints.
We’d suggest you try it out and see if it works or if statichost does even auto-detect this (it does for some languages).
We’ve now deployed the sanitization fix, so you should be able to enable your repo!
The sanitization is working and I added a statichost.yml file with the hugo config, which is also working.
I noticed that i was not able to change the branch after enabling the feature, but that’s fine since the correct branch is selected. I guess one would have to disable the feature, then change branch and enable it again.
Thank you very much for helping in resolving this!