I'm assuming that this link is only available to instance admins? What, precisely, happens when this link is clicked?

I made the two version number changes to my docker-compose.yml file. Ran Docker Compose Down then Docker Compose Up -D. Visit https://beehaw.org and you'll see the error in your browser: > 404: FetchError: request to http://0.0.0.0:8536/api/v3/site

I'm assuming, out of all the Activity-Pub connected 'Fediverse', there are a handful of instances that get the most activity. That being assumed, is there an app (mobile and otherwise) that, functionally, includes most of these instances? For example, is there an app that can seamlessly handle Mastodon, Lemmy, Friendica, Hubzilla, Peertube, etc?

I, recently, started running a Lemmy [instance](https://beehaw.org/). I am, also, new to Linux servers. At the advisement of some tech acquaintances, I've installed [UnnattendedUpgrades](https://wiki.debian.org/UnattendedUpgrades) and [Fail2ban](https://en.wikipedia.org/wiki/Fail2ban). What would you recommend?

It's my, general, understanding that **most** people connect to the Internet through mobile apps. If this is the case, then why have apps such as [Remmel](https://github.com/uuttff8/Remmel), [Lemmur](https://github.com/LemmurOrg/lemmur) and [jerboa](https://github.com/dessalines/jerboa) taken a back seat? IMHO, it would be a mistake to market Lemmy without these mobile apps functioning properly. I have forked the three aforementioned mobile apps [here](https://github.com/beehaw-org) and will try to 'drum up' support from developers wherever I can find them. Please, if you don't feel comfortable talking to me about this here, then send me a private message. Thank you.

 Our instance has unchecked 'Enable Downvotes' which we believed would prevent downvoting.  As you can see, this is not the case. Is this setting federated? If not, why?

When I say 'seem to be' I mean 95% of the time when I check beehaw.org for the 504, I then check lemmy.ml and it is 504 as well. Other users of beehaw.org are reporting the same behavior as well.  

> Is there a way to see a list of all of the registered users on an instance? > Can we restrict registered usernames (e.g. not allow slur-filled usernames)? > Are all Lemmy instances openly federated unless they are on the block list?

`OpenTelemetry trace error occurred. cannot send span to the batch span processor because the channel is full`

We just launched our instance at https://beehaw.org not too long ago. However, a good number of people have been asking questions like this for the past several days on our Discord server. P.S. - I will have a big surprise (hopefully...if all goes well) for the Lemmy community in March.

RE: https://lemmy.ml/post/153893/comment/114138 ~~Should we expect a fix for this latest bug in the next week? Longer, perhaps?~~ Just saw on the Matrix room that it would be a few days. Thanks!

After running docker-compose up -d my Docker logs are reporting: `thread 'main' panicked at 'Couldn't initialize settings.: LemmyError { message: None, inner: Eof at 58:1 at "", context: "SpanTrace" }', src/main.rs:52:35` Any ideas?

After running docker-compose up -d, my Docker logs produce this error: ``` ERROR r2d2: could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432? ``` I've checked docker-compose.yml, lemmy.hjson, /etc/nginx/sites-enabled/lemmy.conf and don't see anything unusual. Any ideas how to troubleshoot this?

Current lemmy.hjson configuration file (with or without the closing bracket...both do not work): ``` { # 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 } } ``` Docker logs: ``` lemmy_1 | thread 'main' panicked at 'Error connecting to postgres://lemmy:password@localhost:5432/lemmy', src/main.rs:65:25 lemmy_1 | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace lemmy_lemmy_1 exited with code 101 lemmy_1 | 2022-01-23T12:53:58.959887Z ERROR r2d2: could not connect to server: Connection refused lemmy_1 | Is the server running on host "localhost" (127.0.0.1) and accepting lemmy_1 | TCP/IP connections on port 5432? lemmy_1 | could not connect to server: Address not available lemmy_1 | Is the server running on host "localhost" (::1) and accepting lemmy_1 | TCP/IP connections on port 5432? ``` Safari browser throws this error when attempting to reach https://beehaw.org `https://beehaw.org/404?err=FetchError:%20request%20to%20http://lemmy:8536/api/v3/site?%20failed,%20reason:%20connect%20ECONNREFUSED%20172.23.0.4:8536` So, my instance is connecting from a secured HTTPS and the lemmy connection is attempting to connect to an unsecured HTTP. docker-compose.yml: ``` version: '2.2' services: postgres: image: postgres:12-alpine environment: - POSTGRES_USER=lemmy - POSTGRES_PASSWORD=thr33n1n3 - POSTGRES_DB=lemmy volumes: - ./volumes/postgres:/var/lib/postgresql/data restart: always lemmy: image: dessalines/lemmy:0.15.1 ports: - "127.0.0.1:8536:8536" restart: always environment: - RUST_LOG="warn,lemmy_server=info,lemmy_api=info,lemmy_api_common=info,lemmy_api_crud=info,lemmy_apub=info,lemmy_db_schema=info,lemmy_db_views=info,lemmy_db_views_ac> volumes: - ./lemmy.hjson:/config/config.hjson depends_on: - postgres - pictrs lemmy-ui: image: beehaw/frontend-ui:latest ports: - "127.0.0.1:1235:1234" restart: always environment: - LEMMY_INTERNAL_HOST=lemmy:8536 - LEMMY_EXTERNAL_HOST=beehaw.org - LEMMY_HTTPS=false depends_on: - lemmy pictrs: image: asonix/pictrs:v0.2.6-r2 ports: - "127.0.0.1:8537:8080" user: 991:991 volumes: - ./volumes/pictrs:/mnt restart: always ```

I have a, fairly, new instance up with several people examining the moderation tools. Someone noticed that the 'remove' option at both the post level and the comment level could be improved upon and I agree with them. Our conclusion is that these would be more user-friendly/intuitive if they were 'remove post' and 'remove comment' respectively.

Using Docker, I've upgraded Lemmy from 0.13.0 to 0.14.1. How do I upgrade to the latest Lemmy UI?

My site certificate **only** supports non-www addresses. So, when we try to access an image uploaded to the site we are getting a bad certificate warning because there is a 'www' in the address. Is there a solution for this?