I’m trying to deploy Grist on the local LAN, but when other hosts in the local domain network access Grist, the Grist platforms of other hosts cannot display web page elements and tables normally because they are not linked to the Internet. How to solve the problem without connecting to the Internet? Ask for advice with a humble heart.
Tables and built-in widgets should be displayable without internet access but custom widgets will not be.
In this case, your best bet is to host a mirror widget server in your LAN as described here:
That should cover most of your LAN needs. Are there other instances you see of Grist trying to hit the internet and being unable to?
I’m perplexed by your description of the problems you’re encountering. Being that Grist in every variant is a webpage, in my experience with self-hosting Grist, is that at least the core functions of Grist are either an all or nothing endeavor. With all the issues I’ve worked through, I’ve never seen only certain pieces or parts of the core Grist not working.
Are you referring to widgets or websockets or things configured through the APIs not working, ie things that aren’t explicitly part of grist-core?
That or you’ve got some overly excessive ad-blockers, firewalls, etc running that are blocking certain components from working properly, which wouldn’t really be a Grist issue.
Specificity to the actual issues you’re seeing, and/or some screenshots would go a long way towards someone helping troubleshoot your problems.
- What Grist deployment are you using (desktop, core, omni-bus)
- Specific page elements or tables not being displayed
- Docker logs (if deploying core or omni-bus)
- Browser dev console error logs