424 Failed Dependency #30

Closed
opened 6 months ago by ghose · 6 comments
ghose commented 6 months ago

I've created a new pages repo in my account following this instructions but I got

image with info

when I go to https://ghose.codeberg.page/

I have default values for privacy (none) and my index.html (basic page without scripts and/or external resources) is on main (the only available branch ATM)

I'd appreciate any hint about how to solve this issue. Thank you.

Is it actually a bug?

EDITED

Settings

settings, default values

I've created a new `pages` repo in my account following [this instructions](https://codeberg.page/) but I got ![image with info](https://i.imgur.com/WA3dfyT.png) when I go to https://ghose.codeberg.page/ I have default values for privacy (none) and my `index.html` (basic page without scripts and/or external resources) is on `main` (the only available branch ATM) I'd appreciate any hint about how to solve this issue. Thank you. Is it actually a bug? **EDITED** Settings ![settings, default values](https://i.imgur.com/eVmRo8G.png)
Collaborator

Hmm, seems like as your user visibility is limited the repo isn't visible to the public (non-logged-in users) at all - that should still work as we have a bot user for such cases, I will have a look into that.

Hmm, seems like as your user visibility is limited the repo isn't visible to the public (non-logged-in users) at all - that should still work as we have a bot user for such cases, I will have a look into that.
momar added the
bug
label 6 months ago
Poster

thank you @momar

I had my profile "visibility" set to "limited". I've changed it to "public" and now pages work as expected.

So this "issue" is solved (for me), but I guess could affect to other users.

Thank you!

thank you @momar I had my profile "visibility" set to "limited". I've changed it to "public" and now pages work as expected. So this "issue" is solved (for me), but I guess could affect to other users. Thank you!
Collaborator

Environment=GITEA_API_KEY=https://{{ gitea_api_key }}

How stupid can one be when copy-pasting...

Edit: and it's also GITEA_API_TOKEN... 🤯

Edit2: it's deployed now and should be working correctly with limited repositories.

`Environment=GITEA_API_KEY=https://{{ gitea_api_key }}` How stupid can one be when copy-pasting... Edit: and it's also `GITEA_API_TOKEN`... 🤯 Edit2: it's deployed now and should be working correctly with limited repositories.
momar closed this issue 6 months ago

@momar

Hi

The same issue is happening to my website. It is a public repository and I set up the .domains file and the DNS records for this. The URL is thegoldenspearsproject.net. Can you take a look into it?

@momar Hi The same issue is happening to my website. It is a public repository and I set up the `.domains` file and the DNS records for this. The URL is [thegoldenspearsproject.net](thegoldenspearsproject.net). Can you take a look into it?
Collaborator

@thegoldenspearproject-developer I think you're missing a TXT record to thegoldenspearproject-developer.codeberg.page for your main domain thegoldenspearsproject.net, in addition to the A/ALIAS record.

When going to www.thegoldenspearsproject.net (where you're using a CNAME record), it probably can find the .domains file, but still fails as it can't resolve the main domain thegoldenspearsproject.net as a Codeberg Page - mentioning #28 as that's something where the error message can be improved.

@thegoldenspearproject-developer I think you're missing a TXT record to `thegoldenspearproject-developer.codeberg.page` for your main domain thegoldenspearsproject.net, in addition to the `A/ALIAS` record. When going to www.thegoldenspearsproject.net (where you're using a `CNAME` record), it probably can find the `.domains` file, but still fails as it can't resolve the main domain thegoldenspearsproject.net as a Codeberg Page - mentioning #28 as that's something where the error message can be improved.

That problem's solved. And thx for the help. But now when I access the site via the custom domains, the browser shows a warning about bad certificates. I see now that the certificates used are still only valid for codeberg domains. Is that because it takes some time for codeberg to generate and apply the correct certificates?

That problem's solved. And thx for the help. But now when I access the site via the custom domains, the browser shows a warning about bad certificates. I see now that the certificates used are still only valid for codeberg domains. Is that because it takes some time for codeberg to generate and apply the correct certificates?
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.