# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 6
# self = https://watcher.sour.is/conv/szsrzxq
So I setup a Cloudron installation on a Vultr VM.
Install went okay.
Setup the first (admin) user okay.
Tried to login:
> Invalid Username or Password
🤦♂️ FAIL 🤦♂️
So I setup a Cloudron installation on a Vultr VM.
Install went okay.
Setup the first (admin) user okay.
Tried to login:
> Invalid Username or Password
🤦♂️ FAIL 🤦♂️
@prologic This sounds like a non-ideal user experience. Any idea what happened there or no?
The way Sandstorm generally addresses the initial-user setup problem is that you can generate an "admin-token" from the CLI to log in administratively one time, and do whatever account setup (or OAuth configuration recovery) that you need to do.
I'm kinda curious where they failed out on this, considering it's a ready-to-deploy app they support on Vultr, from the looks of it.
@ocdtrekkie no idea what happened I'm afraid and unfortunately their community is a bit stagnant? So I probably won't find out for Sundays. It was a complete fresh install I followed the instructions exactly.
@ocdtrekkie no idea what happened I'm afraid and unfortunately their community is a bit stagnant? So I probably won't find out for Sundays. It was a complete fresh install I followed the instructions exactly.