Upgrading to 2.9.3 BIND issue

#1

Hello,

I use LXC, and mastodon runs in a container, all services binds to 0.0.0.0 and then it is served by nginx running on the host server reading from <container.ip>:3000, <container.ip>:4000

Now with the change in the Binding defaulting to 127.0.0.1, nginx wouldn’t be able to connect to the container services… so i followed the “upgrade notes” and edited my .env.production and added “BIND=0.0.0.0” then restarted everything, but only the streaming service (:4000) respects this, the puma one (:3000) still binds to 127.0.0.1

I did workaround it by editing systemd’s mastodon-web.service and added:
Environment=“BIND=0.0.0.0”

But i still wish to know if i did something wrong or maybe the upgrades instructions are unclear ? is my setup wrong, etc…?

Any input would be appreciated.

greetings…

#2

Both should be equivalent, maybe the puma service didn’t restart correctly…?

#3

did the usual systemctl stop/start…
i watch the process dissapear via pstree…
the logs explicitly said “Listening on tcp://127.0.0.1:3000”
with the BIND=0.0.0.0 in .env.production
when i added the BIND envar to systemd’s conf… then logs changed too to: Listening on tcp://0.0.0.0:3000

So yeah, pretty sure it was restarting correctly

#4

The Puma config is read before dotenv is loaded, so BIND has to be specified with a real environment variable and not in the dotenv file.