@penguin_ex_machina
@lemmy.worldI don't know when it started, I usually check my instance through the Voyager app and it never showed a problem, but I'm suddenly getting "server error" and 502 bad gateway errors on my instance on desktop. I haven't made any major changes (read, any at all) since I last confirmed it worked on desktop.
Checking the logs I don't see any obvious proxy issues but I am getting weird connection issues in lemmy-ui
:
TypeError: fetch failed
lemmy-lemmy-ui-1 | at Object.fetch (node:internal/deps/undici/undici:11730:11)
lemmy-lemmy-ui-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
lemmy-lemmy-ui-1 | cause: ConnectTimeoutError: Connect Timeout Error
lemmy-lemmy-ui-1 | at onConnectTimeout (node:internal/deps/undici/undici:6869:28)
lemmy-lemmy-ui-1 | at node:internal/deps/undici/undici:6825:50
lemmy-lemmy-ui-1 | at Immediate._onImmediate (node:internal/deps/undici/undici:6857:13)
lemmy-lemmy-ui-1 | at process.processImmediate (node:internal/timers:478:21) {
lemmy-lemmy-ui-1 | code: 'UND_ERR_CONNECT_TIMEOUT'
lemmy-lemmy-ui-1 | }
lemmy-lemmy-ui-1 | }
Where on earth can I even begin to address this?
Hi! I'm hoping for some guidance upgrading my instance. I'm still running on v0.17.3 because I ran into some issues upgrading to 0.18 and didn't have time to really figure it out. Now that the current release is v0.19, I have people on my instance asking to upgrade and I don't blame them. Can I simply point Docker compose at the latest release, or do I have to do incremental upgrades? What do I need to look out for with v0.18? Documentation seems to be pretty slim for whatever breaking changes happened during that release cycle and how to deal with them. Any help is appreciated!
EDIT: Thank you for all the help! I also had to update pictrs and fix some small config issues and then everything worked as expected. I'm now on 0.19.1!
https://hiddenpalace.org/
The Hidden Palace is a community dedicated to the preservation of video game development media (such as prototypes, hardware, source code, artwork, and more). This website can be utilized as a catalog for the items that we and others are able to collect and share.
https://www.youtube.com/watch?v=Tucr8Ta-kq4
Let's start Python GUI Programming from scratch by Creating a Tasks log App 💻For Part 2 Check the following Video:https://youtu.be/vnb4Kiaz5tEContent0:00:00...
https://www.tiktok.com/@pearlmania500/video/7207941159811960106?lang=en
Honestly circuit city going under was a net positive for all my friends income. #circuitcity #grift #recession #elonmusk #twitter #pearlmania500 #itsgettingworse #resume #2009 im sure some tech bro will come into the comments to tell me how this doesnt work anymore. Dont care.
EDIT: I have it working now! I had to set up DKIM and configure my server so Digital Ocean created the proper PTR records. Now email is being sent to spam but at least it's making it through!
Hopefully this is the last time I need to bug you guys here about stuff. :)
I added a postfix relay to my Lemmy instance and configured the email settings in my lemmy.conf
file but no matter what I do I keep getting a "no_email_setup" error when I try to test the SMTP server. Is there an obvious step I'm missing?
This is my full docker-compose.yml
:
version: "3.3"
networks:
lemmyexternalproxy:
lemmyinternal:
driver: bridge
internal: true
services:
proxy:
image: nginx:1-alpine
networks:
- lemmyinternal
- lemmyexternalproxy
ports:
# only ports facing any connection from outside
- 80:80
- 443:443
volumes:
- ./nginx.conf:/etc/nginx/nginx.conf:ro
# setup your certbot and letsencrypt config
- ./certbot:/var/www/certbot
- /etc/letsencrypt:/etc/letsencrypt
restart: always
depends_on:
- pictrs
- lemmy-ui
lemmy:
image: dessalines/lemmy:0.17.3
hostname: lemmy
networks:
- lemmyinternal
- lemmyexternalproxy
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_actor=info,lemmy_db_views_moderator=info,lemmy_routes=info,lemmy_utils=info,lemmy_websocket=info"
volumes:
- ./lemmy.hjson:/config/config.hjson
depends_on:
- postgres
- pictrs
lemmy-ui:
image: dessalines/lemmy-ui:0.17.3
networks:
- lemmyinternal
environment:
# this needs to match the hostname defined in the lemmy service
- LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536
# set the outside hostname here
- LEMMY_UI_LEMMY_EXTERNAL_HOST=localhost:1236
- LEMMY_HTTPS=true
depends_on:
- lemmy
restart: always
pictrs:
image: asonix/pictrs:0.3.1
# this needs to match the pictrs url in lemmy.hjson
hostname: pictrs
# we can set options to pictrs like this, here we set max. image size and forced format for conversion
# entrypoint: /sbin/tini -- /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp
networks:
- lemmyinternal
environment:
- PICTRS__API_KEY=API_KEY
user: 991:991
volumes:
- ./volumes/pictrs:/mnt
restart: always
postgres:
image: postgres:15-alpine
# this needs to match the database host in lemmy.hson
hostname: postgres
networks:
- lemmyinternal
environment:
- POSTGRES_USER=lemmy
- POSTGRES_PASSWORD=PASSWORD
- POSTGRES_DB=lemmy
volumes:
- ./volumes/postgres:/var/lib/postgresql/data
restart: always
postfix:
image: mwader/postfix-relay
networks:
- lemmyinternal
- lemmyexternalproxy
environment:
- POSTFIX_myhostname=myhostname.here
- POSTFIX_inet_protocols=ipv4
restart: always
And my lemmy.hjson
has this block:
email: {
smtp_server: "postfix:25"
smtp_from_address: "Lemmy <noreply@myhostname.here>"
tls_type: "none"
}
Wanted to cross post this here in case someone has had this issue before. Been dealing with this for a couple of days now.
cross-posted from: https://lemmy.world/post/94985
I set up my own personal Lemmy instance yesterday and everything seems to be up and running. I installed it on Docker with SSL enabled on a Digital Ocean droplet.
The only thing that doesn't seem to work is federated search. I can search local communities, but no matter what I do I can't get it to recognize other instances. I've tried:
- Searching with the bang prefix (ie, !lemmy_support@lemmy.ml)
- Searching with the whole URL (https://lemmy.ml/c/lemmy_support)
- Keywords ("lemmy support")
And nothing shows up. I've tried the same search terms multiple times over the past day or so and nothing is changing. My instance has federation and federation debugging enabled (although I can't figure out where the federation debugging outputs yet, because nothing in console log changes), and as far as I can tell there are no errors in the Docker logs that could point me in a specific direction. Where can I start looking to properly debug this?
EDIT: I needed to expose my lemmy backend to the proxy network. This answer here helped me get to the solution. Thanks so much! https://lemmy.world/comment/150173
Let's make a list of our favorite add-ons! For me, I always enable these by default:
Then I go out and get my favorite 3rd party add-ons (note, some of these are paid, some are free):
I'm sure there are others but this list is off the top of my head. What do you all use?