-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
server keeps restarting #37
Comments
I think the Docker build needs to be updated. Full details here. Copy-pasta follows: Advisory: ssb-server crash fixed A bug in ssb-links causes ssb-server to crash when handling certain messages recently published. The main error message on crash is: Error: can only encode arrays. This bug is fixed in ssb-links v3.0.10. If you encounter this crash, please reinstall/upgrade your ssb-server to get the updated ssb-links module. It is possible a similar issue could exist with other #ssb plugins using flumeview-links, in which case we will update this thread. This issue primarily affects pub operators and users who run ssb-server directly. Users of apps that bundle ssb-server (e.g. Patchwork) are not affected. There are no known security implications. |
@sunjam is correct, an updating version is incoming. sorry for the delay. 💜 |
published a new version which should fix this:
i've upgraded my own 3 pubs and they seem to be happy again. 😺 |
ℹ️ the upgrade process for pub operators: https://github.com/ahdinosaur/ssb-pub#update-ssb-pub-image (if already using v2, otherwise see v1 -> v2 upgrade guide )
check your pub is running with commands like:
|
Can you please spell out the update process to get things working again.
It is failing for me, perhaps related to the helper. Unsure, but I'm still
offline
…On Mon, Nov 9, 2020, 8:25 PM Mikey ***@***.***> wrote:
published a new version which should fix this: v2.2.0 🎉
- updated to use ***@***.***: ssbc/ssb-server#739
<ssbc/ssb-server#739>)
- updated to use Node 14
i've upgraded my own 3 pubs and they seem to be happy again. 😺
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANUKZVH2VSKT73VFHP2E2LSPC6EFANCNFSM4SKSTOTQ>
.
|
@sunjam: i might have been too optimistic. do you see an error, or just that you can't connect to your server from a client? i also realized now invites are broken.
ughhhhh 😿 |
Yes, updated pull fixed the pub running, but I see the exact same error you posted when creating invites. |
okay, i think figured out the invite problem: ssbc/secret-stack#62. the hotfix is to change your (change connections.incoming.net[].external from an array of strings to a string) {
"connections": {
"incoming": {
"net": [
{
"scope": "public",
"host": "0.0.0.0",
- "external": ["hostname.yourdomain.tld"],
+ "external": "hostname.yourdomain.tld",
"transform": "shs",
"port": 8008
}
]
},
"outgoing": {
"net": [
{
"transform": "shs"
}
]
}
}
} |
and change `install.sh` to match. ref: #37 (comment)
and change `install.sh` to match. ref: #37 (comment)
and change `install.sh` to match. ref: #37 (comment)
Thanks for the hotfix, @ahdinosaur !! 🙏 |
I think this may be related to the recent bug in ssb-links; but my pub keeps restarting and no longer works. How do I recover?
The text was updated successfully, but these errors were encountered: