Update fallback directory whitelist based on operator relay changes
We need to contact the operators to check if these changes are permanent. (It's safe to ignore these warnings: we don't want fallbacks that change their details, particularly without telling us.)
WARNING::71AB4726D830FAE776D74AEF790CF04D8E0151B4 excluded: has it changed IPv4 from 18.104.22.168 to 22.214.171.124? WARNING::BD552C165E2ED2887D3F1CCE9CFF155DDA2D86E6 excluded: has it changed IPv4 from 126.96.36.199 to 188.8.131.52? WARNING::0C2C599AFCB26F5CFC2C7592435924C1D63D9484 excluded: has it lost its former IPv6 address [2001:41d0:a:fb7a::1]:9001? WARNING::BC630CBBB518BE7E9F4E09712AB0269E9DC7D626 excluded: has it changed ORPort from 184.108.40.206:9001 to 220.127.116.11:443? WARNING::0C1E7DD9ED0676C788933F68A9985ED853CA5812 excluded: has it lost its former IPv6 address [2a02:180:1:1::5b8f:538c]:993? WARNING::CBD0D1BD110EC52963082D839AC6A89D0AE243E7 excluded: has it changed IPv4 from 18.104.22.168 to 22.214.171.124? WARNING::50586E25BE067FD1F739998550EDDCB1A14CA5B2 excluded: has it lost its former IPv6 address [2a02:168:6e00:0:3a60:77ff:fe9c:8bd1]:9001? WARNING::2EC0C66EA700C44670444280AABAB1EC78B722A0 excluded: has it changed ORPort from 126.96.36.199:403 to 188.8.131.52:443? WARNING::DC163DDEF4B6F0C6BC226F9F6656A5A30C5C5686 excluded: has it changed IPv4 from 184.108.40.206 to 220.127.116.11? WARNING::F4263275CF54A6836EE7BD527B1328836A6F06E1 excluded: has it changed DirPort from 18.104.22.168:9090 to 22.214.171.124:80?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information