The answer here is fairly simple because your eZ publish installation's user/role permissions are configured incorrectly to allow allow anonymous users access under a different siteaccess than the one you are using.
This happens often when moving eZ publish to another server or environment without adding the desired siteaccess into the Admin >> User >> Role >> Anonymous >> Permissions.