hi both
Early adopters of the last update may have gotten a wrong food server, with this bug.
I fixed it a few hours later, under the same version number. Sorry for that!
Just run an 1.17 updater, which should give you the new package without this problem.
Regards
KittyCatS