Post AXHjsg7aTSYflXdUQ4 by benzucker@maly.io
(DIR) More posts by benzucker@maly.io
(DIR) Post #AXHiLILbkBmIWQiBCi by stux@mstdn.social
2023-07-02T13:08:48Z
0 likes, 0 repeats
Hmm.. I don't know what wrong ๐ฉ Yesterday I've updated our #Lemmy instance just by editing the Docker file but now it returns "Server error" and that's it..Can't find any errors in any of the logs, super frustratingAnyone ideas?
(DIR) Post #AXHilPBewAnlGPVayG by hahajl@m.cmx.im
2023-07-02T13:13:38Z
0 likes, 0 repeats
@stux lol
(DIR) Post #AXHio9iqtIMcAaLVJI by benfrog@mstdn.social
2023-07-02T13:14:10Z
0 likes, 0 repeats
@stux Docker is a house of cards, and by default most instances log to stdout if you haven't modified that setting. The conflict is likely between _a_ dockerfile (remember they are all put together) and your Docker Compose file (remember that literally each dockerfile is loaded into your dockercompose file in the "context" section).
(DIR) Post #AXHj0DojUZW4LQqlKC by benzucker@maly.io
2023-07-02T13:16:20Z
0 likes, 0 repeats
@stux Welcome to the club...
(DIR) Post #AXHjE3TSkCJKJvUtI8 by Mx_EddyNikko@universeodon.com
2023-07-02T13:18:49Z
0 likes, 0 repeats
@stux Yes, good luck with a fix
(DIR) Post #AXHjhcFKXd8uYtyzFQ by benzucker@maly.io
2023-07-02T13:16:48Z
0 likes, 0 repeats
@stux After wasting two days I gave up on it and started over from scratch by emptying the database folder.
(DIR) Post #AXHjhcuo3QJsdXO6tc by stux@mstdn.social
2023-07-02T13:24:05Z
0 likes, 0 repeats
@benzucker I already did that once :catblush: Docker is soooooo not my friend :bloblaugh: Somehow i have a feeling this is also gonna costs me days
(DIR) Post #AXHjsg7aTSYflXdUQ4 by benzucker@maly.io
2023-07-02T13:26:10Z
0 likes, 0 repeats
Let me know if you are successful one day so maybe I put some more work into my "Low Effort Federated . Lemmy Instance" ๐
(DIR) Post #AXHk2ZrAcaFpEQg34i by oliver@die-partei.social
2023-07-02T13:27:51Z
0 likes, 0 repeats
@stux Asking #lemmy:matrix.org. Huge userbase and if no one else knows what to do, dessalines answers himself answers 2 days later. ๐น
(DIR) Post #AXHmQ7MePFQHiskqZ6 by AXHmQ72nb3XkjJSzce.Aleks76@mastodon.borsos.at
2023-07-02T13:49:48Z
0 likes, 0 repeats
@stux What did you changed in Dockerfile?
(DIR) Post #AXHmQ8Mggb2wpHmOGG by stux@mstdn.social
2023-07-02T13:54:34Z
0 likes, 0 repeats
@Aleks76 The images forLemmy, Lemmy-UI and Pictrs only ๐ฎ I did discover this though
(DIR) Post #AXHnAo189jMpKTx2Rs by AXHmQ72nb3XkjJSzce.Aleks76@mastodon.borsos.at
2023-07-02T14:02:37Z
0 likes, 0 repeats
@stux can you try to reach the redit URL from the same machine with curl -v? Maybe also check if your port 443 on localhost is not in use with following command : netstat -atonp|grep 443
(DIR) Post #AXHoT4RluRKVS4gZoe by markymarrow@mstdn.social
2023-07-02T14:17:19Z
0 likes, 0 repeats
@stux @Aleks76 127.0.1.1 are you sure thatโs correct? localhost generally being 127.0.0.1
(DIR) Post #AXHox2aXNsKgNJ4oQy by stux@mstdn.social
2023-07-02T14:21:45Z
0 likes, 0 repeats
@markymarrow @Aleks76 it's weird indeed!It should be localhost and not on 443 also ๐ค But the thing is, nothing has changed in the Docker file with ports or whatever. Only the image versions
(DIR) Post #AXHp4o01VdWLRdhSRE by shanihp@mastodon.social
2023-07-02T14:23:21Z
0 likes, 0 repeats
@stux why does geddit.social resolve to 127.0.1.1 on your system (rather than the public ip)? the ECONNREFUSED is L4 tcp connect error. nothing is listening on port 443
(DIR) Post #AXHpFyHJdIWkVf72Su by stux@mstdn.social
2023-07-02T14:26:15Z
0 likes, 0 repeats
@shanihp Yes... Good questionIt should or revolve to the internal on 8080, nginx proxies everything to external
(DIR) Post #AXHpeZ9wA5klqOOBBg by shanihp@mastodon.social
2023-07-02T14:30:25Z
0 likes, 0 repeats
@stux is the lemmy container running? so you actually setup a dns override locally on your machine/docker setup so that geddit.social points to localhost? and you're expecting lemmy-ui talks to lemmy over http/8080 rather than https/443 ?check the lemmy-ui doc around the config, maybe something changed (since it uses https://geddit.social, instead of http://geddit.social:8080)
(DIR) Post #AXHq6eCyyzf3c0Ch96 by stux@mstdn.social
2023-07-02T14:34:49Z
0 likes, 0 repeats
@Aleks76 @markymarrow Hm.. when i shut down nginx and restart the containers it "works" until i fire up nginx again and it's loading the same errors againBut i didn't change a thing in the ports, or nginx configs ๐ค
(DIR) Post #AXHqJ1C7LZhuNQhKme by stux@mstdn.social
2023-07-02T14:35:57Z
0 likes, 0 repeats
@Aleks76 @markymarrow lol..The instance does come online now, ony for a bit i think... yesterday it also crashed after a bit
(DIR) Post #AXHrE9cqflgT22RhCa by AXHmQ72nb3XkjJSzce.Aleks76@mastodon.borsos.at
2023-07-02T14:47:30Z
0 likes, 0 repeats
@stux @markymarrow try this please to see which ports are exposed:docker exec -it c769b8d0a2ff cat Dockerfile|grep EXPOSE, (replace c769b8d0a2ff with your CONTAINER ID, once it runns) and then check the Ports on running instances where are they mapped: docker ps
(DIR) Post #AXI3A7nQjO3LeMEx9s by chaosmonkey@masto.ai
2023-07-02T17:00:17Z
0 likes, 0 repeats
@stux Just saw this... I have loads of experience in Docker and containers in general. Feel free to DM me the Docker file or other details if you want. Happy to take a look.By the way, I just setup Lemmy myself at weddit.eu(not open to public yet, in alpha)
(DIR) Post #AXIJYe1OAWyboLU0q8 by jeaveme@hachyderm.io
2023-07-02T20:05:54Z
0 likes, 0 repeats
@stux why are you using lemmy-ui v0.18.0 instead of 0.18.1-rc.7?
(DIR) Post #AXIJdMj5tnRDcSB2VE by stux@mstdn.social
2023-07-02T20:06:48Z
0 likes, 0 repeats
@jeaveme yeah little mistake, also with RC 0.18.1 same issue :(
(DIR) Post #AXIKSNFLiy2o09aRm4 by jeaveme@hachyderm.io
2023-07-02T20:15:39Z
0 likes, 0 repeats
@stux ok, didn''t have much hope that was the cause because it is just the patch number, but just in case... :(