Closed prezmix closed 2 months ago
Can conform this issue. Generating meta info is essential for sharing links on social media, so it's quite important to have.
After running in CSR for a while and attempting to run in SSR again I did not get the same error as reported in 253 but instead just a 502 from nginx:
2024/05/10 10:37:05 [error] 5540#5540: *9122184 upstream sent too big header while reading response header from upstream, client: 172.18.0.1, server: myserver.com, request: "GET /post/myserver.com/17 HTTP/1.1", upstream: "http://172.18.0.37:80/post/myserver.com/17", host: "myserver.com"
This was a simple fix by adding some nginx directives to increase the buffer size. In my case with nginx-proxy-manager:
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/438
Seems to work now though still do not understand why the initial errors are gone, though I suspect could have been initially caused by no posts in the lemmy db.
Describe the bug Per 260 and 253 no meta information is generated at all and the proposed solution of running in SSR mode does not work as the app doesn't work in SSR mode using the official docker image as already reported by many.
Viewing source also exposes the env vars.
To Reproduce (if applicable) Go to any post on official instance eg. https://phtn.app/post/lemmy.world/15076463 and view source to confirm lack of meta tags and the exposed env vars, eg.
Expected behavior Meta information should be generated eg. the post should show all the meta information as in
/photon/src/routes/post/[instance]/[id=integer]/+page.svelte
:@CorvetteCole was successful with SSR and the meta tags are being shown correctly, eg. viewing source for https://lemdro.id/post/lemdro.id/8275014:
He apparently did this by unpacking the docker images into his VM, but that is not feasible.
Any efforts on this would be appreciated!
Thank you for a great front end.