-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
check
command results in Error: no async:whoami
on various cloud providers
#19
Comments
On the other hand if I execute these instructions on my plain old laptop, my ssb room container runs without error. possibly this is OVH-specific? Any debugging tips? |
Error: no async:whoami
on various cloud providers
Error: no async:whoami
on various cloud providerscheck
command results in Error: no async:whoami
on various cloud providers
NB this is the same error as reported at #21 for Digital Ocean. As such we can assume it occurs for various setups Also as noted at #21 the room server still starts and appears to function. It is just the |
Same problem
After removing the health check the web-server is exposed by my proxy (traefik). |
Sorry, does that mean the ssb-room is Basically Working Properly after you removed the health check? Thanks! |
AFAICT the ssb-room I have is running on a cheap VM successfully without any changes. It just throws ugly errors; I'm currently caught up on a different distribut edsocial network system so don't have time to sort out exactly what I did, despite my bold claims I would document it, sorry. |
@danmackinlay Thanks for the quick reply!
Did you wind up using a DO droplet? How did you get the room up and running?
Curious: which one? |
@denisgoddard
yes
I used
|
Is there a way to understand what causes it? I have my own computer and I'm trying to run my own room, but I have this error. Also, it seems that error marks the container unhealthy. Edit: That makes the healer script useless. It will just restart it every time. The room works great so far. |
Running the manual install instructions creates a room that seems to start up but cannot pass a
./room check
succesfully.Here is a transcript of the state the system gets in to, on an ovh.com vanilla Debian 10 VM.
The text was updated successfully, but these errors were encountered: