Yeah the separate nginx container just feels... Hacky lol
@exploding-heads.com
I just found out my posts are finally going through without any changes using the nginx proxy container to nginx ingress method! If you do have a way to do it all directly through nginx I'd love to see how it's all done, maybe I was missing something outside of the snippet you posted.
Since it's currently working I'll look into spinning a test instance up when I get a chance and play with that ingress annotation.
I had an AI write 95% of my kurbenetes config. I had this at one point, it is likely you are not proxying (usually nginx) the Lemmy backend to /api and there are are other endpoints that need mapped to it too.
Doing this made / path with Lemmy ui break, but posts and comments were actually updating according to logs. i set it up with a nginx container behind my ingress now and it appears everything works besides my comments and posts not being federated even though I can curl the links for troubleshooting federation without issue. Got any ideas?
Yeah seems like they are pretty strict on what you are doing, i assume not having a business on the account affects it too. Maybe depends on who you get to reply to your ticket as well lol
I got content updating now. I had to add a nginx deployment with the standard nginx.conf loaded through a config map then used nginx-ingress to proxy the proxy container so that it would be live. Comments and posts are not syncing yet, but I think that may just need some time for the instances to sort themselves out with my instance. I'll update if I can get comment / posting working or not.
Thanks for the link. I recently did something similar, this fixed my federation issue allowing me to post / comment / upvote. I am wondering now if there is an issue with the proxy config that prevents subscriptions from going through.
thanks for using Leebra!
go to feed...