I’ve followed all of those instructions, making the necessary changes, and now I’m getting this error:
404: FetchError: request to http://lemmy:8536/api/v3/site? failed, reason: getaddrinfo EAI_AGAIN lemmy
Using Lemmy on a smart phone with a browser should work fine since the site is built to be responsive. However, having a native Lemmy application for Android and iOS could provide opportunities for further feature development that isn’t included with the browser version. That is why I believe it is a good idea to keep these apps going.
In what way have they “taken a back seat?” Taken a back seat to what?
Taken a back seat to browser development.
…and look like they’re actively maintained.
Not as actively as the browser development.
I don’t believe those client apps are built by the same folks as Lemmy…
They aren’t except for ‘jerboa’.
…therefore whether they “function properly” is purely a concern for their developers and users.
It’s a concern because most users connect to the Internet through mobile apps.
Lemmy is non-commercial and as such “the market” doesn’t work in the same way as an integrated product like Instagram, Twitter, etc.
I’m not addressing the differing world market systems. I’m addressing how most people connect to the Internet.
Maybe I’ve missed something, but let me tell you what I’ve done and see if you can catch anything that I may have done wrong. OK?
I first logged into PostgreSQL and used the ALTER ROLE to change the password of the user that is accessing the ‘beehaw_db’ database. I made sure that this exact password is entered properly in both the docker-compose.yml and lemmy.hjson files.
I’m still getting the same authentication error. Am I missing something? What would you recommend as far as troubleshooting this?
In the lemmy.hjson I had the wrong database name. I’ve changed it to 'beehaw_db which I can see the ‘owner’, in postgres itself, is ‘admin’. So, I changed the username to ‘admin’ in the same hjson file.
Now, I’m getting:
lemmy_1 | 2022-01-24T15:57:58.976448Z ERROR r2d2: FATAL: password authentication failed for user "admin"
{
# for more info about the config, check out the documentation
# https://join-lemmy.org/docs/en/administration/configuration.html
# settings related to the postgresql database
# address where pictrs is available
pictrs_url: "http://pictrs:8080"
database: {
# name of the postgres database for lemmy
database: "lemmy"
# username to connect to postgres
user: "lemmy"
# password to connect to postgres
password: “baconshit”
# host where postgres is running
host: "postgres"
# port where postgres can be accessed
port: 5432
# maximum number of active sql connections
pool_size: 5
}
# the domain name of your instance (eg "lemmy.ml")
hostname: "beehaw.org"
# Settings related to activitypub federation
federation: {
# Whether to enable activitypub federation.
enabled: true
# Allows and blocks are described here:
# https://join-lemmy.org/docs/en/federation/administration.html///instance-allowlist-and-blocklist
#
# list of instances with which federation is allowed
allowed_instances: [
lemmy.ca
midwest.social
/* ... */
]
# Instances which we never federate anything with (but previously federated objects are unaffected)
blocked_instances: [
string
/* ... */
]
# If true, only federate with instances on the allowlist and block everything else. If false
# use allowlist only for remote communities, and posts/comments in local communities
# (meaning remote communities will show content from arbitrary instances).
strict_allowlist: true
}
# tls_enabled: true
}
I’ve added those creds back in and I’m getting this in the Docker logs:
lemmy_1 | 2022-01-23T19:46:10.980030Z ERROR r2d2: FATAL: password authentication failed for user "lemmy"
Also, browser still throws:
https://beehaw.org/404?err=FetchError:%20request%20to%20http://lemmy:8536/api/v3/site?%20failed,%20reason:%20connect%20ECONNREFUSED%20172.30.0.4:8536
Not sure what to try next. Any ideas? Thanks again for the help.
I just found the typo in that file and fixed it. Site is back up and running! Thank you for your help!