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.
It’s worse than that. As the other comment said, it’s the consumer who pays the tarrif but let’s assume today:
Let’s then assume that for all 3 countries 25% of the cost is the raw Nickel that goes into the battery. Let’s also assume that it’s a flat 20% tariffs across the board.
Now your prices become:
Increase it to a 60% tariff:
So no matter what, prices go up even for the US manufacturer as they still have to import raw materials. The tariffs end up making local manufacturing more competitive with overseas at the cost of the consumer. As consumers just saw the price of batteries go from $4.00 to $5.75, a whopping 43% increase. Yay inflation!
The original idea behind tarrifs are just that… To give local businesses a competitive advantage while they catch up to overseas products. Once the US company is established you can then drop the tariff as they no longer need help while they ramp up manufacturing.
So maybe the US manufacturer costs might go down, if they’re able to make more at scale, but they still have to beat the automatic 75c increase because of their own imports. And all of that is still assuming that the tariff is large enough to make the US company the cheapest option. Otherwise it may end up backfiring and cause less sales as consumers end up not paying the increased costs. As you can see above with only a 20% tariff.
Deflation just doesn’t happen in a bubble though.
From my understanding the primary lever that can be pulled for this is the Fed interest rate. With a high interest rates you’re trying to decrease the amount of money institutions spend and rather increase the amount that they invest/save. As it becomes easier to make money by buying bonds than by reinvesting into your business. This in effect removes money from the economy.
The problem here is this means businesses also spend less on salaries, thus triggering layoffs. This then also has a downward pressure on inflation as the working class ends of being layed off as unemployment rises. This puts more and more pressure on businesses to cut costs as more and more people have less disposable income to spend.
This is the downward spiral that’s being referred to here.
In effect you can’t create defationary policies without causing high unemployment, at least in a capitalist society.
Take a look at the history of the Great Depression and the New Deal that helped the U.S. get out of it. Effectively the government had to create jobs to stimulate the economy as businesses couldn’t or wouldn’t shoulder that cost but the government could. As disposable income rose, so did spending and in turn inflation turned positive again as unemployment fell.
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.