️ WARNING ️
# as user root or sudo # If /dev/sda is your drive dd if=/dev/urandom of=/dev/sda status=progress
Cloudron App Packagers
Oh I see. Since I had access to your instance for fixing the issue anyways, I saw that the app was healthy and running, but the nginx reverse proxy config wasn't correctly updated.
This may actually be a bug in Cloudron. The reason likely is that I've changed the app's internal port from 80 to 8000 to not require apache to run as root.
To fix this quickly, I've just submitted the location form of the app configure, which triggers a recreation of the reverse proxy files.
At least for me the app is now reachable.
This explains a lot.
@girish Digging this back up again. So I found the config file, however removing the disallowed peers doesnt work as it is all reset when the turn server is restarted.
@robi For your setup is your computer and server on the same network? I'm seeing 401s every time I try to connect with others.
@ianhyzy You can try this one by one:
systemctl stop docker . Does this make the server unresponsive after 30 minutes?
systemctl stop box docker . Does this also make server unresponsive after 30 minutes?
I can help debug further, one you tell me if 1 or 2 is causing issues.