Map Bugsnag's services to user-friendly hostnames and ports.
Bugsnag exposes a number of services, which you may wish to map to user-friendly hostnames and ports. Depending on your network configuration, you may need to configure your firewall, proxy or load balancer to make these changes.
The main Bugsnag dashboard. Exposed on TCP port 49080.
We recommend you expose this on your internal network, so your teams can access Bugsnag in their browsers. This is the hostname you’ll need to configure in
Example: bugsnag.internal.example.com on port 80
The write-only error and deploy reporting endpoint. Exposed on TCP port 49000.
Example: notify-bugsnag.example.com port 80, or notify.bugsnag.internal.example.com port 80
The write-only source map upload endpoint. Exposed on TCP port 49001.
Example: upload.bugsnag.internal.example.com on port 80
The webhook endpoint used for two-way issue tracker integrations. Exposed on TCP port 49002.
We recommend you expose this to any issue tracker integrations you have configured. This is the hostname you’ll need to configure in
Example: bugsnag-hooks.internal.example.com on port 80
The Bugsnag API. Exposed on the same TCP port as the dashboard, 49080, however to access this you have to set the
X-Bugsnag-API: true header.
We recommend you expose this on your internal network, so your teams can access the Bugsnag API.
Example: api.bugsnag.internal.example.com on port 80