marsara9

How many corporate man hours are wasted re-inventing the wheel a bajillion times? Wouldn’t

Honestly, very little. Unless you're in a "not designed here" environment. There's a lot of open source applications/libraries out there that can be added to your project to get what you need.

But I do agree, vibe coding can be great as long as it's just for one off small projects. Need to do a quick computation or a quick POC and don't want to spend the time setting everything up? Great!

But if you want to build an application that's used by 1000 or even millions and receives regular updates? Please follow best practices / design patterns, etc... otherwise you'll be rewiring the entire codebase every time you want to add a new feature.

Are you able to query to see what IP address that domain returns? Does it return the 192.168.x address that you set?

Edit: But the idea is to first see where the connection is failing... first see what error your browser is returning? 5xx? 4xx? This can be an indication as to where the error is happening. But high-level check DNS first, see if nslookup or dig return the IP address that you set. (Remember changes to DNS entries can take time to propagate). Assuming all of that is correct, then check to see what nginx is showing in its logs. Do you see it logging anything every time you try and access it via the domain name? Next up is checking the logs from plex itself, does it show any logs coming though? etc... But the idea is to find where the connection is breaking down.

Are you wanting to access your sites remotely or only via the local LAN?

If you're aiming for remote access then you can't use the 192.168.* range as that's the up address behind your NAT/router. You have use your public IP and do port forwarding from your router.

If it was a certificate issue I'd expect youd just get an error from your browser saying the cert is invalid or expired.

If I had to guess though you're running into a nat reflection issue: https://nordvpn.com/cybersecurity/glossary/nat-loopback/

Read up on that. But you may need to provide different DNS entries if you're inside or outside your LAN or add a NAT hairpin rule to your router. But this is only applicable if you're exposing the same service to the WWW.

Some other things to try though:

• Have you tried just pinging the address? Is the DNS resolution returning the address you expect?
• Whats in your nginx logs? Do you see anything when you try and connect?
• Within your nginx container can you ping your service directly? Is something blocking nginx from accessing the site?

So I've been working on a solution for this.

As I see it Google and others are going to have a hard if not impossible time to incorporate the fediverse, and the fact that the same content can exist on multiple servers.

So I'm working on a search engine specifically build, for Lemmy at least. Where it'll take you to whatever your preferred instance is when tapping on a search result.

I hope to have a MVP up and running in a few more days.