The way my setup works is…
If I punch a hole in the firewall for you, it doesn’t matter what port you want/need, it’s open.
Basically, Site kit has full access to whatever it wants (within reason of course).
For visitors, everything is funneled through Cloudflare. Again though, Site kit has access through there too, even though it’s not needed as Site kit has direct access.
Last, but not least, Site kit has full access to reverse DNS, there shouldn’t be a problem there either. dig l34.ns.rocklobster.network = 162.208.8.222 – dig -x 162.208.8.222 = l34.ns.rocklobster.network
As of about an hour ago, it’s still working, but it takes a long time (hanging the system) for it to populate information on the dashboard or the admin dashboard.
-
This reply was modified 9 months, 1 week ago by
ohgoodiee.
-
This reply was modified 9 months, 1 week ago by
ohgoodiee.
@ohgoodiee Very useful insights, many thanks for sharing. Glad to hear it’s now working with your firewall modifications. If you encounter anymore issues feel free to get in touch.