Working Setup files, for my ARM64 Ubuntu host server.
The postgres, lemmy, lemmy-ui, and pictrs containers all are on the lemmyinternal network only.
The nginx:1-alpine container is in both networks.
docker-compose.yml
lemmy.hjson:
The following nginx.conf is for the internal proxy, which is included in the docker-compose.yml
This is entirely separate from Nginx-Proxy-Manager (NPM)
nginx.conf:
The nginx-proxy-manager container only needs to be in the same container network as the internal nginx:1-alpine container from the stack.
You need to create a proxy host for http port 80 to the IP address of the internal nginx:1-alpine container on the lemmyexternalproxy network in docker. Include the websockets support option.
Yea Ill do a write up in a bit with everything I can share that helped. Ill post it under the original thread. Not sure if I can sticky things but Ill try.
It would seem it was called "Internal" as opposed to isolated on my Portainer. That appears to have been it though.
I can get to other communities now.
Still having disparity with posts and comments showing up, but Im hoping that will be something to update in time.
I see my Pictrs appears to be the same as what you had sent over.
Protainer network isolation does not appear to be in place. All are bridged networks, and I would assume access issues would be more encompassing if that were a direct correlation to the issue.
Im still betting on User Error for configuration so far. Being myself, of course.
The differences I see are the otel link, and the TLS setting:
# Whether the site is available over TLS. Needs to be true for federation to work.
tls_enabled: true
I see you dont have it on there, which I would assume means you cant be federated?
I have added the otel link and enabled the debug mode. Federation is already enabled and the instance is set to "ALL". Still no luck on this end. Same status, except now im not getting any log errors in the container logs (Viewed from Portainer).
Including this in case it is a possible issue:
federation enabled, host is lemmy.bulwarkob.com
Hey, does your instance have the "UI: v0.XX.X" tag at the bottom of the page? Mine does not, only the BE tag.
I see other successful instances DO have it. Wondering if somehow related.
Not yet. Based on my error logs, Im thinking some sort of websocket issue where operations are timing out trying to communicate with other instances.
Unfortunately I am not well familiar with NGINX and proxies in gerenal (hence using GUI based NPM).
Im hoping I can find a kind soul to basically walk with me through my setup and see if the issue can be pinpointed.
Ill definitely post how it got working if/when I get there.
I believe I have the simple set up for the NPM reverse proxy. Just as you say, it points to the docker address of the lemmyInstance NGINX. I can get to my instance with HTTPS secured and good.
Just getting errors when communicating to other instances.
I can only imagine it is web socket related, but I am not familiar enough to look at the proxy configs and determine what might be wrong with it unfortunately.
I might need to try and find someone to essentially look through it with me in real time.
Do you know if I should expect to have TWO unique NGINX proxy instances (assuming I use NGINX)? One in-stack, and one separate for web facing reverse proxy? Or do I need a combination of the two configs into one instance?
I am going to see if I can get a caddy reverse proxy setup in the meantime and see how it performs given your configuration there.
Ive been through a boatload of changes today since earlier.
Ive rebuilt using mostly the provided yml in the official guide, and after some tweaking, almost everything is working.
The internal proxy is now working, and the containers are working amongst themselves fully as far as I can tell.
I do not know how to setup a web facing reverse proxy in a way that works around the internal proxy already running (other than the already in place NPM).
I turned the NPM back on, and was able to get it working to reach the site, however I cannot reach any other communities from within my site. I believe the reverse proxy NPM is just not set up right.
Error message in lemmy:
I would be happy to remove NPM from this stack if its not too difficult to get a correctly working reverse proxy set up. The documentation doesnt give much to work with in it.
I actually started with this tutorial a few days ago after failing the official guide. I followed it but was unable to get it running due to unexpected errors. Im guessing this tutorial is somewhat out of date.
Ive made progress since using that guide though so I will see if I can pull any useful bits out of it later today and continue.
Worst case, I could also just ditch NPM if I can get another NGINX set up in a way that you might know how to do correctly.
Id love to give anomaly 2 a try