Skip to content

Persistent 502 Bad Gateway Error when pushing a new Bot to Forta registry #866

@marceontech

Description

@marceontech

Forta Agent Publishing Error Report

Environment Details

  • Date: 2025-08-24 04:53:00
  • Agent Name: forta-flashloan-aave-detector
  • Windows Version: 10
  • Docker Version: 28.3.2, build 578ccf6
  • Node Version: v22.11.0
  • NPM Version: 11.2.0

Error Description

502 Bad Gateway when pushing to Forta registry

Detailed Error Message

Error pushing agent image: unknown: failed commit on ref "index-sha256:83b90747a4cd992bbee60d333dc53e880cd64793c6e15ead68a89b1858751caf": unexpected status from PUT request to https://disco.forta.network/v2/forta-flashloan-aave-detector/manifests/latest: 502 Bad Gateway

Attempted Approaches

1. Basic Publishing

  • Method: npx forta-agent publish
  • Result: 502 Bad Gateway
  • Registry: disco.forta.network

2. GitHub Container Registry

  • Changed registry to ghcr.io
  • Set up GitHub PAT
  • Result: Same 502 error

3. Manual Docker Build/Push

  • Built locally: ✅
  • Tagged image: ✅
  • Layer push status:
    d9059661ce70: Pushed
    93b3025fe103: Pushed
    4c3009faa752: Pushed
    56c050b536a6: Pushed
    1d634c7931e4: Pushed
    7bf47ff3592f: Pushed
    eee371b9ce3f: Pushed
    7264a8db6415: Pushed
    
  • Final result: 502 on manifest push

4. Environment Cleanup attempts

  • Cleared Docker cache
  • Cleaned npm cache
  • Removed all containers/images
  • Result: No improvement

Current Configuration

{
  "jsonRpcUrl": "https://polygon-mainnet.g.alchemy.com/v2/MY-API-KEY",
  "network": "polygon",
  "dockerImageRegistry": "disco.forta.network",
  "agentRegistryAddr": "0x61447385B019187daa48e91c55c02AF1F1f3F863"
}

5. Authentication Variations

  • Tried Docker login with different methods:
  • Interactive login
  • Password stdin
  • Environment variables
  • Result: Authentication succeeded but push still failed

6. Registry Configuration Changes

  • Tried different registry configurations in forta.config.json
  • Attempted both with and without explicit registry address
  • Result: No improvement, same 502 error

Each approach resulted in the same 502 Bad Gateway error, suggesting a potential issue with the Forta registry itself rather than client-side configuration. Been trying along the whole day with no luck, I want to deploy the bot on Polygon network, using RPC by Alchemy

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions