Technology

37696 readers

243 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

Lemmy behind 2 Proxies (sedd.it)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

Just wanted to know if I should expect any issues with this set-up. 1st proxy is NGINX on the host machine (Ansible-setup). 2nd proxy is NGINX on OPNsense. I'm using self signed certs on the host machine because I don't want port 80 left open. OPNsense ACME plugin manages my certificates.

I've noticed that a lot of comments do not get pulled with posts. Also, I am unable to log in to my server with Jerboa.

Does lemmy use port 80 for anything besides getting SSL certs? Will the double proxy screw up federation or my ability to log in through 3rd party solutions?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago (1 children)

I am running mine with two nginx proxies in lurbenetes for similar reasons. i run a nginx container with the standard nginx.config from the docs, then I have an ingress with let's encrypts SSL certificate and domain info. I added a annotation for websocksts and just pointed to the first proxies / path for the parent proxies path.

Comments don't sync right right now because of the federation setup and people hosting so many private instances / shutting them off. There is a timeout that is being exceeding so not all instances are getting the update from the main instance that there was an update.

[–] [email protected] 0 points 1 year ago (2 children)

Maybe web sockets aren't setup properly for me on OPNSense NGINX. I'll have to look into that. Could be that Jerboa needs websockets to log in?

[–] [email protected] 1 points 1 year ago

My first thought when you mentioned those issues with Jerboa and comments was websockets. This is how the lemmy devs configure nginx, and I would make sure your setup on OPNSense is similar, specifically the "Upgrade" and "Connection" header bits.

[–] [email protected] 1 points 1 year ago

Fun fact since 0.18.0 is out, they dropped websockets.