10
310
Fork
You've already forked codeberg-cli
33

SSL error when cloning repository #264

Open
opened 2025年11月27日 17:20:52 +01:00 by dotcarmen · 4 comments

I've managed to successfully create a repository using the cli, however i'm failing to clone it - which is interesting, considering I successfully cloned a new fork not too long ago

After running berg repo clone dotcarmen/foo (it's a private repo as i'm want to do with early dev) i get this error:

there is no TLS stream available; class=Ssl (16)

i'm on macOS Tahoe 26.1 and i'm using an SSH key

I've managed to successfully create a repository using the cli, however i'm failing to clone it - which is interesting, considering I successfully cloned a new fork not too long ago After running `berg repo clone dotcarmen/foo` (it's a private repo as i'm want to do with early dev) i get this error: ``` there is no TLS stream available; class=Ssl (16) ``` i'm on macOS Tahoe 26.1 and i'm using an SSH key

This appears to be an issue with the homebrew packaging - when I built it myself it worked

This appears to be an issue with the homebrew packaging - when I built it myself it worked

Oh weird, if i 'cargo install' it doesnt work, but 'cargo build' from source does. How odd...

Oh weird, if i 'cargo install' it doesnt work, but 'cargo build' from source does. How odd...

On my end, I'm encountering this issue regardless of using Brew, using cargo install, or cargo build.

On my end, I'm encountering this issue regardless of using Brew, using cargo install, or cargo build.
Owner
Copy link

Can anyone here try with the latest state of the main branch? I haven't done anything other than update the dependencies. Currently I'm hoping for it to be fixed by upstream changes.

Otherwise I don't really have good options of debugging this. I have a test setup for the command and the test passes as expected. So it really seems to be more of a platform issue. Maybe I can try to give you some instructions if I get an idea.

One more question:

  • Are you targeting codeberg.org or another forgejo instance?
Can anyone here try with the latest state of the main branch? I haven't done anything other than update the dependencies. Currently I'm hoping for it to be fixed by upstream changes. Otherwise I don't really have good options of debugging this. I have a test setup for the command and the test passes as expected. So it really seems to be more of a platform issue. Maybe I can try to give you some instructions if I get an idea. One more question: - Are you targeting codeberg.org or another forgejo instance?
Sign in to join this conversation.
No Branch/Tag specified
main
v0.5.1
v0.5.0
v0.4.11
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.1
v0.4.2
v0.4.0
v0.3.5
v0.3.4
v0.3.2
v0.3.1
v0.3.0
v0.2.1
v0.2.0
v0.1.1
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 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
Aviac/codeberg-cli#264
Reference in a new issue
Aviac/codeberg-cli
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?