Staging environments allowedIpRanges feature

**Describe the bug**
Hello, I observed on some of my organization's apps that when deploying staging environments, the allowedIpRanges seems unstable.
From a whitelisted IP, I have a short time window from which I can access the static website, then it becomes unavailable with a 403 error.

**How to reproduce**
Deploy a staging environment with the option `config_file_location` and a configuration file which includes at least 1 IP
```json
{
"networking": {
"allowedIpRanges": [
"your-ip/32"
]
}
}
```
When the staging is deployed, it takes sometimes to be able to access from the whitelisted IP, but after a while it becomes again unavailable with 403 error.

**Expectation**

I would expect the whitelist works the same for production and staging environments.
I would also expect that by default if a configuration is not provided for staging environments, the production one is used and not an empty configuration.