DocTator to Lemmy SupportEnglish · 1 year agoubuntu 22.04 install from scratch .. not even sure what this iswww.lemmydocker.genesis-radio.netexternal-linkmessage-square10fedilinkarrow-up17arrow-down10file-text
arrow-up17arrow-down1external-linkubuntu 22.04 install from scratch .. not even sure what this iswww.lemmydocker.genesis-radio.netDocTator to Lemmy SupportEnglish · 1 year agomessage-square10fedilinkfile-text
minus-squareMax-P@lemmy.max-p.melinkfedilinkEnglisharrow-up2·1 year agoIt looks like you’re reaching the lemmy server directly as opposed to lemmy-ui. What’s your NGINX configuration like?
minus-squareDocTatorOPlinkfedilinkEnglisharrow-up1·1 year agoFor formatting purposes : https://pastebin.com/dbL6HHZc
minus-squareMax-P@lemmy.max-p.melinkfedilinkEnglisharrow-up1·1 year agoYou can use the triple backticks for better rendering on lemmy: imit_req_zone $binary_remote_addr zone=lemmydocker.genesis-radio.net_ratelimit:10m rate=1r/s; server { listen 80; listen [::]:80; server_name lemmydocker.genesis-radio.net; location /.well-known/acme-challenge/ { root /var/www/certbot; } location / { return 301 https://$host$request_uri; } } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name lemmydocker.genesis-radio.net; ssl_certificate /etc/letsencrypt/live/lemmydocker.genesis-radio.net/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/lemmydocker.genesis-radio.net/privkey.pem; location / { proxy_pass http://0.0.0.0:8536; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } access_log /var/log/nginx/access.log combined; Replied on your other comment that you deleted
minus-squareDocTatorOPlinkfedilinkEnglisharrow-up1·1 year agoI got it working mostly. … at least it’s rendering the UI now… Only problem is that when you try to sign up or click on just about anything, it just spins and hangs. Not sure what that’s about.
minus-squareMax-P@lemmy.max-p.melinkfedilinkEnglisharrow-up2·1 year agoYeah so you’re just sending everything to the lemmy server itself, you don’t have the lemmy-ui frontend (which defaults to port 1234). Look at the example NGINX configuration: https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx_internal.conf Notice how it sends different things to one of the two backends. You need this replicated exactly or it won’t work quite right.
minus-squareDocTatorOPlinkfedilinkEnglisharrow-up1·1 year agoyeah, I went by the documentation … that’s completely different from what it tells you… ugh
minus-squareMax-P@lemmy.max-p.melinkfedilinkEnglisharrow-up1·1 year agoYou mean this? https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx.conf That one’s assuming the Docker setup where it’ll send traffic to the internal NGINX, which runs the other config I linked. Yeah the docs aren’t the clearest it seems, had my share of issues getting mine going haha
It looks like you’re reaching the lemmy server directly as opposed to lemmy-ui. What’s your NGINX configuration like?
For formatting purposes : https://pastebin.com/dbL6HHZc
You can use the triple backticks for better rendering on lemmy:
imit_req_zone $binary_remote_addr zone=lemmydocker.genesis-radio.net_ratelimit:10m rate=1r/s; server { listen 80; listen [::]:80; server_name lemmydocker.genesis-radio.net; location /.well-known/acme-challenge/ { root /var/www/certbot; } location / { return 301 https://$host$request_uri; } } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name lemmydocker.genesis-radio.net; ssl_certificate /etc/letsencrypt/live/lemmydocker.genesis-radio.net/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/lemmydocker.genesis-radio.net/privkey.pem; location / { proxy_pass http://0.0.0.0:8536; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } access_log /var/log/nginx/access.log combined;
Replied on your other comment that you deleted
I got it working mostly. … at least it’s rendering the UI now…
Only problem is that when you try to sign up or click on just about anything, it just spins and hangs. Not sure what that’s about.
deleted by creator
Yeah so you’re just sending everything to the lemmy server itself, you don’t have the lemmy-ui frontend (which defaults to port 1234).
Look at the example NGINX configuration: https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx_internal.conf
Notice how it sends different things to one of the two backends. You need this replicated exactly or it won’t work quite right.
yeah, I went by the documentation … that’s completely different from what it tells you… ugh
You mean this? https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx.conf
That one’s assuming the Docker setup where it’ll send traffic to the internal NGINX, which runs the other config I linked.
Yeah the docs aren’t the clearest it seems, had my share of issues getting mine going haha