What confuses me is that Remote Config was working fine until yesterday, and today it’s just spitting out this Error without me touching anything.
Unity.Services.RemoteConfig.WebRequest.WebRequestException: HTTP/1.1 403 Forbidden
at Unity.Services.RemoteConfig.ConfigManagerImpl.FetchConfigsAsync (System.String configType, System.Object userAttributes, System.Object appAttributes, System.Object filterAttributes) [0x001c9] in .\Library\PackageCache\com.unity.remote-config-runtime@4.0.2\Runtime\ConfigManagerImpl.cs:286
at Unity.Services.RemoteConfig.ConfigManagerImpl.FetchConfigsAsync (System.Object userAttributes, System.Object appAttributes) [0x0002f] in .\Library\PackageCache\com.unity.remote-config-runtime@4.0.2\Runtime\ConfigManagerImpl.cs:338
at UGSManager.FetchConfigsAsync () [0x00038]
Hey @DaegeunPark ,
The HTTP/1.1 403 Forbidden error typically indicates a client-side issue where the request is blocked due to insufficient permissions or incorrect configuration. Seeing this for Remote Config is pretty uncommon and here are some possible reasons:
-
Invalid or Missing Credentials: Incorrect or missing API key, token, or authentication details. This should not be the case as we don’t need the auth token for accessing the request endpoint.
-
Permission Restrictions: Verify that your user account or service account has the necessary permissions set in the Unity Dashboard for accessing Remote Config.
-
Incorrect Configuration: Double-check the projectId and environmentId values in your request. Ensure they match the ones listed in your Unity Dashboard.
-
Endpoint Issues: Confirm you are targeting the correct API endpoint for your project and environment. This one is also not likely as we set that endpoint within the SDK.
-
CORS Restrictions or IP Filtering: If applicable, verify that your server or network configuration allows requests from your client.
To help diagnose the issue further, tools like Proxyman or Charles Proxy for Mac or Fiddler for Windows can be invaluable. If you can use them, please inspect the details of your outgoing requests, such as headers, endpoints, and payloads, which can provide critical insights into what might be causing the error.
If you’d like, also please feel free to provide the projectId and environmentId, and we can take a closer look at your specific setup to help identify the cause of the issue.
The backend team can also take a look if you have e.g some rules (overwrites) set, but unpublished or some similar scenario.
I attached the screenshot for successful request for Remote Config, where you can also see the headers as well, so it would help if you can compare your case with it.
Let us know how we can assist further!
Best regards,
Vlatko