• 4 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle
  • When I say two servers I mean two VMs to get the system to work effectively.

    From memory, the admin interface doesn’t get an SSL certificate issued to it. It perpetually stays HTTP. If you don’t set up another server as a reverse proxy, it won’t let you log in due to CORS issues. Add another server as a reverse proxy, and it’ll come good and let you log in.

    Hopefully that makes sense?






  • I hope that in my lifetime I can see ISPs regulated as a public utility.

    From an Aussie where our Internet is somewhat considered a “public utility” (NBNCo), it’s not the best. I’m paying $130/mo (Aussie bucks) for 250/100 fibre.

    Our NTDs are capable of gigabit symmetrical, but thanks to our Lord and Saviour, Rupert Murdoch, it was essentially limited speed wise and the network was built with ridiculous complexity, such as the CVC constraints (Connectivity Virtual Circuit), which means ISPs have to buy additional bandwidth and hope and pray that every user doesn’t max out their connections at the same time.

    For example, the POI (Point of Interconnect) I’m connected to has a total of 1.5Gbps with the ISP I’m with. Based on their stats which they make public to customers, I’m guesstimating that there’s approximately ~50 other households in my POI area connected with this ISP. We all have to share that bandwidth otherwise it slows to a crawl.

    ETA: I’m purely talking about the FTTP network here, not the other part of the mess that is NBNCo and FTTN/C/B, Fixed Wireless, Satellite & HFC… the NBN is a complete mess.






  • I did, yes. It took me a few hours of troubleshooting though, spanned across two days. I’m using Nginx Proxy Manager instead of the Nginx proxy that comes with Lemmy, but it all translates similarly. I also followed this guide on YouTube.

    If it’s sitting there saying “pending” for your subscriptions, it may be that the “proxpass /” location ports are off by one. It’ll look like it’s federating properly, but really it isn’t. That was one thing I noticed with the documentation/examples; things were off and not updated. Check my screenshot attached for what I mean. The documentation/example config for the proxy lists the Lemmy-ui port as 1235, but it’s actually 1236.

    Screenshot

    Hopefully that makes sense. If I can be of any more assistance, let me know!!