u/RowFit1060

Hi All. First Satisfactory Game, trying to figure out how to get the maximum power out of my coal plants when I've got a hard upper limit on how much water I can supply them. I'm about to transition to Oil power, but I'm basically at max power capacity and need to squeeze out every watt i can til I can bring it online.

So. I have a pure sulfur & pure coal node supplying 270/min compacted-coal to 16 coal plants all overclocked to 150%. I have found that I have more than enough fuel to crank them all the way to 200% or higher. But if I do that, they run out of water and start shutting down.

The problem is that the only water source in reasonable distance of the plant (ie not on the other side of my map) can only supply a maximum of six (maybe seven) water extractors. Head Lift is not an issue as the water source is Uphill from the power plant and feeds it from the top.

Each water extractor has its own dedicated mk1 pipe and is cranked to 250%. They are divided into two groups of 3, each leading to a pipe manifold with a loopback built over top of the coal plants, like so.

W      W      W
|______|______|
C-C-C-C-C-C-C-C
|_____________|

I just got access to valves. How do I maximize the power output when my maximum possible water flow is 1,800m^(3)/s?

Hi, relatively new to docker.
I found myself in a bit of a pickle, and I'm trying to get advice. I use a SWAG container to reverse-proxy a few services on my NAS via a user defined bridge network between the containers. However, I want to be able to integrate a few other services; the problem is that those services are currently running on separate devices on my LAN, (game servers and home assistant), and moving them onto my nas isn't really... practical (it would fry the thing).

Is there a way to expose JUST the swag container via a Macvlan or something so it can reverse-proxy to devices on my 10.x.x.x LAN while ALSO staying connected to the dockers on the bridge. Or should I have two swag instances?? I'm just trying to figure out a solution without publishing all my ports to the web on accident.

Ok, I run immich and jellyfin docker instances on my NAS (running OMV for OS), reverse proxied through a SWAG container on the same machine. After moving my server to another ethernet port, my websites went down, and I was unable to get new HTTPS certs via let's encrypt.
On another post, I was able to narrow it down to a DNS issue.

I receive the following error from the SWAG:

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by NameResolutionError("HTTPSConnection(host='acme-v02.api.letsencrypt.org', port=443): Failed to resolve 'acme-v02.api.letsencrypt.org' ([Errno -3] Try again)"))

'$ Cat /etc/resolv.conf' returns a stub on the ethernet interface

nameserver 127.0.0.53
options edns0 trust-ad
search .

Running '$ resolvectl status' returns

Global
      Protocols: +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (eno1)
Current Scopes: LLMNR/IPv4
    Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
               DNSSEC=no/unsupported

and running nslookup for letsencrypt gives me

$ nslookup acme-v02.api.letsencrypt.org  
Server:         127.0.0.53
Address:        127.0.0.53#53

** server can't find acme-v02.api.letsencrypt.org: REFUSED

I can nslookup other sites from my NAS just fine, But not let's encrypt. I use a pihole, but I first whitelisted acme-v02.api.letsencrypt.org, then just exempted my nas from being forced to use the pihole in my router, and added quad9 as a backup DNS server on the NAS, so I know it's not being blocked that way.

The Sites are available on LAN through local static IP and hostname, and my other port forwarded services are running fine, so I know it's not an issue with port forwarding or static IP.
I've also verified that the DDNS docker I have running on the machine IS working and updating my IP with Cloudflare whenever it's changed by my ISP, so I know it's not that either.

Everything WORKED until a week ago when I moved the nas, so I have no earthly idea why it suddenly can't resolve Let's encrypt. Please, help.

Alright. I have a NAS at my house running OMV (yes I know truenas is better but I'm locked in at this point) that has a dockerized jellyfin server and immich instance published through a SWAG container.
This weekend, moved the server & modem to repair a piece of scuffed floor under the cabinet they were in. I had to unplug my AT&T Fiber modem (it does IP passthrough to an Asus router that did not need to be moved), and put it on a little end table where I could move it out of the way when needed. I also moved the NAS to another ethernet connection in another room. Suddenly, all my instances are unreachable on WAN. They work fine on LAN. I have verified:

• My External IP is unchanged, and I have DDNS set up to update cloudflare even if it did
• My NAS has a Static LAN IP saved in my ASUS router
• Port Forwarding on router is unchanged, and a separate game server on my PC still works fine
• The Docker Compose files do not have any port conflicts
• My NAS Firewall is unchanged.
• The Docker containers are on the same user-defined bridge network.
• Everything works on LAN like I would expect it to, both from LAN IP and hostname.

The Services are on Separate subdomains registered through Cloudflare, with SWAG doing the re-directs.
The ATT Fiber hub operates on IP-Passthrough, and an Asus router running handles port forwarding and DHCP.
I have a PiHole on a separate device managing DNS requests only, not DHCP.

All services WERE up and working fine prior to this weekend.

What on god's green earth am I missing????
I even tried to switch the domains in cloudflare so I could run the dockers through a Argo tunnel like I did before I got fiber and that didn't work either (though I may have did it incorrectly, it's been awhile).

I'm practically tearing my hair out trying to figure out what went wrong, and If anyone has ideas or suggestions, I would be very thankful.