As you may recall, I’ve thought to try to stem off the bandwidth consumption at this point by just changing everything to use internal private IP addresses since that will at least stop me from getting some large bills.
I have noticed something else peculiar here. I changed the database connection away from the public IP to the private IP so as to not consume the monthly transfer allowance as quickly, but on the database server I expected to only see connections made via the private IP address from the Discourse docker server. I DO see traffic from the local private IP now, but I still see inordinate amounts of traffic coming from the public IP and thus still rapidly consuming the monthly allowance.
I’ve looked and looked for both the public IP address and the hostname of the database server on the Discourse Docker server, but I can’t find it anywhere. Even if I go into the app (
./launcher enter app) and do an
env | grep DB I see the correct PRIVATE IP address for the LAN being used here. I can grep through the filesystem and I just don’t see occurrences that I’d expect.
Any thoughts on how Discourse or the Docker image might be still accessing the wrong IP? I just cannot figure out where all of this public IP traffic is spawning from on the Discourse server.