Network Management

Meraki API polling fails with Response status code does not indicate success: 308 (Permanent Redirect)

SolarWinds NPM may fail to retrieve the Meraki organization list when the configured Meraki endpoint returns an HTTP 308 Permanent Redirect. This occurs because the Meraki client does not complete the request successfully after the redirect, causing Get Organization List to fail.

First published date

4/8/2026 3:44 PM

Last published date

4/10/2026 3:16 PM

Overview

When adding or validating a Meraki Orchestrator in SolarWinds NPM 2026.1, the Get Organization List action may fail and the node cannot be added successfully. In the affected case, the customer reported that the Meraki API stopped working even though the API key remained active, and the logs showed repeated failures against the organizations/ request.

A typical log example is:

WARN SolarWinds.SharedCommunication.API.RequestProcessorBase`1 - An error occurred during 'organizations/' request.
Exception: System.Net.Http.HttpRequestException: Response status code does not indicate success: 308 (Permanent Redirect).

ERROR SolarWinds.Orion.Orchestrators.BusinessLayer.Meraki.Clients.MerakiClient - Get organizations failed.
System.AggregateException: One or more errors occurred.
---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 308 (Permanent Redirect).

This issue occurs when SolarWinds sends the Meraki API request to a hostname that responds with an HTTP 308 Permanent Redirect, but the client does not complete the request successfully after the redirect.

Product section

Orion Platform

Cause

By default, the Meraki polling workflow uses api.meraki.com as the hostname when adding Meraki devices. SolarWinds documentation also states that if the customer’s Meraki organization uses a different domain suffix or region-specific hostname, the MerakiCloudHostname setting must be changed in Advanced Configuration.

In this scenario, the request to organizations/ returned HTTP 308 Permanent Redirect, which caused the Meraki client to fail while retrieving organizations.

Resolution

1. Review the current Meraki hostname setting

Open Advanced Configuration and search for MerakiCloudHostname. SolarWinds supports changing this value globally or per polling engine, depending on the deployment design.

  • Use the Global tab to change the hostname for all polling engines.

  • Use the Server Specific tab when different polling engines need different Meraki endpoints.

2. Replace the redirecting hostname with the correct direct endpoint

If the configured Meraki hostname returns HTTP 308, update MerakiCloudHostname to the direct endpoint used by the customer’s Meraki environment instead of the redirecting hostname.

For the documented government/FedRAMP scenario, the working recommendation was:

  • Change MerakiCloudHostname from api.gov-meraki.com to n2.dashboard.gov-meraki.com.

3. Restart services on the affected polling engine

After changing MerakiCloudHostname, restart the SolarWinds services on the polling engine handling the Meraki polling.

4. Retry adding or validating the Meraki orchestrator

Run Get Organization List again and proceed with adding the Meraki orchestrator. SolarWinds documentation confirms this is the workflow used after setting the correct hostname and API key.

5. Validate connectivity and proxy settings if the issue persists

If the problem continues:

  • Confirm the polling engine can reach the configured Meraki endpoint over TCP 443.

  • Review the global HTTP proxy settings, because Meraki polling uses those settings.

  • In multi-engine environments, ensure the orchestrator and related nodes are handled under the same MerakiCloudHostname context and polling engine design.