Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Do you get the same error by running psql on terminal?
I don't know how to do this yet, but this will be the first thing I try this morning.
Frustratingly, when you use psql on the terminal, it does not prompt you for a password. So I'm still not sure if the password works or not :(
Ahh, ok... if you add the
-W
option when logging in to psql (psql -U lemmy -W
), it will prompt for the password.The password works! So, apparently it's something with the connection string.
Turns out, unless you update
pg_hba.conf
to force password use, using the-W
option prompts for a password, but authenticates with any value entered.