Yes, they are queries made and responses received by the phpBB code running on the server, and not "from the browser." We of course agree with 3Di that he's "seeing activity in the browser" when checking extension versions, but that's just the UI portion of the processing. Not "the actual version check being performed", which is JSON data exchanges between the server-side phpBB code and whomever the remote version check server is (phpbb.com or otherwise).
+1 for what 3Di said; that is not my experience either. There is nothing "by definition of trying to run a local instance of your phpBB site" which will make it inherently need to constantly contact either your own production site's web server, or even phpbb.com's servers.Lumpy Burgertushie wrote: ↑Wed Jun 24, 2020 1:15 amdoes anyone know how to completely stop phpbb from trying to phone home when running in wamp or xampp or usbwebserver etc.
I have come to the conclusion that phpbb trying to phone home for different reasons is what make every one of the lamp stacks so slow on local host.
That said, indeed you can be in a situation where that is in fact what's happening in your local installation. For example, if your .htaccess was copied into the local instance, and it has particular paths or file types which were being re-written with rules that cited your production DNS name, components of the pages which "could" or "should" have been served from the local X/WAMPP server could potentially be redirecting your web browser to pull those resources from the production site instead. Even if the main page documents themselves are coming from the local server.
Or you could potentially create that kind of situation in even stranger ways, like having copied a config.php which was still configured to still talk to the production database server's IP address or DNS name, despite having a local database server you could have been using. But again, nothing that "is actually required to be that way", nor "by definition a local phpBB installation is going to behave slowly" because they are always "required to phone home."
If the F12 Network view doesn't show you resources are being pulled from somewhere other than the local web server, the next step I would try is a straight-up LAN trace of all the traffic on and off my local computer when I'm interacting with the local site. To try and identify what is still possibly trying to access something (successfully or unsuccessfully) over the wire, if not HTTP requests from your web browser that would have been visible in the F12 Network view.