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:
Because of changes in how the lemmy API works I had to abandon the project awhile back.
The GitHub page is still up and if anyone wants to take over they're more than welcome. But the project would need a complete rewrite in order to function and even then there'd still be limitations.
I've tried commenting out the ports in the compose file, which should make them only available on the internal network, I thought. But when I do that, the containers can no longer connect to each other.
Did you create an explicit network for them to talk on? Otherwise the default docker network doesn't support internal DNS queries.
https://docs.docker.com/engine/network/#container-networks
Specifically you need a network using the bridge driver: https://docs.docker.com/engine/network/drivers/bridge/
Can you share the Home Assistant automation / setup that you have for Uptime Kuma notifications? As I'm in the same boat as you. I just got a webhook setup but I'm getting flooded with notifications, especially after services update.
My hope is I just want to be notified when a particular service is down for say 5 minutes but all I care about is knowing the node name. I don't necessarily care to get notified if the service comes back up.
Yes it would. In my case though I know all of the users that should have remote access snd I'm more concerned about unauthorized access than ease of use.
If I wanted to host a website for the general public to use though, I'd buy a VPS and host it there. Then use SSH with private key authentication for remote management. This way, again, if someone hacks that server they can't get access to my home lan.
Their setup sounds similar to mine. But no, only a single service is exposed to the internet: wireguard.
The idea is that you can have any number of servers running on your lan, etc... but in order to access them remotely you first need to VPN into your home network. This way the only thing you need to worry about security wise is wireguard. If there's a security hole / vulnerability in one of the services you're running on your network or in nginx, etc... attackers would still need to get past wireguard first before they could access your network.
But here is exactly what I've done:
Now I can just turn on my phone's VPN whenever I need to access any one of the services that would normally only be accessible from home.
P.s. there's additional steps I did to ensure that the masquerade of the VPN was disabled, that all VPN clients use my pihole, and that I can still get decent internet speeds while on the VPN. But that's slightly beyond the original ask here.
A couple of options in my opinion, as I just did this myself:
You can use the CLI tool to "upload" them. You can even do this from the server itself. So upload times would be as fast as your network card can process or however fast your server is, whichever is slower. It does require that you create an API key for the user in question though.
Otherwise you can create an external library and link that to your account. Now Immich will still index this library but it won't move or manage the actual files. I'm not sure though if it looks at those files for duplicates (i.e. if you try and upload the same photo from your phone to the server). This external library will also prevent deleting photos as well, FYI.
There might be other options that I'm not aware of, as I've only been using Immich for about a month now.
Edit: link to the CLI documentation: https://immich.app/docs/features/command-line-interface/
some query community:[!ultralight@lemmy.world](/c/ultralight@lemmy.world) would search your community. Now, if this community is less than 24hrs old, it may not have been indexed yet, so you may just need to wait a day or so.
I just tested with https://www.search-lemmy.com/results?query=test+community%3A%21ultralight%40lemmy.world&page=1 I was able to at least find 2 posts.
Cloudflare? Namecheap?
Not sure exactly what features you're after but the vast majority of them support what you mentioned above.
Assuming the fediverse becomes mainstream one thing I hope to actually see is that existing company forums start to join the fediverse.
Think if you no longer needed to login to EA's website to post about bugs to the Sims. Or if Prusa's 3d printer community forums could also be found right here... Or any other existing community help forum.
The problem though is, that in order to get there, Meta and others have to bring the users and essentially show the way first.
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
nslookupordigreturn 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.