Secure Connection Failed on static page with repo specified. #2225

RockyMountSDAVA commented 2025年11月20日 12:48:27 +01:00

Comment

I making a website with codebergs static pages and trying to make a page that is in a repo not named pages as I plan to host a couple static sites.

When I navigate to reponame.username.codeberg.page I get an SSL_ERROR_INTERNAL_ERROR_ALERT. I don't get this if I navigate tousername.codeberg.page/reponame. The page loads without issue.

For the moment I'm able to workaround this by copying my repo to a pages repo. The page loads without issue at username.codeberg.page, but still gets the SSL error at pages.username.codeberg.page. Eventually I'll need a repo with a different name in order to host a second static site.

Some notes:

• The repo has capital letters in it, but no periods or other special characters. Though I doubt this is the issue as use pages as the repo name also results in the same error.
• I will be using a custom domain name. For now it is point to username.codeberg.page so I'm uncertain if pointing to reponame.username.codeberg.page will work given the error.
• I'm hosting out of the main branch without a specific pages branch.

### Comment I making a website with codebergs static pages and trying to make a page that is in a repo not named `pages` as I plan to host a couple static sites. When I navigate to `reponame.username.codeberg.page` I get an `SSL_ERROR_INTERNAL_ERROR_ALERT`. I don't get this if I navigate to`username.codeberg.page/reponame`. The page loads without issue. For the moment I'm able to workaround this by copying my repo to a `pages` repo. The page loads without issue at `username.codeberg.page`, but still gets the SSL error at `pages.username.codeberg.page`. Eventually I'll need a repo with a different name in order to host a second static site. Some notes: * The repo has capital letters in it, but no periods or other special characters. Though I doubt this is the issue as use `pages` as the repo name also results in the same error. * I will be using a custom domain name. For now it is point to `username.codeberg.page` so I'm uncertain if pointing to `reponame.username.codeberg.page` will work given the error. * I'm hosting out of the `main` branch without a specific `pages` branch.

Gusted commented 2025年11月20日 13:03:47 +01:00

@RockyMountSDAVA wrote in #2225 (comment):

When I navigate to reponame.username.codeberg.page I get an SSL_ERROR_INTERNAL_ERROR_ALERT. I don't get this if I navigate tousername.codeberg.page/reponame. The page loads without issue.

This is expected behavior. The following format is supported:

Access your new website using this link:
https://USERNAME.codeberg.page[/REPOSITORY][/@BRANCH]

@RockyMountSDAVA wrote in https://codeberg.org/Codeberg/Community/issues/2225#issue-2713056: > When I navigate to `reponame.username.codeberg.page` I get an `SSL_ERROR_INTERNAL_ERROR_ALERT`. I don't get this if I navigate to`username.codeberg.page/reponame`. The page loads without issue. This is expected behavior. The following format is supported: > Access your new website using this link: https://USERNAME.codeberg.page[/REPOSITORY][/@BRANCH]

RockyMountSDAVA commented 2025年11月21日 10:44:35 +01:00

So will reponame.username.codeberg.page work as the TXT or CNAME in my domain registrar without issue? I figured navigating there directly would be a good way to validate I had the correct string, but I guess not.

So will `reponame.username.codeberg`.page work as the TXT or CNAME in my domain registrar without issue? I figured navigating there directly would be a good way to validate I had the correct string, but I guess not.

Gusted commented 2025年11月21日 12:35:57 +01:00

@RockyMountSDAVA wrote in #2225 (comment):

So will reponame.username.codeberg.page work as the TXT or CNAME in my domain registrar without issue?

Yes, it will.

@RockyMountSDAVA wrote in https://codeberg.org/Codeberg/Community/issues/2225#issuecomment-8391417: > So will `reponame.username.codeberg`.page work as the TXT or CNAME in my domain registrar without issue? Yes, it will.