Codeberg/Community
54
325
Fork
You've already forked Community
12

Codeberg pages for personal blog with custom domain leads to SSL_ERROR_INTERNAL_ERROR_ALERT #2021

Closed
opened 2025年07月12日 23:20:02 +02:00 by joelvonrotz · 6 comments

Comment

Hello,
I've been recently trying to migrate my "little" blog (it's rather large despite the rather small amount of content) from Github to Codeberg Pages. I think I've got everything setup, but I have something misconfigured, but don't know where. I receive following when loading up https://joelvonrotz.ch

image

My blog sits at https://codeberg.org/joelvonrotz/pages and has following .domain file under /static/

joelvonrotz.ch
joelvonrotz.codeberg.page
pages.pages.joelvonrotz.codeberg.page

My website uses Zola as a static site generator in combination with the woodpecker CI. The CI builds the page and pushes the result onto the pages branch. The repository uses main as the default branch.

My DNS configuration is as following for my page:

image

I'm not sure where I'm hitting my head and would be happy, if you could help me out. Thank you :)

### Comment Hello, I've been recently trying to migrate my "little" blog (it's rather large despite the rather small amount of content) from Github to Codeberg Pages. I think I've got everything setup, but I have something misconfigured, but don't know where. I receive following when loading up `https://joelvonrotz.ch` ![image](/attachments/a0e92ecd-5f33-4f29-bab6-6a1d085a1599) My blog sits at https://codeberg.org/joelvonrotz/pages and has following `.domain` file under `/static/` ``` joelvonrotz.ch joelvonrotz.codeberg.page pages.pages.joelvonrotz.codeberg.page ``` My website uses [Zola](https://www.getzola.org/) as a static site generator in combination with the woodpecker CI. The CI builds the page and pushes the result onto the `pages` branch. The repository uses `main` as the default branch. My DNS configuration is as following for my page: ![image](/attachments/b9ed759b-da1b-4214-a8c0-959f37dfb65b) I'm not sure where I'm hitting my head and would be happy, if you could help me out. Thank you :)

The problem is that in the build pages branch the domain still resides in the static/ folder, it should instead be in the root of the repo/branch that serves the page.

If you adjust your woodpecker file to move it there instead of putting it into the folder it should work I think :)

The problem is that in the build `pages` branch the domain still resides in the `static/` folder, it should instead be in the root of the repo/branch that serves the page. If you adjust your woodpecker file to move it there instead of putting it into the folder it should work I think :)

Hi, the server had an old DNS entry cached for the TXT record. Your website is accessible again.

Hi, the server had an old DNS entry cached for the TXT record. Your website is accessible again.

@gedankenstuecke wrote in #2021 (comment):

The problem is that in the build pages branch the domain still resides in the static/ folder, it should instead be in the root of the repo/branch that serves the page.

If you adjust your woodpecker file to move it there instead of putting it into the folder it should work I think :)

In the pages branch, you can see the page is on root level :)

But the website works now, had to wait for the DNS entries to update (as Gusted mentioned). Was very tired yesterday to figure this out 😅

@gedankenstuecke wrote in https://codeberg.org/Codeberg/Community/issues/2021#issuecomment-5805032: > The problem is that in the build `pages` branch the domain still resides in the `static/` folder, it should instead be in the root of the repo/branch that serves the page. > > If you adjust your woodpecker file to move it there instead of putting it into the folder it should work I think :) In the `pages` branch, you can see the page is on root level :) But the website works now, had to wait for the DNS entries to update (as Gusted mentioned). Was very tired yesterday to figure this out 😅

@Gusted wrote in #2021 (comment):

Hi, the server had an old DNS entry cached for the TXT record. Your website is accessible again.

Thank you! I wasn't sure if I configured it correctly, but it was the case 😅 Gotta be a Bit more patient next time

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2021#issuecomment-5805074: > Hi, the server had an old DNS entry cached for the TXT record. Your website is accessible again. Thank you! I wasn't sure if I configured it correctly, but it was the case 😅 Gotta be a Bit more patient next time

@joelvonrotz wrote in #2021 (comment):

But the website works now, had to wait for the DNS entries to update (as Gusted mentioned). Was very tired yesterday to figure this out 😅

And I clearly shouldnt try to give advice when tired either 😅

@joelvonrotz wrote in https://codeberg.org/Codeberg/Community/issues/2021#issuecomment-5806772: > But the website works now, had to wait for the DNS entries to update (as Gusted mentioned). Was very tired yesterday to figure this out :sweat_smile: And I clearly shouldnt try to give advice when tired either 😅

@gedankenstuecke wrote in #2021 (comment):

@joelvonrotz wrote in #2021 (Kommentar):

But the website works now, had to wait for the DNS entries to update (as Gusted mentioned). Was very tired yesterday to figure this out 😅

And I clearly shouldnt try to give advice when tired either 😅

No worries. Shit happens and I hope the sleep was at least good! Works now, although gotta read more into how pages are served :)

@gedankenstuecke wrote in https://codeberg.org/Codeberg/Community/issues/2021#issuecomment-5808560: > @joelvonrotz wrote in #2021 (Kommentar): > > > But the website works now, had to wait for the DNS entries to update (as Gusted mentioned). Was very tired yesterday to figure this out :sweat_smile: > > And I clearly shouldnt try to give advice when tired either :sweat_smile: No worries. Shit happens and I hope the sleep was at least good! Works now, although gotta read more into how pages are served :)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2021
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?