Grok Bot browser blocked from loopback (127.0.0.1) since Nov 6, local services unreachable; shell fine

Hi @RM_PANDA2297, yes, the loopback block is intentional. It’s a security change that bot computers pick up when they’re rebuilt on the current image, which is why it started for you on Nov 6. Without it, any web page open in the bot’s browser could connect to services running on the bot’s own machine. The browser can now only use its built-in proxy on loopback. The shell isn’t affected, which is why curl to your NAS still works.