- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
API Failed to establish a new connection
Hello,
My team has a reporting process that pulls daily from the Meraki API site. It has been functioning fine until Thursday of last week. It now begins to connect and pull data but errors after some time with the following:
2024-10-15 02:21:54,725 DEBUG Incremented Retry for (url='/api/v1/networks/L_x/alerts/settings'): Retry(total=19, connect=None, read=None, redirect=None, status=None) 2024-10-15 02:21:54,725 WARNING Retrying (Retry(total=19, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is unreachable',)': /api/v1/networks/L_x/alerts/settings 2024-10-15 02:21:54,725 DEBUG Starting new HTTPS connection (2): n459.meraki.com:443
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='n459.meraki.com', port=443): Max retries exceeded with url: /api/v1/networks/L_x/alerts/settings (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is unreachable',))
To triage the delay between connection attempts has been up to 5 minutes and still erroring.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi.. Looks like you are hitting the shard (n459.meraki.com) directly? Can you try hitting the api megaproxy itself? https://api.meraki.com/api/v1
If that fails, it might be worth opening a support case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posting a follow up. We were pointing to https://api.meraki.com/api/v1, but some sort of redirect was happening to cause the use of n459.meraki.com.
As of this morning, everything is working again without any additional changes to our scripts. Guess things were resolved on Meraki's side.
